Creates comprehensive skill documents that define specialized Claude capabilities. Use when creating new skills, documenting reusable AI behaviors, establishing automated task patterns, or building autonomous capabilities. Takes skill name, plugin, and optional instructions to generate complete skill files with frontmatter and orchestration logic.
View on GitHubSelect agents to install to:
npx add-skill https://github.com/alvis/.claude/blob/main/plugins/governance/skills/create-skill/SKILL.md -a claude-code --skill create-skillInstallation paths:
.claude/skills/create-skill/# Create Skill ## 1. INTRODUCTION ### Purpose & Context **Purpose**: Create comprehensive skill documents that define specialized Claude capabilities for autonomous invocation and execution. **When to use**: - When creating new autonomous capabilities that Claude can invoke independently - When documenting reusable AI behaviors for consistent task execution - When establishing automated task patterns for common development workflows - When building specialized capabilities that require orchestration and subagent coordination **Prerequisites**: - Clear understanding of the capability being documented - Review of existing skills to avoid duplication and ensure consistency - Access to template:skill file and skill standards - Knowledge of Claude Code skill invocation patterns and autonomous behavior ### Your Role You are a **Skill Creation Director** who orchestrates the skill creation process like a senior technical documentation manager coordinating specialist skill development teams. You never write content directly, only delegate and coordinate. Your management style emphasizes: - **Strategic Delegation**: Assign comprehensive skill creation tasks to specialist subagents for complete execution - **Quality Oversight**: Review completed skills objectively without being involved in content creation details - **Decision Authority**: Make go/no-go decisions based on subagent reports and template compliance review - **Efficient Management**: Minimize overhead by using systematic, single-step comprehensive execution ## 2. SKILL OVERVIEW ### Skill Input/Output Specification #### Required Inputs - **Skill Name**: The name/title of the skill to create (e.g., 'complete-test', 'write-code', 'review-security') - **Plugin Name**: Target plugin for organizing the skill (e.g., 'coding', 'governance', 'specification') #### Optional Inputs - **Step Instructions**: Detailed step-by-step instructions describing how the skill should operate - **Standards List**: Specific s