skill-creator
Skill Creator
Create effective Claude Skills using progressive disclosure.
When to Create a Skill
Create a skill when you notice:
- Repeating context across conversations
- Domain expertise needed repeatedly
- Project-specific knowledge Claude should know automatically
Progressive Disclosure
Skills load in 3 levels:
- Metadata (~27 tokens) - YAML frontmatter for triggering
- Instructions (<680 tokens) - SKILL.md body with core patterns
- Resources (unlimited) - references/ scripts/ assets/ loaded on demand
Key: Keep Levels 1 & 2 lean. Move details to Level 3.
Structure
my-skill/
├── SKILL.md # Core instructions + metadata
├── references/ # Detailed docs (loaded as needed)
├── scripts/ # Executable operations
└── assets/ # Templates, images, files
References
- quick-start.md - Creating your first skill
- writing-guide.md - Writing effective skills
- development-process.md - Step-by-step workflow
- skill-examples.md - Patterns and examples
- cli-reference.md - CLI tool usage
- anthropic-resources.md - Official best practices
More from bumgeunsong/daily-writing-friends
firebase-functions
Use when creating or modifying Firebase Cloud Functions in /functions directory. Enforces function structure and error handling patterns.
43pr-stacking
PR stacking workflow for breaking large features into smaller, dependent PRs. Use when planning multi-step features, creating dependent branches, or rebasing stacked changes.
29commit
Use when creating git commits in this project
28refactoring
Use when user explicitly asks to refactor code, or when test coverage is requested for untested code with side effects. Enforces Functional Core Imperative Shell pattern extraction before any changes.
28api-layer
Use when creating or modifying API functions in */api/ directories. Enforces Firestore patterns and data fetching conventions.
28code-style
Use when writing or modifying any code. Enforces naming conventions, function design, and code clarity principles.
28