Skill Creator
Generate production-ready Claude Code skills following established conventions.
Core Workflow
- Define skill purpose: Clear name, description, and use cases
- Determine category: Place in correct folder (foundation, frontend, backend, etc.)
- Create SKILL.md: Main skill file with frontmatter and content
- Add references: Optional templates.md, conventions.md, or patterns.md
- Include examples: Production-ready code samples
- Write checklist: Output verification checklist
Skill Categories
| Category |
Path |
Purpose |
| Foundation |
foundation/ |
Project setup, dev environment, git, docs |
| Frontend |
frontend/ |
React, Vue, UI components, styling, UX |
| Backend |
backend/ |
APIs, auth, server logic, services |
| AI Engineering |
ai-engineering/ |
LLMs, RAG, agents, prompts |
| Architecture |
architecture/ |
System design, ADRs, tech decisions |
| CI/CD |
ci-cd/ |
Automation, deployments, pipelines |
| Database |
database-management/ |
Migrations, queries, data engineering |
| Testing |
testing/ |
Unit tests, integration, e2e, mocks |
| Security |
security/ |
Vulnerabilities, auth, hardening |
| Performance |
performance/ |
Observability, monitoring, optimization |
SKILL.md Template
---
name: skill-name-in-kebab-case
description: One-line description of what the skill does and when to use it. Include trigger phrases like "use when users request X, Y, or Z".
---
# Skill Title
Brief tagline explaining the skill's value proposition.
## Core Workflow
1. **Step one**: Description
2. **Step two**: Description
3. **Step three**: Description
...
## [Main Content Sections]
### Section with Code Examples
\`\`\`typescript
// Production-ready code example
\`\`\`
### Patterns / Templates
Document reusable patterns with examples.
## Best Practices
- Practice one
- Practice two
- Practice three
## Output Checklist
Every output should include:
- [ ] Item one
- [ ] Item two
- [ ] Item three
Reference Files Structure
When skills need supplementary documentation:
skill-name/
├── SKILL.md # Main skill file (required)
└── references/ # Optional reference materials
├── templates.md # Code/file templates
├── conventions.md # Standards and conventions
└── patterns.md # Reusable patterns
Frontmatter Requirements
---
name: kebab-case-skill-name # Must match folder name
description: >
Clear description including:
- What the skill does
- When to use it
- Trigger phrases ("use when X", "create Y", "generate Z")
---
Content Guidelines
Code Examples
- Must be production-ready, not pseudocode
- Include TypeScript types where applicable
- Show complete, working examples
- Use modern syntax and best practices
Sections to Include
- Core Workflow: Numbered steps for using the skill
- Main Content: Patterns, templates, examples
- Best Practices: Industry-proven recommendations
- Output Checklist: Verification items
Writing Style
- Active voice, imperative mood
- Concise, scannable formatting
- Tables for structured comparisons
- Code blocks for all technical content
Skill Quality Criteria
Completeness
Consistency
Usefulness
Example: Creating a New Skill
Step 1: Define the Skill
Name: api-rate-limiter
Category: backend
Purpose: Implement rate limiting for APIs
Triggers: "add rate limiting", "protect API", "throttle requests"
Step 2: Create Folder Structure
mkdir -p backend/api-rate-limiter
touch "backend/api-rate-limiter/SKILL.md"
Step 3: Write SKILL.md
---
name: api-rate-limiter
description: Implements rate limiting for APIs using token bucket, sliding window, or fixed window algorithms. Use when users request "add rate limiting", "protect API from abuse", or "throttle requests".
---
# API Rate Limiter
Protect your APIs from abuse with production-ready rate limiting.
## Core Workflow
...
Step 4: Add References (if needed)
mkdir -p backend/api-rate-limiter/references
touch backend/api-rate-limiter/references/algorithms.md
Output Checklist
When creating a new skill:
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: skill-creator-1343description: Creates new Claude Code skills following repository conventions with proper structure, frontmatter, workflows, code examples, and reference files. Use when users request "create a skill", "new skill", "generate skill", or "add skill to collection".4---56# Skill Creator78Generate production-ready Claude Code skills following established conventions.910## Core Workflow11121. **Define skill purpose**: Clear name, description, and use cases132. **Determine category**: Place in correct folder (foundation, frontend, backend, etc.)143. **Create SKILL.md**: Main skill file with frontmatter and content154. **Add references**: Optional templates.md, conventions.md, or patterns.md165. **Include examples**: Production-ready code samples176. **Write checklist**: Output verification checklist1819## Skill Categories2021| Category | Path | Purpose |22| -------------- | ---------------------- | ----------------------------------------- |23| Foundation | `foundation/` | Project setup, dev environment, git, docs |24| Frontend | `frontend/` | React, Vue, UI components, styling, UX |25| Backend | `backend/` | APIs, auth, server logic, services |26| AI Engineering | `ai-engineering/` | LLMs, RAG, agents, prompts |27| Architecture | `architecture/` | System design, ADRs, tech decisions |28| CI/CD | `ci-cd/` | Automation, deployments, pipelines |29| Database | `database-management/` | Migrations, queries, data engineering |30| Testing | `testing/` | Unit tests, integration, e2e, mocks |31| Security | `security/` | Vulnerabilities, auth, hardening |32| Performance | `performance/` | Observability, monitoring, optimization |3334## SKILL.md Template3536```markdown37---38name: skill-name-in-kebab-case39description: One-line description of what the skill does and when to use it. Include trigger phrases like "use when users request X, Y, or Z".40---4142# Skill Title4344Brief tagline explaining the skill's value proposition.4546## Core Workflow47481. **Step one**: Description492. **Step two**: Description503. **Step three**: Description51 ...5253## [Main Content Sections]5455### Section with Code Examples5657\`\`\`typescript58// Production-ready code example59\`\`\`6061### Patterns / Templates6263Document reusable patterns with examples.6465## Best Practices6667- Practice one68- Practice two69- Practice three7071## Output Checklist7273Every output should include:7475- [ ] Item one76- [ ] Item two77- [ ] Item three78```7980## Reference Files Structure8182When skills need supplementary documentation:8384```85skill-name/86├── SKILL.md # Main skill file (required)87└── references/ # Optional reference materials88 ├── templates.md # Code/file templates89 ├── conventions.md # Standards and conventions90 └── patterns.md # Reusable patterns91```9293## Frontmatter Requirements9495```yaml96---97name: kebab-case-skill-name # Must match folder name98description: >99 Clear description including:100 - What the skill does101 - When to use it102 - Trigger phrases ("use when X", "create Y", "generate Z")103---104```105106## Content Guidelines107108### Code Examples109110- Must be production-ready, not pseudocode111- Include TypeScript types where applicable112- Show complete, working examples113- Use modern syntax and best practices114115### Sections to Include1161171. **Core Workflow**: Numbered steps for using the skill1182. **Main Content**: Patterns, templates, examples1193. **Best Practices**: Industry-proven recommendations1204. **Output Checklist**: Verification items121122### Writing Style123124- Active voice, imperative mood125- Concise, scannable formatting126- Tables for structured comparisons127- Code blocks for all technical content128129## Skill Quality Criteria130131### Completeness132133- [ ] Solves a specific, well-defined problem134- [ ] Includes working code examples135- [ ] Has clear trigger phrases in description136- [ ] Provides output verification checklist137138### Consistency139140- [ ] Follows naming conventions (kebab-case)141- [ ] Uses standard section headings142- [ ] Matches existing skill format143- [ ] Placed in correct category folder144145### Usefulness146147- [ ] Examples are copy-paste ready148- [ ] Covers common use cases149- [ ] Anticipates edge cases150- [ ] References external docs where helpful151152## Example: Creating a New Skill153154### Step 1: Define the Skill155156```157Name: api-rate-limiter158Category: backend159Purpose: Implement rate limiting for APIs160Triggers: "add rate limiting", "protect API", "throttle requests"161```162163### Step 2: Create Folder Structure164165```bash166mkdir -p backend/api-rate-limiter167touch "backend/api-rate-limiter/SKILL.md"168```169170### Step 3: Write SKILL.md171172```markdown173---174name: api-rate-limiter175description: Implements rate limiting for APIs using token bucket, sliding window, or fixed window algorithms. Use when users request "add rate limiting", "protect API from abuse", or "throttle requests".176---177178# API Rate Limiter179180Protect your APIs from abuse with production-ready rate limiting.181182## Core Workflow183184...185```186187### Step 4: Add References (if needed)188189```bash190mkdir -p backend/api-rate-limiter/references191touch backend/api-rate-limiter/references/algorithms.md192```193194## Output Checklist195196When creating a new skill:197198- [ ] Skill name is kebab-case199- [ ] Description includes trigger phrases200- [ ] Placed in correct category folder201- [ ] SKILL.md follows template structure202- [ ] Code examples are production-ready203- [ ] Includes Core Workflow section204- [ ] Has Output Checklist section205- [ ] Reference files added if needed206207---208> Converted and distributed by [TomeVault](https://tomevault.io/claim/patricio0312rev) — claim your Tome and manage your conversions.209<!-- tomevault:4.0:skill_md:2026-04-11 -->