AI Skill Report Card
Managing Claude Skills
Creates and manages Claude Code agent skills with proper structure and configuration. Use when creating new skills, organizing skill files, or setting up skill frontmatter.
Quick Start15 / 15
Create a basic skill:
Bashmkdir -p ~/.claude/skills/my-skill cat > ~/.claude/skills/my-skill/SKILL.md << 'EOF' --- description: Does something specific when triggered ---
Recommendation▾
Add more specific triggers in the description like 'when creating, organizing, configuring, or debugging Claude skills'
Instructions
- Analyze the input
- Process according to requirements
- Return formatted output
Examples18 / 20
Example 1: Input: sample input Output: expected result EOF
Recommendation▾
Include examples of actual skill testing and validation steps with concrete commands
Workflow15 / 15
Creating a new skill:
Progress:
- Create skill directory:
mkdir -p ~/.claude/skills/skill-name - Write SKILL.md with frontmatter and instructions
- Test with
/skill-nameor let Claude auto-invoke - Add supporting files if needed
- Refine based on usage
Skill locations by scope:
- Personal:
~/.claude/skills/skill-name/(all projects) - Project:
.claude/skills/skill-name/(current project only) - Enterprise: Managed settings (organization-wide)
Recommendation▾
Expand completeness section with troubleshooting common errors and file structure requirements
Examples18 / 20
Example 1: Simple task skill
YAML--- name: code-review-checklist description: Provides code review checklist for pull requests disable-model-invocation: true ---
Code Review Checklist
- Code follows style guidelines
- Tests are included and passing
- Error handling is appropriate
- Documentation is updated
**Example 2: Auto-invoked reference skill**
```yaml
---
description: API conventions for this codebase. Use when writing or reviewing API code.
---
API Standards
- Use RESTful naming conventions
- Return consistent error formats with status codes
- Include request validation
- Document all endpoints
**Example 3: Skill with dynamic content**
```yaml
---
description: Summarizes git changes and flags risks. Use when reviewing diffs or creating commits.
---
Current Changes
!git diff HEAD
Instructions
Summarize changes in bullet points and list any risks.
Best Practices
Frontmatter essentials:
- Always include
descriptionwith trigger phrases - Use
disable-model-invocation: truefor manual-only skills - Set
context: forkfor complex, isolated tasks - Limit
allowed-toolsfor focused workflows
Content guidelines:
- Keep instructions concise (skills stay in context)
- Use dynamic injection (!
command) for live data - Reference supporting files from main SKILL.md
- Include concrete examples with input/output pairs
Organization:
- Use kebab-case directory names
- Group related skills in subdirectories
- Place frequently-used skills in personal folder
- Project-specific skills go in
.claude/skills/
Common Pitfalls
- Missing description: Claude won't know when to auto-invoke
- Verbose instructions: Every line costs tokens across turns
- Wrong scope: Personal skills override project ones
- No examples: Abstract instructions confuse execution
- Forgetting restart: New top-level skill directories need session restart
- Tool conflicts:
disallowed-toolsonly applies during skill execution