Command Code

Manage Agent Skills

Learn how to create, browse, edit, and organize your Agent Skills in Command Code.

Browsing skills

Use the /skills slash command to view all your skills:

Open skills browser

# In Command Code interactive session /skills

This opens an interactive menu showing:

  • All user-level skills with (user) label
  • All project-level skills with (project) label
  • Use arrow keys to navigate
  • Press Enter to open any skill in your editor
  • Press Esc to close and return to your session

Create skills

User-level skills

User-level skills are available across all your projects.

Location: ~/.commandcode/skills/

Create a user skill

# Create the directory mkdir -p ~/.commandcode/skills/my-skill # Create the SKILL.md file cat > ~/.commandcode/skills/my-skill/SKILL.md << 'EOF' --- name: my-skill description: What this skill does and when to use it --- # My Skill Instructions for Claude... EOF

Use cases:

  • Personal coding preferences
  • General development workflows
  • Cross-project best practices
  • Your own code style guidelines

Example:

Code review skill

mkdir -p ~/.commandcode/skills/code-review cat > ~/.commandcode/skills/code-review/SKILL.md << 'EOF' --- name: code-review description: Perform thorough code reviews checking for bugs, security issues, and best practices --- # Code Review Checklist ## Security - [ ] No hardcoded credentials or API keys - [ ] Input validation on all user data - [ ] Proper authentication and authorization ## Code Quality - [ ] Clear, descriptive variable names - [ ] Functions do one thing well - [ ] No code duplication ## Performance - [ ] No unnecessary loops - [ ] Efficient data structures - [ ] Optimized queries ## Testing - [ ] Unit tests cover main functionality - [ ] Edge cases tested - [ ] Error conditions handled EOF

Project-level skills

Project-level skills are available only in that specific project.

Location: .commandcode/skills/ (in your project root)

Create a project skill

# Create the directory mkdir -p .commandcode/skills/my-skill # Create the SKILL.md file cat > .commandcode/skills/my-skill/SKILL.md << 'EOF' --- name: my-skill description: What this skill does and when to use it --- # My Skill Instructions for Claude... EOF

Use cases:

  • Project-specific patterns
  • Team conventions
  • Architecture guidelines
  • Domain-specific workflows

Example:

API guidelines skill

mkdir -p .commandcode/skills/api-guidelines cat > .commandcode/skills/api-guidelines/SKILL.md << 'EOF' --- name: api-guidelines description: API design patterns and conventions for this project --- # API Guidelines ## Endpoint naming - Use plural nouns: `/users`, `/posts` - Use kebab-case: `/user-profiles` - Version in URL: `/v1/users` ## Response format Always return JSON with this structure: \```json { "data": { ... }, "meta": { "count": 10, "page": 1 }, "errors": [] } \``` ## Error codes - 400: Bad request (validation errors) - 401: Unauthorized (missing/invalid token) - 403: Forbidden (insufficient permissions) - 404: Not found - 500: Server error ## Authentication All endpoints require Bearer token in Authorization header except: - POST /v1/auth/login - POST /v1/auth/register EOF

Edit skills

You can edit using the /skills command.

  1. Type /skills in Command Code
  2. Navigate to the skill you want to edit
  3. Press Enter

This opens the SKILL.md file in your default editor (configured via $EDITOR environment variable).

Manual editing

You can also edit skills directly via the following paths:

Edit a skill

# Edit user-level skill code ~/.commandcode/skills/my-skill/SKILL.md # Edit project-level skill code .commandcode/skills/my-skill/SKILL.md

After editing, the changes are immediately applied and ready to use. No restart is required.

Setting up your editor

The /skills command uses your $EDITOR environment variable to open files.

See setting up your editor for setup instructions.

Organizing skills

You can organize your skills using the following best practices:

Single skill per directory

Each skill must be in its own directory:

.commandcode/skills/ ├── code-review/ │ └── SKILL.md ├── api-guidelines/ │ └── SKILL.md └── testing-patterns/ └── SKILL.md

Adding supporting files

Skills can include additional files:

my-skill/ ├── SKILL.md # Required ├── scripts/ # Executable code │ ├── process.py │ └── validate.sh ├── references/ # Additional docs │ ├── API_REFERENCE.md │ └── EXAMPLES.md └── assets/ # Templates, resources ├── template.json └── schema.sql

Reference these files in your SKILL.md:

See [API Reference](references/API_REFERENCE.md) for details. Run the validation script: \```bash scripts/validate.sh \```

Naming conventions

Skill names

  • Use lowercase letters, numbers, and hyphens only
  • Max 64 characters
  • Must not start or end with hyphen
  • No consecutive hyphens

Good names:

code-review api-guidelines testing-patterns commit-messages

Bad names:

CodeReview # uppercase not allowed code_review # underscores not allowed -code-review # cannot start with hyphen code--review # consecutive hyphens

Directory names

The directory name must match the skill name field:

code-review/ # Directory name └── SKILL.md # Must have: name: code-review

Next steps