skill-generator
Create new Claude Code skills with proper structure and best practices. Use when the user wants to create a new skill, extend Claude's capabilities, or needs help structuring a SKILL.md file.
What this skill does
# Skill Generator Generate concise, focused Claude Code skills through guided questions. ## Process Follow these steps: ### 1. Understand the Purpose Ask: - "What should this skill help you accomplish?" - "Give me 2-3 concrete examples of when you'd use it" - "What would you say to Claude to trigger this?" ### 2. Recommend Structure Based on use cases: - **Workflow-based**: Sequential steps (pipeline, workflow) - **Task-based**: Distinct operations (toolkit with separate commands) - **Reference/Guidelines**: Standards or specs to follow - **Capabilities-based**: Integrated system with related features ### 3. Recommend Resources (if needed) - **Scripts** (`scripts/`) - for automation or repetitive code - **References** (`references/`) - for API docs, schemas, specs - **Assets** (`assets/`) - for templates or boilerplate Most simple skills don't need resources. ### 4. Generate SKILL.md Create directory and SKILL.md: ```bash # Personal: ~/.claude/skills/[skill-name]/ # Project: .claude/skills/[skill-name]/ ``` **SKILL.md template** (keep it concise - aim for <200 lines): ```yaml --- name: [hyphen-case-name] description: [What it does + when to use + trigger keywords] --- # [Skill Title] [1-2 sentence overview] ## [Main Section] [Core instructions - keep focused] ### [Subsection if needed] [Concrete examples, not lengthy explanations] ``` **Key requirements:** - Description includes what, when, and triggers - Use hyphen-case for name - Keep concise - split long content to references/ - Provide examples over explanations - Validate YAML frontmatter ### 5. Show Result & Usage Present the generated skill concisely and explain how to use it: ``` Created: ~/.claude/skills/[name]/SKILL.md To use: 1. Restart Claude Code 2. Test with: "[example trigger phrase]" To share: Move to .claude/skills/ and commit ``` ## Quick Templates **Workflow-based:** ```markdown ## Workflow ### Step 1: [Action] ### Step 2: [Process] ### Step 3: [Output] ``` **Task-based:** ```markdown ## Tasks ### 1. [Task] [Brief description + example] ### 2. [Task] [Brief description + example] ``` **Reference/Guidelines:** ```markdown ## Guidelines ### [Category] [Standard/spec + example] ``` ## Best Practices **Effective descriptions:** - State what it does + when to use + trigger words - "Extract PDF text, fill forms, merge docs. Use when working with PDFs." - "Helps with data" (too vague) **Keep it concise:** - Aim for <200 lines in SKILL.md - Move details to references/ files - Prefer examples over lengthy explanations **Resource organization:** ``` skill-name/ ├── SKILL.md # Main (required) ├── references/ # Docs (optional) ├── scripts/ # Utils (optional) └── assets/ # Templates (optional) ``` ## Common Issues - **Skill not triggering**: Add more trigger keywords to description - **YAML invalid**: Check `---` markers are on their own lines - **Scripts fail**: `chmod +x scripts/*.py`
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.