claude-mpm 4.20.3__py3-none-any.whl → 4.25.10__py3-none-any.whl

claude_mpm/skills/bundled/main/skill-creator/SKILL.md

@@ -2,208 +2,188 @@
 name: skill-creator
 description: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
 license: Complete terms in LICENSE.txt
+progressive_disclosure:
+  entry_point:
+    summary: "Create modular skills that extend Claude with specialized knowledge, workflows, and tools through structured components"
+    when_to_use: "When users want to create or update skills with specialized domain knowledge, workflows, or tool integrations. Focus on progressive disclosure for skills >150 lines."
+    quick_start: "1. Understand skill with concrete examples 2. Plan reusable components (scripts/references/assets) 3. Initialize with init_skill.py 4. Edit SKILL.md and resources 5. Package and validate 6. Iterate based on usage"
+  references:
+    - skill-structure.md
+    - creation-workflow.md
+    - progressive-disclosure.md
+    - best-practices.md
+    - examples.md
 ---
 
 # Skill Creator
 
-This skill provides guidance for creating effective skills.
+## Overview
 
-## About Skills
+Create effective skills that extend Claude's capabilities through specialized knowledge, workflows, and tools. Skills are modular packages that transform Claude from a general-purpose agent into a specialized agent with procedural knowledge for specific domains.
 
-Skills are modular, self-contained packages that extend Claude's capabilities by providing
-specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific
-domains or tasks—they transform Claude from a general-purpose agent into a specialized agent
-equipped with procedural knowledge that no model can fully possess.
+**This skill exemplifies its own teachings** by using progressive disclosure to keep the entry point lean while providing deep detail in reference files.
 
-### What Skills Provide
+## When to Use This Skill
 
-1. Specialized workflows - Multi-step procedures for specific domains
-2. Tool integrations - Instructions for working with specific file formats or APIs
-3. Domain expertise - Company-specific knowledge, schemas, business logic
-4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks
+Activate when:
+- Creating a new skill from scratch
+- Updating or refactoring an existing skill
+- Adding progressive disclosure to monolithic skills
+- Understanding skill structure and best practices
+- Planning skill components (scripts, references, assets)
+- Packaging skills for distribution
 
-### Anatomy of a Skill
+## Core Principles
 
-Every skill consists of a required SKILL.md file and optional bundled resources:
+1. **Example-Driven Design**: Start with concrete usage examples, not abstract concepts
+2. **Progressive Disclosure**: Keep entry point <200 lines (optimal: 140-160), detailed content in references
+3. **Reusable Components**: Extract scripts for repeated code, references for knowledge, assets for templates
+4. **Imperative Voice**: Use verb-first instructions throughout (not second person)
+5. **Purpose-Built Resources**: Each component should solve specific repetitive needs
 
-```
-skill-name/
-├── SKILL.md (required)
-│   ├── YAML frontmatter metadata (required)
-│   │   ├── name: (required)
-│   │   └── description: (required)
-│   └── Markdown instructions (required)
-└── Bundled Resources (optional)
-    ├── scripts/          - Executable code (Python/Bash/etc.)
-    ├── references/       - Documentation intended to be loaded into context as needed
-    └── assets/           - Files used in output (templates, icons, fonts, etc.)
-```
-
-#### SKILL.md (required)
-
-**Metadata Quality:** The `name` and `description` in YAML frontmatter determine when Claude will use the skill. Be specific about what the skill does and when to use it. Use the third-person (e.g. "This skill should be used when..." instead of "Use this skill when...").
-
-#### Bundled Resources (optional)
-
-##### Scripts (`scripts/`)
-
-Executable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten.
-
-- **When to include**: When the same code is being rewritten repeatedly or deterministic reliability is needed
-- **Example**: `scripts/rotate_pdf.py` for PDF rotation tasks
-- **Benefits**: Token efficient, deterministic, may be executed without loading into context
-- **Note**: Scripts may still need to be read by Claude for patching or environment-specific adjustments
-
-##### References (`references/`)
-
-Documentation and reference material intended to be loaded as needed into context to inform Claude's process and thinking.
-
-- **When to include**: For documentation that Claude should reference while working
-- **Examples**: `references/finance.md` for financial schemas, `references/mnda.md` for company NDA template, `references/policies.md` for company policies, `references/api_docs.md` for API specifications
-- **Use cases**: Database schemas, API documentation, domain knowledge, company policies, detailed workflow guides
-- **Benefits**: Keeps SKILL.md lean, loaded only when Claude determines it's needed
-- **Best practice**: If files are large (>10k words), include grep search patterns in SKILL.md
-- **Avoid duplication**: Information should live in either SKILL.md or references files, not both. Prefer references files for detailed information unless it's truly core to the skill—this keeps SKILL.md lean while making information discoverable without hogging the context window. Keep only essential procedural instructions and workflow guidance in SKILL.md; move detailed reference material, schemas, and examples to references files.
-
-##### Assets (`assets/`)
-
-Files not intended to be loaded into context, but rather used within the output Claude produces.
-
-- **When to include**: When the skill needs files that will be used in the final output
-- **Examples**: `assets/logo.png` for brand assets, `assets/slides.pptx` for PowerPoint templates, `assets/frontend-template/` for HTML/React boilerplate, `assets/font.ttf` for typography
-- **Use cases**: Templates, images, icons, boilerplate code, fonts, sample documents that get copied or modified
-- **Benefits**: Separates output resources from documentation, enables Claude to use files without loading them into context
-
-### Progressive Disclosure Design Principle
-
-Skills use a three-level loading system to manage context efficiently:
-
-1. **Metadata (name + description)** - Always in context (~100 words)
-2. **SKILL.md body** - When skill triggers (<5k words)
-3. **Bundled resources** - As needed by Claude (Unlimited*)
+## What Skills Provide
 
-*Unlimited because scripts can be executed without reading into context window.
+**Four Core Capabilities:**
+1. **Specialized workflows** - Multi-step procedures for specific domains
+2. **Tool integrations** - Instructions for working with file formats or APIs
+3. **Domain expertise** - Company-specific knowledge, schemas, business logic
+4. **Bundled resources** - Scripts, references, and assets for complex tasks
 
-## Skill Creation Process
+**Three-Level Loading System:**
+1. Metadata (name + description) - Always in context (~100 words)
+2. SKILL.md body - When skill triggers (<200 lines, optimal: 140-160)
+3. Bundled resources - As needed by Claude (unlimited)
 
-To create a skill, follow the "Skill Creation Process" in order, skipping steps only if there is a clear reason why they are not applicable.
+## Quick Start
 
-### Step 1: Understanding the Skill with Concrete Examples
+### Six-Step Creation Process
 
-Skip this step only when the skill's usage patterns are already clearly understood. It remains valuable even when working with an existing skill.
+**Step 1: Understand with Concrete Examples**
+Gather 3-5 realistic usage examples. Ask: "What would users say to trigger this skill?" and "What tasks should it accomplish?" → [Complete guide](./references/creation-workflow.md#step-1-understanding-the-skill-with-concrete-examples)
 
-To create an effective skill, clearly understand concrete examples of how the skill will be used. This understanding can come from either direct user examples or generated examples that are validated with user feedback.
+**Step 2: Plan Reusable Components**
+Analyze examples to identify: scripts (repeated code), references (domain knowledge), assets (templates). → [Planning guide](./references/creation-workflow.md#step-2-planning-the-reusable-skill-contents)
 
-For example, when building an image-editor skill, relevant questions include:
+**Step 3: Initialize Skill**
+Run `scripts/init_skill.py <skill-name> --path <output-directory>` to generate template structure. → [Initialization details](./references/creation-workflow.md#step-3-initializing-the-skill)
 
-- "What functionality should the image-editor skill support? Editing, rotating, anything else?"
-- "Can you give some examples of how this skill would be used?"
-- "I can imagine users asking for things like 'Remove the red-eye from this image' or 'Rotate this image'. Are there other ways you imagine this skill being used?"
-- "What would a user say that should trigger this skill?"
+**Step 4: Edit Skill**
+Implement scripts/references/assets, then update SKILL.md using imperative voice. Apply progressive disclosure if >150 lines. → [Editing guide](./references/creation-workflow.md#step-4-edit-the-skill)
 
-To avoid overwhelming users, avoid asking too many questions in a single message. Start with the most important questions and follow up as needed for better effectiveness.
+**Step 5: Package and Validate**
+Run `scripts/package_skill.py <path/to/skill-folder>` to validate and create distributable zip. → [Packaging guide](./references/creation-workflow.md#step-5-packaging-a-skill)
 
-Conclude this step when there is a clear sense of the functionality the skill should support.
+**Step 6: Iterate**
+Use on real tasks, notice struggles, update skill accordingly. → [Iteration guide](./references/creation-workflow.md#step-6-iterate)
 
-### Step 2: Planning the Reusable Skill Contents
+## Skill Anatomy
 
-To turn concrete examples into an effective skill, analyze each example by:
-
-1. Considering how to execute on the example from scratch
-2. Identifying what scripts, references, and assets would be helpful when executing these workflows repeatedly
-
-Example: When building a `pdf-editor` skill to handle queries like "Help me rotate this PDF," the analysis shows:
-
-1. Rotating a PDF requires re-writing the same code each time
-2. A `scripts/rotate_pdf.py` script would be helpful to store in the skill
-
-Example: When designing a `frontend-webapp-builder` skill for queries like "Build me a todo app" or "Build me a dashboard to track my steps," the analysis shows:
-
-1. Writing a frontend webapp requires the same boilerplate HTML/React each time
-2. An `assets/hello-world/` template containing the boilerplate HTML/React project files would be helpful to store in the skill
-
-Example: When building a `big-query` skill to handle queries like "How many users have logged in today?" the analysis shows:
-
-1. Querying BigQuery requires re-discovering the table schemas and relationships each time
-2. A `references/schema.md` file documenting the table schemas would be helpful to store in the skill
-
-To establish the skill's contents, analyze each concrete example to create a list of the reusable resources to include: scripts, references, and assets.
-
-### Step 3: Initializing the Skill
+```
+skill-name/
+├── SKILL.md (required)           # Entry point with frontmatter + markdown
+├── scripts/ (optional)           # Executable code (Python/Bash)
+├── references/ (optional)        # Documentation loaded as needed
+└── assets/ (optional)            # Templates, images, files for output
+```
 
-At this point, it is time to actually create the skill.
+**Component Guidelines:**
+- **Scripts**: When same code is repeatedly rewritten or deterministic execution needed
+- **References**: For detailed specs, workflows, schemas, API docs (150-500 lines each)
+- **Assets**: For templates, boilerplate, images, fonts used in outputs
+- **Entry Point**: Core workflow, navigation, reminders (140-160 lines optimal)
 
-Skip this step only if the skill being developed already exists, and iteration or packaging is needed. In this case, continue to the next step.
+→ [Complete structure guide](./references/skill-structure.md)
 
-When creating a new skill from scratch, always run the `init_skill.py` script. The script conveniently generates a new template skill directory that automatically includes everything a skill requires, making the skill creation process much more efficient and reliable.
+## Progressive Disclosure Pattern
 
-Usage:
+**When to apply:** Skills >150 lines total
 
-```bash
-scripts/init_skill.py <skill-name> --path <output-directory>
-```
+**Implementation:**
+1. Add `progressive_disclosure` frontmatter with summary, when_to_use, quick_start
+2. Reduce entry point to 140-160 lines (core workflow + navigation)
+3. Create 3-5 reference files (150-500 lines each)
+4. Organize by topic: structure, workflow, best practices, examples
+5. Add navigation section linking all references
 
-The script:
+**Benefits:**
+- Entry loads only essential content
+- Deep detail available when needed
+- Better organization and maintainability
+- 20-30% reduction in entry point size
 
-- Creates the skill directory at the specified path
-- Generates a SKILL.md template with proper frontmatter and TODO placeholders
-- Creates example resource directories: `scripts/`, `references/`, and `assets/`
-- Adds example files in each directory that can be customized or deleted
+→ [Complete progressive disclosure guide](./references/progressive-disclosure.md)
 
-After initialization, customize or remove the generated SKILL.md and example files as needed.
+**Meta-example:** This skill-creator demonstrates progressive disclosure:
+- Entry: 150 lines (28% reduction from 209)
+- References: 5 files with complete implementation details
+- Recently optimized: mcp-builder (160 lines), testing-anti-patterns (140 lines)
 
-### Step 4: Edit the Skill
+## Navigation
 
-When editing the (newly-generated or existing) skill, remember that the skill is being created for another instance of Claude to use. Focus on including information that would be beneficial and non-obvious to Claude. Consider what procedural knowledge, domain-specific details, or reusable assets would help another Claude instance execute these tasks more effectively.
+### Core Concepts
+- **[🏗️ Skill Structure](./references/skill-structure.md)** - Anatomy, components (scripts/references/assets), progressive disclosure architecture. Load when planning skill layout or understanding resource types.
 
-#### Start with Reusable Skill Contents
+### Step-by-Step Process
+- **[🔄 Creation Workflow](./references/creation-workflow.md)** - Complete 6-step process from examples to iteration. Load when creating new skill or following structured workflow.
 
-To begin implementation, start with the reusable resources identified above: `scripts/`, `references/`, and `assets/` files. Note that this step may require user input. For example, when implementing a `brand-guidelines` skill, the user may need to provide brand assets or templates to store in `assets/`, or documentation to store in `references/`.
+### Design Patterns
+- **[📊 Progressive Disclosure](./references/progressive-disclosure.md)** - Three-level loading, implementation guide, anti-patterns, examples. Load when refactoring skills >150 lines or optimizing context usage.
 
-Also, delete any example files and directories not needed for the skill. The initialization script creates example files in `scripts/`, `references/`, and `assets/` to demonstrate structure, but most skills won't need all of them.
+### Quality Standards
+- **[✅ Best Practices](./references/best-practices.md)** - Writing style, metadata quality, content organization, anti-patterns. Load when writing/reviewing skill content or ensuring quality.
 
-#### Update SKILL.md
+### Real-World Examples
+- **[📚 Examples](./references/examples.md)** - Complete skill examples: mcp-builder, testing-anti-patterns, pdf-editor, brand-guidelines, database-builder, frontend-builder. Load when starting new skill or seeking patterns.
 
-**Writing Style:** Write the entire skill using **imperative/infinitive form** (verb-first instructions), not second person. Use objective, instructional language (e.g., "To accomplish X, do Y" rather than "You should do X" or "If you need to do X"). This maintains consistency and clarity for AI consumption.
+## Key Reminders
 
-To complete SKILL.md, answer the following questions:
+- **Start with examples** - 3-5 concrete usage scenarios before designing
+- **Use init script** - `scripts/init_skill.py` creates proper structure automatically
+- **Imperative voice** - "To accomplish X, do Y" (not "You should do X")
+- **Progressive disclosure** - Entry <200 lines, details in references (for skills >150 lines)
+- **Avoid duplication** - Information lives in ONE place (entry summary, reference detail)
+- **Component clarity** - Scripts for code, references for knowledge, assets for templates
+- **Validate before sharing** - `scripts/package_skill.py` validates and packages
+- **Iterate continuously** - Use on real tasks, update based on struggles
 
-1. What is the purpose of the skill, in a few sentences?
-2. When should the skill be used?
-3. In practice, how should Claude use the skill? All reusable skill contents developed above should be referenced so that Claude knows how to use them.
+## Red Flags - STOP
 
-### Step 5: Packaging a Skill
+If you catch yourself:
+- "Let me write all the details in SKILL.md" → Move to references (progressive disclosure)
+- "I'll use second person" → Switch to imperative voice
+- "Same information in entry and reference" → Delete duplication
+- Using generic description → Be specific about activation conditions
+- Leaving example files from init script → Delete unused resources
+- Skipping validation → Always run package_skill.py before sharing
+- Creating skill without examples → Gather concrete usage scenarios first
+- Entry point >200 lines → Apply progressive disclosure pattern
 
-Once the skill is ready, it should be packaged into a distributable zip file that gets shared with the user. The packaging process automatically validates the skill first to ensure it meets all requirements:
+**ALL of these mean: STOP. Review principles and references.**
 
-```bash
-scripts/package_skill.py <path/to/skill-folder>
-```
+## Integration with Other Skills
 
-Optional output directory specification:
+**Meta-Skills:**
+- **skill-creator** (this skill) - Creates other skills, demonstrates its own patterns
 
-```bash
-scripts/package_skill.py <path/to/skill-folder> ./dist
-```
-
-The packaging script will:
+**Development Skills:**
+- **mcp-builder** - Example of progressive disclosure implementation
+- **testing-anti-patterns** - Example of ultra-lean entry point (140 lines)
 
-1. **Validate** the skill automatically, checking:
-   - YAML frontmatter format and required fields
-   - Skill naming conventions and directory structure
-   - Description completeness and quality
-   - File organization and resource references
+**Workflow Skills:**
+- **documentation** - Writing clear, structured content
+- **verification-before-completion** - Testing skills before packaging
 
-2. **Package** the skill if validation passes, creating a zip file named after the skill (e.g., `my-skill.zip`) that includes all files and maintains the proper directory structure for distribution.
+## Real-World Impact
 
-If validation fails, the script will report the errors and exit without creating a package. Fix any validation errors and run the packaging command again.
+From skill optimization experience:
+- Progressive disclosure: 20-30% reduction in entry point size
+- mcp-builder: 209 → 160 lines (23% reduction, 6 references)
+- testing-anti-patterns: → 140 lines (ultra-lean with 4 references)
+- skill-creator: 209 → 150 lines (28% reduction, 5 references)
+- Context efficiency: Load only needed references (saves 50-80% context)
+- Maintainability: Update specific references without touching entry point
+- Clarity: Better organization improves discoverability and comprehension
 
-### Step 6: Iterate
-
-After testing the skill, users may request improvements. Often this happens right after using the skill, with fresh context of how the skill performed.
+---
 
-**Iteration workflow:**
-1. Use the skill on real tasks
-2. Notice struggles or inefficiencies
-3. Identify how SKILL.md or bundled resources should be updated
-4. Implement changes and test again
+**Remember:** Skills are modular packages that transform Claude into a specialized agent. Apply progressive disclosure for skills >150 lines. This skill demonstrates the pattern it teaches.