Install
$ agentstack add skill-goca-se-dotcontext-add-new-command ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Skill: Add a New Claude Code Slash Command
When to Use
Use this skill when you need to add a new interactive command that users can invoke with /command-name in Claude Code.
Prerequisites
- Understanding of what the command should do
- Knowledge of Claude Code's tool system (AskUserQuestion, file tools, etc.)
Steps
1. Create the command file
Create a new markdown file in .claude/commands/:
touch .claude/commands/my-command.md
The filename (without .md) becomes the slash command name.
2. Structure the command file
Follow this template structure:
# Command Name
Brief description of what this command does.
## Instructions
Detailed instructions for Claude on how to execute this command.
**Important guidelines:**
- List specific behaviors
- Reference which tools to use
- Mention any context files to check
## Tasks
### 1. First Step
Description of what to do first.
### 2. Second Step
Description of what to do next.
## Output
Describe what the command should produce when complete.
3. Include AskUserQuestion usage
Per ADR-005, all commands should use AskUserQuestion for clarification:
**Important:** Use the AskUserQuestion tool to clarify:
- [Question 1]
- [Question 2]
4. Reference context files
Commands should check relevant context:
Before proceeding:
- Check `.context/decisions/` for related ADRs
- Consult `.claude/skills/` for patterns to follow
5. Test the command
In Claude Code, run /my-command to verify it works as expected.
Anti-Patterns
- Don't make commands too broad - Keep focused on one task
- Don't skip AskUserQuestion - Always clarify before significant work
- Don't hardcode paths - Use relative paths from project root
- Don't ignore existing patterns - Check skills/ and decisions/ first
Example
See .claude/commands/code-review.md for a well-structured command that:
- Has clear instructions
- Uses a checklist for thoroughness
- Provides specific output format
- References exact file locations
Related
- ADR-004: Claude Code integration
- ADR-005: AskUserQuestion requirement
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: goca-se
- Source: goca-se/dotcontext
- License: MIT
- Homepage: https://github.com/goca-se/dotcontext#readme
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.