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.
What this skill does
# 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: ```bash 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: ```markdown --- 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: 1. **Frontmatter**: `name` is kebab-case, 1-64 chars; `description` is a quoted string with "Use when" clause 2. **Content**: Has "When to Use" section with trigger conditions and at least one usage example 3. **Structure**: SKILL.md is under 5000 words; references and assets are in correct subdirectories 4. **Test**: Invoke the skill with a real use case and confirm expected output ### 4. Package for Distribution (Optional) ```bash 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**: 1. Initialize: `init_skill.py release-notes-generator --path ~/.claude/skills/` 2. Add templates to `assets/`: `changelog-template.md`, `pr-release-template.md`, `slack-template.md` 3. Add rules to `references/`: `tech-to-product-mappings.md` 4. Complete `SKILL.md` with usage instructions 5. Validate: check frontmatter, test with a real commit range 6. 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
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.