skill-creator
Create new Claude Agent Skills. Use when asked to create, build, or develop a skill.
What this skill does
# Skill Creator ## Overview Guides users through creating well-structured Claude Agent Skills by gathering requirements, generating the skill structure, and producing properly formatted SKILL.md files. ## Instructions When helping create a new skill, follow this workflow: ### Phase 1: Discovery Ask the user about their skill requirements: 1. **Purpose**: "What should this skill help Claude do?" 2. **Trigger**: "When should Claude use this skill? What phrases or requests should activate it?" 3. **Scope**: "What are the boundaries? What should this skill NOT do?" 4. **Examples**: "Can you give me an example input and expected output?" ### Phase 2: Design Based on discovery, determine: 1. **Skill name**: lowercase, hyphens, max 64 chars 2. **Category**: creative, development, enterprise, or document 3. **Description**: clear trigger-focused description (max 1024 chars) 4. **Structure**: simple (SKILL.md only) or advanced (with scripts/templates) ### Phase 3: Generation Create the skill files: 1. Generate `SKILL.md` with proper frontmatter 2. Add clear instructions section 3. Include concrete examples 4. Add guidelines and constraints 5. Create supporting files if needed ### Phase 4: Review Present the generated skill and: 1. Explain each section's purpose 2. Suggest improvements 3. Offer to refine based on feedback ## Output Format ### SKILL.md Template ```yaml --- name: [skill-name] description: [Clear description explaining what this skill does and when Claude should use it] version: 1.0.0 --- # [Skill Name] ## Overview [Brief description of purpose] ## Instructions [Step-by-step guidance for Claude] ## Examples ### Example: [Use Case Name] **Input:** [Example user request] **Output:** [Expected response or action] ## Guidelines [Constraints and best practices] ``` ## Examples ### Example: Create a Code Review Skill **User**: "I want a skill that reviews Python code for best practices" **Response**: Let me help you create a Python code review skill. I have a few questions: 1. Should it focus on any specific aspects (security, performance, style)? 2. What coding standards should it follow (PEP 8, type hints)? 3. Should it suggest fixes or just identify issues? [After gathering requirements, generate the skill] ### Example: Create a Documentation Skill **User**: "Create a skill for writing API documentation" **Response**: I'll help you build an API documentation skill. Let me understand your needs: 1. What format should the docs be in (Markdown, OpenAPI)? 2. Should it include code examples? 3. Any specific sections required (authentication, errors)? ## Guidelines - Always start with discovery questions - Generate complete, working skills - Include realistic examples - Explain design decisions - Offer iteration opportunities - Follow marketplace standards ## Checklist for Generated Skills Before presenting a skill, verify: - [ ] Name follows conventions (lowercase, hyphens, ≤64 chars) - [ ] Description clearly explains trigger conditions - [ ] Instructions are step-by-step and clear - [ ] At least one concrete example included - [ ] Guidelines cover edge cases - [ ] No hardcoded secrets or credentials
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.