skill-creator
Use PROACTIVELY when creating new Claude Code skills from scratch. Automated generation tool following Claudex marketplace standards with intelligent templates, pattern detection, and quality validation. Supports guided creation, quick start templates, clone-and-modify, and validation-only modes. Not for modifying existing skills or non-skill Claude Code configurations.
What this skill does
# Skill Creator Automates creation of Claude Code skills through interactive guidance, template generation, and quality validation. ## When to Use **Trigger Phrases**: - "create a new skill for [purpose]" - "generate a skill called [name]" - "scaffold a [type] skill" - "set up a new skill" **Use Cases**: - Creating new skills from scratch - Following Claudex marketplace standards - Learning skill structure through examples ## Quick Decision Matrix | User Request | Mode | Action | |--------------|------|--------| | "create skill for [purpose]" | Guided | Interactive creation | | "create [type] skill" | Quick Start | Template-based | | "skill like [existing]" | Clone | Copy pattern | | "validate skill" | Validate | Quality check | ## Mode 1: Guided Creation (Default) **Use when**: User wants full guidance and customization **Process**: 1. Gather basic info (name, description, author) 2. Define purpose, category, triggers 3. Assess complexity → determine skill type 4. Customize directory structure 5. Select pattern (mode-based, phase-based, validation, data-processing) 6. Generate files from templates 7. Run quality validation 8. Provide installation and next steps **Workflow**: `workflow/guided-creation.md` ## Mode 2: Quick Start **Use when**: User specifies skill type directly (minimal, standard, complex) **Process**: 1. Confirm skill type 2. Gather minimal required info 3. Generate with standardized defaults 4. Flag ALL customization points **Advantages**: Fast, minimal questions **Trade-off**: More TODO sections to customize ## Mode 3: Clone & Modify **Use when**: User wants to base skill on existing one **Process**: 1. Read existing skill's structure 2. Extract organizational pattern (not content) 3. Generate new skill with same structure 4. Clear example-specific content **Advantages**: Proven structure, familiar patterns ## Mode 4: Validation Only **Use when**: User wants to check existing skill quality **Process**: 1. Read existing skill files 2. Run quality checklist 3. Generate validation report 4. Offer to fix issues automatically **Use Case**: Before submission, after modifications ## Skill Types | Type | Complexity | Directories | Pattern | |------|------------|-------------|---------| | Minimal | Low | SKILL.md, README.md only | phase-based | | Standard | Medium | + data/, examples/ | phase-based or validation | | Complex (mode) | High | + modes/, templates/ | mode-based | | Complex (data) | High | + scripts/, data/ | data-processing | ## Generated Files **Required** (all skills): - `SKILL.md` - Main skill manifest (with YAML frontmatter) - `README.md` - User documentation - `CHANGELOG.md` - Version history **Optional** (based on type): - `modes/` - Mode-specific workflows - `data/` - Reference materials - `examples/` - Example outputs - `templates/` - Reusable templates - `scripts/` - Automation scripts > **Note**: `plugin.json` is NOT required. The marketplace.json is the single source of truth for plugin metadata. ## Quality Validation Validates against `data/quality-checklist.md`: - File existence (all required files) - Syntax (YAML frontmatter, JSON) - Content completeness - Security (no secrets) - Naming conventions (kebab-case) - Quality grade (A-F) ## Success Criteria - [ ] All required files generated (SKILL.md, README.md, CHANGELOG.md) - [ ] Valid YAML frontmatter with `name` and `description` - [ ] `name` matches directory name (Anthropic spec requirement) - [ ] No security issues (no secrets in files) - [ ] Kebab-case naming (lowercase + hyphens only) - [ ] Version 0.1.0 for new skills - [ ] Description includes capabilities AND trigger context - [ ] Quality grade C or better ## Reference Materials ### Templates - `templates/SKILL.md.j2` - Main manifest with frontmatter - `templates/README.md.j2` - User documentation - `templates/CHANGELOG.md.j2` - Version history ### Patterns - `patterns/mode-based.md` - Multi-mode skills - `patterns/phase-based.md` - Sequential workflows - `patterns/validation.md` - Audit skills - `patterns/data-processing.md` - Data analysis ### Reference Data - `data/categories.yaml` - Valid categories - `data/skill-types.yaml` - Type definitions - `data/quality-checklist.md` - Validation criteria ### Examples - `examples/minimal-skill/` - `examples/standard-skill/` - `examples/complex-skill/` ## Quick Commands ```bash # Check existing skills ls ~/.claude/skills/ # View skill structure tree ~/.claude/skills/[skill-name]/ # Validate frontmatter syntax head -20 ~/.claude/skills/[skill-name]/SKILL.md # Run marketplace validation python3 scripts/validate-skills.py ``` ## Error Handling | Error | Solution | |-------|----------| | Name exists | Suggest alternatives or confirm overwrite | | Invalid name | Explain kebab-case, provide corrected suggestion | | Permission denied | Check ~/.claude/skills/ write access | | Template fails | Fallback to manual creation with guidance | --- **Version**: 0.1.0 | **Author**: Connor
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.