skill-creator
Scaffold a new Claude Code skill with SKILL.md, frontmatter, and bundled resources. Use when creating a custom skill, standardizing skill structure across a team, or packaging a skill for distribution.
- License 许可
- MIT
- 最近更新
- 2026-10-18
- Stars
- ★ 0
- Forks
- 2
01 前言 Front Matter
- name
- skill-creator
- effort
- low
- description
- Scaffold a new Claude Code skill with SKILL.md, frontmatter, and bundled resources. Use when creating a custom skill, standardizing skill structure across a team, or packaging a skill for distribution.
- allowed-tools
- Write Bash
02 资源文件 2
- 脚本scripts/init_skill.py5.5 KB
- 脚本scripts/package_skill.py3.9 KB
03 SKILL.md 正文
Skill creator
Generate new Claude Code skills with correct directory structure, YAML frontmatter, and optional bundled resources.
When to use
- Creating a new custom skill for a project
- Standardizing skill structure across a team
- Generating skill templates with scripts, references, and assets
- Packaging skills for distribution
Skill directory structure
skill-name/
├── SKILL.md # Required: Main skill file with YAML frontmatter
├── scripts/ # Optional: Executable code for deterministic tasks
├── references/ # Optional: Documentation loaded contextually
└── assets/ # Optional: Templates, images, boilerplate (not loaded into context)
Workflow
1. Create the skill
Create a new skill called "my-skill-name" in ~/.claude/skills/
Or with a specific purpose:
Create a skill for generating release notes from git commits,
with templates for CHANGELOG.md and Slack announcements
Or via the initialization script:
python3 ~/.claude/skills/skill-creator/scripts/init_skill.py <skill-name> --path <output-directory>
2. Generated SKILL.md template
The created SKILL.md follows this structure:
---
name: skill-name
description: "What the skill does. Use when [trigger conditions]."
---
# Skill Name
## When to Use
- Trigger condition 1
- Trigger condition 2
## What This Skill Does
1. **Step 1**: Description
2. **Step 2**: Description
## How to Use
[Usage examples]
## Example
**User**: "Example prompt"
**Output**: [Example output]
3. Validate the skill
After creation, verify:
- Frontmatter:
nameis kebab-case, 1-64 chars;descriptionis a quoted string with "Use when" clause - Content: Has "When to Use" section with trigger conditions and at least one usage example
- Structure: SKILL.md is under 5000 words; references and assets are in correct subdirectories
- Test: Invoke the skill with a real use case and confirm expected output
4. Package for distribution (optional)
python3 ~/.claude/skills/skill-creator/scripts/package_skill.py <path/to/skill-folder> [output-directory]
Organizational patterns
| Pattern | Best For | Structure |
|---|---|---|
| Workflow-Based | Sequential procedures | Step-by-step instructions |
| Task-Based | Multiple operations | Collection of tasks |
| Reference/Guidelines | Standards, specs | Rules and examples |
| Capabilities-Based | Interrelated features | Feature descriptions |
Example: Creating a release notes skill
User: "Create a skill for generating release notes with 3 output formats"
Steps:
- Initialize:
init_skill.py release-notes-generator --path ~/.claude/skills/ - Add templates to
assets/:changelog-template.md,pr-release-template.md,slack-template.md - Add rules to
references/:tech-to-product-mappings.md - Complete
SKILL.mdwith usage instructions - Validate: check frontmatter, test with a real commit range
- Package:
package_skill.py ~/.claude/skills/release-notes-generator
Tips
- Keep SKILL.md under 5000 words for efficient context usage
- Use
references/for domain knowledge that doesn't change often - Put templates in
assets/so they're not auto-loaded into context - Always include a "Use when" clause in the description frontmatter
- Test with real use cases before packaging
04 同仓库更多 Skills
voice-refine
Transform verbose voice input into structured, token-efficient Claude prompts. Use when cleaning up voice memos, dictation output, or speech-to-text transcriptions that contain filler words, repetitions, and unstructured thoughts.
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing
update-threat-db
Delegate threat-intelligence research and updates to AgentSec, then validate the guide and landing mirrors.
token-audit
Audit Claude Code configuration to measure fixed-context token overhead and produce a prioritized action plan. Use when hitting rate limits, experiencing early context compression, or after adding significant config files.
talk-stage6-revision
Produces revision sheets with quick navigation by act, a master concept-to-URL table, Q&A cheat-sheet with 6-10 anticipated questions, glossary, and external resources list. Use when preparing for a talk with Q&A, creating shareable reference material for attendees, or building a safety-net glossary for live delivery.
talk-stage5-script
Produces a complete 5-act pitch with speaker notes, a slide-by-slide specification, and a ready-to-paste Kimi prompt for AI slide generation. Requires validated angle and title from Stage 4. Use when you have a confirmed talk angle and need the full script, slide spec, and AI-generated presentation prompt.