Loading...
Loading...
Provides guidance for creating effective Claude Code skills with proper YAML frontmatter, directory structure, and best practices. Activates when the user mentions "create skill", "new skill", "スキル作成", "SKILL.md", "skill development".
npx skill4agent add yusuketsunoda/ppt-trans claude-skill-creatorPersonal: ~/.claude/skills/skill-name/SKILL.md
Project: .claude/skills/skill-name/SKILL.md
Plugin: Bundled with the packagemkdir -p .claude/skills/my-skill-name---
name: skill-identifier # Required: Only lowercase letters, numbers, hyphens, max 64 characters
description: What it does + when to use it # Required: Max 1024 characters, include trigger keywords
allowed-tools: Read, Grep, Edit # Optional: Tool restrictions
---api-docs-writerdb-migration-helper# ✅ GOOD
description: Assists with creating, debugging, and fixing failed E2E tests. Used when Playwright tests fail or when creating new tests.
# ❌ BAD
description: Helps with tests# Skill Title
Overview (1-2 sentences)
## When to Use This Skill
- Scenario 1
- Scenario 2
## Instructions
1. **Step 1**: First thing to do
2. **Step 2**: Next thing to do
3. **Step 3**: Final thing to do
## Examples
### Example 1: [Scenario]
[Code example]
## Troubleshooting
**Issue**: Problem
**Solution**: Resolution
## AI Assistant Instructions
When this skill is activated:
1. First, check ○○
2. Next, execute ○○
Always:
- Always ○○
Never:
- Never ○○allowed-tools: Read, Grep, Glob # Read-onlymy-skill-name/
├── SKILL.md # Main file (required, max 500 lines)
├── reference.md # Detailed reference (loaded when needed)
└── templates/ # TemplatesFor details, refer to [reference.md](reference.md).# ✅ DO
- api-docs-writer: API documentation generation
- test-strategy: Test implementation
# ❌ DON'T
- developer-helper: Everything (vague)# ✅ GOOD
description: Generate OpenAPI/Swagger documentation from Express/FastAPI. Used when creating API documentation.
# ❌ BAD
description: Helps with API documentation## AI Assistant Instructions
When this skill is activated:
1. First, analyze the codebase
2. Ask questions if needed
3. Generate an initial version
Always:
- Use TypeScript for type safety
- Include error handling
Never:
- Don't skip validationmy-skill-name/
├── SKILL.md # Core ( < 500 lines)
├── reference.md # Details (loaded only when needed)
└── examples.md # Extended examples (loaded only when needed)---
name: component-generator
description: Generate React/Vue/Angular components. Used when creating new components.
---
# Component Generator
## Instructions
1. Confirm the component type (React/Vue/Angular)
2. Get the name and props
3. Generate: Component + Tests + Storybook
4. Follow project conventions| Cause | Solution |
|---|---|
| Insufficient trigger keywords | Add specific keywords to the description |
| Invalid name format | Correct to use only lowercase letters, numbers, and hyphens |
| Invalid YAML | Check the |
| Incorrect filename | Standardize to |
| Cause | Solution |
|---|---|
| Description is too broad | Change to more specific keywords |
| Keyword overlap with other skills | Use unique keywords |
| Cause | Solution |
|---|---|
| Instructions are vague | Clarify using numbered steps |
| Missing AI Instructions | Add the section |
# Project skills
git add .claude/skills/skill-name/
git commit -m "feat: add [skill-name] skill"
git push
# Team members can get it with git pull.claude/skills/skill-name/SKILL.md---namedescription