ChatGPT Claude Codex CLI Cohere Cursor DeepSeek Gemini GitHub Copilot GLM Grok Kimi Llama MiniMax Mistral OpenAI opencode Skill

skill-creator

To create new CLI skills following Anthropic's official best practices with zero manual configuration. This skill automates brainstorming, template application, validation, and installation processes while maintaining progressive disclosure patterns and writing style standards.

LLM Mart · 0 points · 20 views 37 listing impressions 0 install-command copies

#automation

Download sickn33-agentic-awesome-skills-skills_skill-creator-1f67c44.zip · 22 KB
This skill couldn't be refreshed from GitHub on the last check — you're seeing the last imported snapshot.

Install

skills CLI npx skills add https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/skill-creator
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install sickn33-agentic-awesome-skills@llmmart
Git git clone https://github.com/sickn33/agentic-awesome-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole sickn33/agentic-awesome-skills collection as a plugin from our marketplace. Git is the plain clone.

README

skill-creator

Automate CLI skill creation with best practices built-in.

What It Does

The skill-creator automates the entire workflow of creating new CLI skills for GitHub Copilot CLI and Claude Code. It guides you through brainstorming, applies standardized templates, validates content quality, and handles installation—all while following Anthropic's official best practices.

Key Features

  • 🎯 Interactive Brainstorming - Collaborative session to define skill purpose and scope
  • ✨ Template Automation - Automatic file generation with zero manual configuration
  • 🔍 Quality Validation - Built-in checks for YAML, content quality, and writing style
  • 📦 Flexible Installation - Choose repository-only, global, or hybrid installation
  • 📊 Visual Progress Bar - Real-time progress indicator showing completion status (e.g., [████████████░░░░░░] 60% - Step 3/5)
  • 🔗 Prompt Engineer Integration - Optional enhancement using prompt-engineer skill

When to Use

Use this skill when you want to:

  • Create a new CLI skill following official standards
  • Extend CLI functionality with custom capabilities
  • Package domain knowledge into a reusable skill format
  • Automate repetitive CLI tasks with a custom skill
  • Install skills locally or globally across your system

Installation

Prerequisites

This skill is part of the cli-ai-skills repository. To use it:

# Clone the repository
git clone https://github.com/yourusername/cli-ai-skills.git
cd cli-ai-skills

Install Globally (Recommended)

Install via symlinks to make the skill available everywhere:

# For GitHub Copilot CLI
ln -sf "$(pwd)/.github/skills/skill-creator" ~/.copilot/skills/skill-creator

# For Claude Code
ln -sf "$(pwd)/.claude/skills/skill-creator" ~/.claude/skills/skill-creator

Benefits of global installation:

  • Works in any directory
  • Auto-updates when you git pull the repository
  • No configuration files needed

Repository-Only Installation

If you prefer to use the skill only within this repository, no installation is needed. The skill will be available when working in the cli-ai-skills directory.

Usage

Basic Skill Creation

Simply ask the CLI to create a new skill:

# GitHub Copilot CLI
gh copilot "create a new skill for debugging Python errors"

# Claude Code
claude "create a skill that helps with git workflows"

The skill will guide you through with visual progress tracking:

  1. Brainstorming (20%) - Define purpose, triggers, and type
  2. Prompt Enhancement (40%, optional) - Enhance with prompt-engineer skill
  3. File Generation (60%) - Create files from templates
  4. Validation (80%) - Check quality and standards
  5. Installation (100%) - Choose local, global, or both

Each phase displays a progress bar:

[████████████░░░░░░] 60% - Step 3/5: File Generation

Advanced Usage

Create Code Generation Skill

"Create a code skill that generates React components from descriptions"

The skill will:

  • Use the specialized code-skill-template.md
  • Ask about specific frameworks (React, Vue, etc.)
  • Include code examples in the examples/ folder

Create Documentation Skill

"Build a skill that writes API documentation from code"

The skill will:

  • Use documentation-skill-template.md
  • Ask about documentation formats
  • Set up references for style guides

Install for Specific Platform

"Create a skill for Copilot only that analyzes TypeScript errors"

The skill will:

  • Generate files only in .github/skills/
  • Skip Claude-specific installation
  • Validate against Copilot requirements

Example Walkthrough

Here's what creating a skill looks like:

You: "create a skill for database schema migrations"

[████░░░░░░░░░░░░░░] 20% - Step 1/5: Brainstorming & Planning

What should this skill do?
> Helps users create and manage database schema migrations safely

When should it trigger? (3-5 phrases)
> "create migration", "generate schema change", "migrate database"

What type of skill?
> [×] General purpose

Which platforms?
> [×] Both (Copilot + Claude)

[... continues through all phases ...]

🎉 Skill created successfully!

📦 Skill Name: database-migration
📁 Location: .github/skills/database-migration/
🔗 Installed: Global (Copilot + Claude)

File Structure

When you create a skill, this structure is generated:

.github/skills/your-skill-name/
├── SKILL.md              # Main skill instructions (1.5-2k words)
├── README.md             # User-facing documentation (this file)
├── references/           # Detailed guides (2k-5k words each)
│   └── (empty, ready for extended docs)
├── examples/             # Working code samples
│   └── (empty, ready for examples)
└── scripts/              # Executable utilities
    └── (empty, ready for automation)

Configuration

No configuration needed! This skill uses runtime discovery to:

  • Detect installed platforms (Copilot CLI, Claude Code)
  • Find repository root automatically
  • Extract author info from git config
  • Determine optimal file locations

Validation

Every skill created is automatically validated for:

  • ✅ YAML Frontmatter - Required fields and format
  • ✅ Description Format - Third-person, trigger phrases
  • ✅ Word Count - 1,500-2,000 ideal, under 5,000 max
  • ✅ Writing Style - Imperative form, no second-person
  • ✅ Progressive Disclosure - Proper content organization

Frameworks Used

This skill leverages several established methodologies:

  • Progressive Disclosure - 3-level content hierarchy (metadata → SKILL.md → bundled resources)
  • Bundled Resources Pattern - References, examples, and scripts as separate files
  • Anthropic Best Practices - Official skill development standards
  • Zero-Config Design - Runtime discovery, no hardcoded values
  • Template-Driven Generation - Consistent structure across all skills

Troubleshooting

"Template not found" Error

Ensure you're in the cli-ai-skills repository or have cloned it:

git clone https://github.com/yourusername/cli-ai-skills.git
cd cli-ai-skills

"Platform not detected" Warning

If platforms aren't detected:

  1. Choose "Repository only" installation
  2. Manually specify platform during setup
  3. Install globally later using provided commands

Validation Failures

If validation finds issues:

  • Review suggestions in the output
  • Choose automatic fixes for common problems
  • Manually edit files for complex issues
  • Re-run validation: scripts/validate-skill-yaml.sh .github/skills/your-skill

Advanced Features

Prompt Engineer Integration

Enhance your skill descriptions with AI:

  1. Enable during Phase 2 (Prompt Refinement)
  2. Skill will invoke prompt-engineer automatically
  3. Review enhanced output before proceeding

Bundled Resources

For complex skills, use bundled resources:

  • references/ - Detailed documentation (no word limit)
  • examples/ - Working code samples users can run
  • scripts/ - Automation utilities loaded on demand

Version Management

Update existing skills:

scripts/update-skill-version.sh your-skill-name 1.1.0

Contributing

Created a useful skill? Share it:

  1. Ensure validation passes
  2. Add usage examples
  3. Update main README.md
  4. Submit a pull request

Resources

Support

For issues or questions:

  • Check existing skills in .github/skills/ for examples
  • Review resources/skills-development.md for methodology
  • Open an issue in the repository

Version: 1.1.0 Platform: GitHub Copilot CLI, Claude Code Author: Eric Andrade Last Updated: 2026-02-01

Skill manifest

skill-creator

Purpose

To create new CLI skills following Anthropic's official best practices with zero manual configuration. This skill automates brainstorming, template application, validation, and installation processes while maintaining progressive disclosure patterns and writing style standards.

When to Use This Skill

This skill should be used when:

  • User wants to extend CLI functionality with custom capabilities
  • User needs to create a skill following official standards
  • User wants to automate repetitive CLI tasks with a reusable skill
  • User needs to package domain knowledge into a skill format
  • User wants both local and global skill installation options

Core Capabilities

  1. Interactive Brainstorming - Collaborative session to define skill purpose and scope
  2. Prompt Enhancement - Optional integration with prompt-engineer skill for refinement
  3. Template Application - Automatic file generation from standardized templates
  4. Validation - YAML, content, and style checks against Anthropic standards
  5. Installation - Local repository or global installation with symlinks
  6. Progress Tracking - Visual gauge showing completion status at each step

Step 0: Discovery

Before starting skill creation, gather runtime information:

# Detect available platforms
COPILOT_INSTALLED=false
CLAUDE_INSTALLED=false
CODEX_INSTALLED=false

if command -v gh &>/dev/null && gh copilot --version &>/dev/null 2>&1; then
    COPILOT_INSTALLED=true
fi

if [[ -d "$HOME/.claude" ]]; then
    CLAUDE_INSTALLED=true
fi

if [[ -d "$HOME/.codex" ]]; then
    CODEX_INSTALLED=true
fi

# Determine working directory
REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
SKILLS_REPO="$REPO_ROOT"

# Check if in cli-ai-skills repository
if [[ ! -d "$SKILLS_REPO/.github/skills" ]]; then
    echo "⚠️  Not in cli-ai-skills repository. Creating standalone skill."
    STANDALONE=true
fi

# Get user info from git config
AUTHOR=$(git config user.name || echo "Unknown")
EMAIL=$(git config user.email || echo "")

Key Information Needed:

  • Which platforms to target (Copilot, Claude, Codex, or all three)
  • Installation preference (local, global, or both)
  • Skill name and purpose
  • Skill type (general, code, documentation, analysis)

Main Workflow

Progress Tracking Guidelines

Throughout the workflow, display a visual progress bar before starting each phase to keep the user informed. The progress bar format is:

[████████████░░░░░░] 60% - Step 3/5: Creating SKILL.md

Format specifications:

  • 20 characters wide (use █ for filled, ░ for empty)
  • Percentage based on current step (Step 1=20%, Step 2=40%, Step 3=60%, Step 4=80%, Step 5=100%)
  • Step counter showing current/total (e.g., "Step 3/5")
  • Brief description of current phase

Display the progress bar using:

echo "[████░░░░░░░░░░░░░░] 20% - Step 1/5: Brainstorming & Planning"

Phase 1: Brainstorming & Planning

Progress: Display before starting this phase:

echo "[████░░░░░░░░░░░░░░] 20% - Step 1/5: Brainstorming & Planning"

Display progress:

╔══════════════════════════════════════════════════════════════╗
║     🛠️  SKILL CREATOR - Creating New Skill                  ║
╠══════════════════════════════════════════════════════════════╣
║ → Phase 1: Brainstorming                 [10%]               ║
║ ○ Phase 2: Prompt Refinement                                 ║
║ ○ Phase 3: File Generation                                   ║
║ ○ Phase 4: Validation                                        ║
║ ○ Phase 5: Installation                                      ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: ███░░░░░░░░░░░░░░░░░░░░░░░░░░░  10%              ║
╚══════════════════════════════════════════════════════════════╝

Ask the user:

  1. What should this skill do? (Free-form description)

    • Example: "Help users debug Python code by analyzing stack traces"
  2. When should it trigger? (Provide 3-5 trigger phrases)

    • Example: "debug Python error", "analyze stack trace", "fix Python exception"
  3. What type of skill is this?

    • General purpose (default template)
    • Code generation/modification
    • Documentation creation/maintenance
    • Analysis/investigation
  4. Which platforms should support this skill?

    • GitHub Copilot CLI
    • Claude Code
    • Codex
    • All three (recommended)
  5. Provide a one-sentence description (will appear in metadata)

    • Example: "Analyzes Python stack traces and suggests fixes"

Capture responses and prepare for next phase.

Phase 2: Prompt Enhancement (Optional)

Progress: Display before starting this phase:

echo "[████████░░░░░░░░░░] 40% - Step 2/5: Prompt Enhancement"

Update progress:

╔══════════════════════════════════════════════════════════════╗
║ ✓ Phase 1: Brainstorming                                     ║
║ → Phase 2: Prompt Refinement             [30%]               ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: █████████░░░░░░░░░░░░░░░░░░░░░  30%              ║
╚══════════════════════════════════════════════════════════════╝

Ask the user: "Would you like to refine the skill description using the prompt-engineer skill?"

  • Yes - Use prompt-engineer to enhance clarity and structure
  • No - Proceed with current description

If Yes:

  1. Check if prompt-engineer skill is available
  2. Invoke with current description as input
  3. Review enhanced output with user
  4. Ask: "Accept enhanced version or keep original?"

If No or prompt-engineer unavailable:

  • Proceed with original user input

Phase 3: File Generation

Progress: Display before starting this phase:

echo "[████████████░░░░░░] 60% - Step 3/5: File Generation"

Update progress:

╔══════════════════════════════════════════════════════════════╗
║ ✓ Phase 1: Brainstorming                                     ║
║ ✓ Phase 2: Prompt Refinement                                 ║
║ → Phase 3: File Generation               [50%]               ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: ███████████████░░░░░░░░░░░░░░░  50%              ║
╚══════════════════════════════════════════════════════════════╝

Generate skill structure:

# Convert skill name to kebab-case
SKILL_NAME=$(echo "$USER_INPUT" | tr '[:upper:]' '[:lower:]' | tr ' ' '-')

# Create directories
if [[ "$PLATFORM" =~ "copilot" ]]; then
    mkdir -p ".github/skills/$SKILL_NAME"/{references,examples,scripts}
fi

if [[ "$PLATFORM" =~ "claude" ]]; then
    mkdir -p ".claude/skills/$SKILL_NAME"/{references,examples,scripts}
fi

if [[ "$PLATFORM" =~ "codex" ]]; then
    mkdir -p ".codex/skills/$SKILL_NAME"/{references,examples,scripts}
fi

Apply templates:

  1. SKILL.md - Use appropriate template:

    • skill-template-copilot.md, skill-template-claude.md, or skill-template-codex.md
    • Substitute placeholders:
      • {{SKILL_NAME}} → kebab-case name
      • {{DESCRIPTION}} → one-line description
      • {{TRIGGERS}} → comma-separated trigger phrases
      • {{PURPOSE}} → detailed purpose from brainstorming
      • {{AUTHOR}} → from git config
      • {{DATE}} → current date (YYYY-MM-DD)
      • {{VERSION}} → "1.0.0"
  2. README.md - Use readme-template.md:

    • User-facing documentation (300-500 words)
    • Include installation instructions
    • Add usage examples
  3. References/ (optional but recommended):

    • Create detailed-guide.md for extended documentation (2k-5k words)
    • Move lengthy content here to keep SKILL.md under 2k words

File creation commands:

# Apply template with substitution
sed "s/{{SKILL_NAME}}/$SKILL_NAME/g; \
     s/{{DESCRIPTION}}/$DESCRIPTION/g; \
     s/{{AUTHOR}}/$AUTHOR/g; \
     s/{{DATE}}/$(date +%Y-%m-%d)/g" \
    resources/templates/skill-template-copilot.md \
    > ".github/skills/$SKILL_NAME/SKILL.md"

# Create README
sed "s/{{SKILL_NAME}}/$SKILL_NAME/g" \
    resources/templates/readme-template.md \
    > ".github/skills/$SKILL_NAME/README.md"

# Apply template for Codex if selected
if [[ "$PLATFORM" =~ "codex" ]]; then
    sed "s/{{SKILL_NAME}}/$SKILL_NAME/g; \
         s/{{DESCRIPTION}}/$DESCRIPTION/g; \
         s/{{AUTHOR}}/$AUTHOR/g; \
         s/{{DATE}}/$(date +%Y-%m-%d)/g" \
        resources/templates/skill-template-codex.md \
        > ".codex/skills/$SKILL_NAME/SKILL.md"

    sed "s/{{SKILL_NAME}}/$SKILL_NAME/g" \
        resources/templates/readme-template.md \
        > ".codex/skills/$SKILL_NAME/README.md"
fi

Display created structure:

✅ Created:
   .github/skills/your-skill-name/ (if Copilot selected)
   .claude/skills/your-skill-name/ (if Claude selected)
   .codex/skills/your-skill-name/ (if Codex selected)
   ├── SKILL.md (832 lines)
   ├── README.md (347 lines)
   ├── references/
   ├── examples/
   └── scripts/

Phase 4: Validation

Progress: Display before starting this phase:

echo "[████████████████░░] 80% - Step 4/5: Validation"

Update progress:

╔══════════════════════════════════════════════════════════════╗
║ ✓ Phase 3: File Generation                                   ║
║ → Phase 4: Validation                    [70%]               ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: █████████████████████░░░░░░░░░  70%              ║
╚══════════════════════════════════════════════════════════════╝

Run validation scripts:

# Validate YAML frontmatter
scripts/validate-skill-yaml.sh ".github/skills/$SKILL_NAME"

# Validate content quality
scripts/validate-skill-content.sh ".github/skills/$SKILL_NAME"

Expected output:

🔍 Validating YAML frontmatter...
✅ YAML frontmatter valid!

🔍 Validating content...
✅ Word count excellent: 1847 words
✅ Content validation complete!

If validation fails:

  • Display specific errors
  • Offer to fix automatically (common issues)
  • Ask user to manually correct complex issues

Common auto-fixes:

  • Convert second-person to imperative form
  • Reformat description to third-person
  • Add missing required fields

Phase 5: Installation

Progress: Display before starting this phase:

echo "[████████████████████] 100% - Step 5/5: Installation"

Update progress:

╔══════════════════════════════════════════════════════════════╗
║ ✓ Phase 4: Validation                                        ║
║ → Phase 5: Installation                  [90%]               ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: ██████████████████████████░░░░░  90%              ║
╚══════════════════════════════════════════════════════════════╝

Ask the user: "How would you like to install this skill?"

  • Repository only - Files created in .github/skills/ (works when in repo)
  • Global installation - Create symlinks in ~/.copilot/skills/ (works everywhere)
  • Both - Repository + global symlinks (recommended, auto-updates with git pull)
  • Skip installation - Just create files

If global installation selected:

# Detect which platforms to install for
INSTALL_TARGETS=()

if [[ "$COPILOT_INSTALLED" == "true" ]] && [[ "$PLATFORM" =~ "copilot" ]]; then
    INSTALL_TARGETS+=("copilot")
fi

if [[ "$CLAUDE_INSTALLED" == "true" ]] && [[ "$PLATFORM" =~ "claude" ]]; then
    INSTALL_TARGETS+=("claude")
fi

if [[ "$CODEX_INSTALLED" == "true" ]] && [[ "$PLATFORM" =~ "codex" ]]; then
    INSTALL_TARGETS+=("codex")
fi

# Ask user to confirm detected platforms
echo "Detected platforms: ${INSTALL_TARGETS[*]}"
echo "Install for these platforms? [Y/n]"

Installation process:

# GitHub Copilot CLI
if [[ " ${INSTALL_TARGETS[*]} " =~ " copilot " ]]; then
    ln -sf "$SKILLS_REPO/.github/skills/$SKILL_NAME" \
           "$HOME/.copilot/skills/$SKILL_NAME"
    echo "✅ Installed for GitHub Copilot CLI"
fi

# Claude Code
if [[ " ${INSTALL_TARGETS[*]} " =~ " claude " ]]; then
    ln -sf "$SKILLS_REPO/.claude/skills/$SKILL_NAME" \
           "$HOME/.claude/skills/$SKILL_NAME"
    echo "✅ Installed for Claude Code"
fi

# Codex
if [[ " ${INSTALL_TARGETS[*]} " =~ " codex " ]]; then
    ln -sf "$SKILLS_REPO/.codex/skills/$SKILL_NAME" \
           "$HOME/.codex/skills/$SKILL_NAME"
    echo "✅ Installed for Codex"
fi

Verify installation:

# Check symlinks
ls -la ~/.copilot/skills/$SKILL_NAME 2>/dev/null
ls -la ~/.claude/skills/$SKILL_NAME 2>/dev/null
ls -la ~/.codex/skills/$SKILL_NAME 2>/dev/null

Phase 6: Completion

Progress: Display completion message:

echo "[████████████████████] 100% - ✓ Skill created successfully!"

Update progress:

╔══════════════════════════════════════════════════════════════╗
║ ✓ Phase 5: Installation                                      ║
║ ✅ SKILL CREATION COMPLETE!                                  ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: ██████████████████████████████  100%              ║
╚══════════════════════════════════════════════════════════════╝

Display summary:

🎉 Skill created successfully!

📦 Skill Name: your-skill-name
📁 Location: .github/skills/your-skill-name/
🔗 Installed: Global (Copilot + Claude)

📋 Files Created:
   ✅ SKILL.md (1,847 words)
   ✅ README.md (423 words)
   ✅ references/ (empty, ready for extended docs)
   ✅ examples/ (empty, ready for code samples)
   ✅ scripts/ (empty, ready for utilities)

🚀 Next Steps:
   1. Test the skill: Try trigger phrases in CLI
   2. Add examples: Create working code samples in examples/
   3. Extend docs: Add detailed guides to references/
   4. Commit changes: git add .github/skills/your-skill-name && git commit
   5. Share: Push to repository for team use

💡 Pro Tips:
   - Keep SKILL.md under 2,000 words (currently: 1,847)
   - Move detailed content to references/ folder
   - Add executable scripts to scripts/ folder
   - Update README.md with real usage examples
   - Run validation before committing: scripts/validate-skill-yaml.sh

Error Handling

Platform Detection Issues

If platforms cannot be detected:

⚠️  Unable to detect GitHub Copilot CLI or Claude Code

Would you like to:
1. Install for repository only (works when in repo)
2. Specify platform manually
3. Skip installation

Template Not Found

If templates are missing:

❌ Error: Template not found at resources/templates/

This skill requires the cli-ai-skills repository structure.

Options:
1. Clone cli-ai-skills: git clone <repo-url>
2. Create minimal skill structure manually
3. Exit and set up templates first

Validation Failures

If content doesn't meet standards:

⚠️  Validation Issues Found:

1. YAML: Description not in third-person format
   Expected: "This skill should be used when..."
   Found: "Use this skill when..."

2. Content: Word count too high (5,342 words, max 5,000)
   Suggestion: Move detailed sections to references/

Fix automatically? [Y/n]

Installation Conflicts

If symlink already exists:

⚠️  Skill already installed at ~/.copilot/skills/your-skill-name

Options:
1. Overwrite existing installation
2. Rename new skill
3. Skip installation
4. Install to different location

Bundled Resources

This skill includes additional resources in subdirectories:

references/

Detailed documentation loaded when needed:

  • anthropic-best-practices.md - Official Anthropic skill development guidelines
  • writing-style-guide.md - Writing standards and examples
  • progressive-disclosure.md - Content organization patterns
  • validation-checklist.md - Pre-commit quality checks

examples/

Working examples demonstrating skill usage:

  • basic-skill-creation.md - Simple skill creation walkthrough
  • advanced-skill-bundled-resources.md - Complex skill with references/
  • global-installation.md - Installing skills system-wide

scripts/

Executable utilities for skill maintenance:

  • validate-all-skills.sh - Batch validation of all skills in repository
  • update-skill-version.sh - Bump version and update changelog
  • generate-skill-index.sh - Auto-generate skills catalog

Technical Implementation Notes

Template Substitution:

  • Use sed for simple replacements
  • Preserve YAML formatting exactly
  • Handle multi-line descriptions with proper escaping

Symlink Strategy:

  • Always use absolute paths: ln -sf /full/path/to/source ~/.copilot/skills/name
  • Verify symlink before considering installation complete
  • Benefits: Auto-updates when repository is pulled

Validation Integration:

  • Run validation before installation
  • Block installation if critical errors found
  • Warnings are informational only

Git Integration:

  • Extract author from git config user.name
  • Use repository root detection: git rev-parse --show-toplevel
  • Respect .gitignore patterns

Quality Standards

SKILL.md Requirements:

  • 1,500-2,000 words (ideal)
  • Under 5,000 words (maximum)
  • Third-person description format
  • Imperative/infinitive writing style
  • Progressive disclosure pattern

README.md Requirements:

  • 300-500 words
  • User-facing language
  • Clear installation instructions
  • Practical usage examples

Validation Checks:

  • YAML frontmatter completeness
  • Description format (third-person)
  • Word count limits
  • Writing style (no second-person)
  • Required fields present

References

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Files (agentic-awesome-skills)
  • references
    • output-patterns.md 1.8 KB
      Loading…
    • workflows.md 818 B
      Loading…
  • scripts
    • init_skill.py 11.8 KB
      Loading…
    • package_skill.py 4.3 KB
      Loading…
    • quick_validate.py 3.9 KB
      Loading…
  • LICENSE.txt 11.1 KB
    Loading…
  • README.md 8 KB
    # skill-creator
    
    **Automate CLI skill creation with best practices built-in.**
    
    ## What It Does
    
    The skill-creator automates the entire workflow of creating new CLI skills for GitHub Copilot CLI and Claude Code. It guides you through brainstorming, applies standardized templates, validates content quality, and handles installation—all while following Anthropic's official best practices.
    
    ## Key Features
    
    - **🎯 Interactive Brainstorming** - Collaborative session to define skill purpose and scope
    - **✨ Template Automation** - Automatic file generation with zero manual configuration
    - **🔍 Quality Validation** - Built-in checks for YAML, content quality, and writing style
    - **📦 Flexible Installation** - Choose repository-only, global, or hybrid installation
    - **📊 Visual Progress Bar** - Real-time progress indicator showing completion status (e.g., `[████████████░░░░░░] 60% - Step 3/5`)
    - **🔗 Prompt Engineer Integration** - Optional enhancement using prompt-engineer skill
    
    ## When to Use
    
    Use this skill when you want to:
    - Create a new CLI skill following official standards
    - Extend CLI functionality with custom capabilities
    - Package domain knowledge into a reusable skill format
    - Automate repetitive CLI tasks with a custom skill
    - Install skills locally or globally across your system
    
    ## Installation
    
    ### Prerequisites
    
    This skill is part of the `cli-ai-skills` repository. To use it:
    
    ```bash
    # Clone the repository
    git clone https://github.com/yourusername/cli-ai-skills.git
    cd cli-ai-skills
    ```
    
    ### Install Globally (Recommended)
    
    Install via symlinks to make the skill available everywhere:
    
    ```bash
    # For GitHub Copilot CLI
    ln -sf "$(pwd)/.github/skills/skill-creator" ~/.copilot/skills/skill-creator
    
    # For Claude Code
    ln -sf "$(pwd)/.claude/skills/skill-creator" ~/.claude/skills/skill-creator
    ```
    
    **Benefits of global installation:**
    - Works in any directory
    - Auto-updates when you `git pull` the repository
    - No configuration files needed
    
    ### Repository-Only Installation
    
    If you prefer to use the skill only within this repository, no installation is needed. The skill will be available when working in the `cli-ai-skills` directory.
    
    ## Usage
    
    ### Basic Skill Creation
    
    Simply ask the CLI to create a new skill:
    
    ```bash
    # GitHub Copilot CLI
    gh copilot "create a new skill for debugging Python errors"
    
    # Claude Code
    claude "create a skill that helps with git workflows"
    ```
    
    The skill will guide you through with visual progress tracking:
    1. **Brainstorming** (20%) - Define purpose, triggers, and type
    2. **Prompt Enhancement** (40%, optional) - Enhance with prompt-engineer skill
    3. **File Generation** (60%) - Create files from templates
    4. **Validation** (80%) - Check quality and standards
    5. **Installation** (100%) - Choose local, global, or both
    
    Each phase displays a progress bar:
    ```
    [████████████░░░░░░] 60% - Step 3/5: File Generation
    ```
    
    ### Advanced Usage
    
    #### Create Code Generation Skill
    
    ```bash
    "Create a code skill that generates React components from descriptions"
    ```
    
    The skill will:
    - Use the specialized `code-skill-template.md`
    - Ask about specific frameworks (React, Vue, etc.)
    - Include code examples in the `examples/` folder
    
    #### Create Documentation Skill
    
    ```bash
    "Build a skill that writes API documentation from code"
    ```
    
    The skill will:
    - Use `documentation-skill-template.md`
    - Ask about documentation formats
    - Set up references for style guides
    
    #### Install for Specific Platform
    
    ```bash
    "Create a skill for Copilot only that analyzes TypeScript errors"
    ```
    
    The skill will:
    - Generate files only in `.github/skills/`
    - Skip Claude-specific installation
    - Validate against Copilot requirements
    
    ## Example Walkthrough
    
    Here's what creating a skill looks like:
    
    ```
    You: "create a skill for database schema migrations"
    
    [████░░░░░░░░░░░░░░] 20% - Step 1/5: Brainstorming & Planning
    
    What should this skill do?
    > Helps users create and manage database schema migrations safely
    
    When should it trigger? (3-5 phrases)
    > "create migration", "generate schema change", "migrate database"
    
    What type of skill?
    > [×] General purpose
    
    Which platforms?
    > [×] Both (Copilot + Claude)
    
    [... continues through all phases ...]
    
    🎉 Skill created successfully!
    
    📦 Skill Name: database-migration
    📁 Location: .github/skills/database-migration/
    🔗 Installed: Global (Copilot + Claude)
    ```
    
    ## File Structure
    
    When you create a skill, this structure is generated:
    
    ```
    .github/skills/your-skill-name/
    ├── SKILL.md              # Main skill instructions (1.5-2k words)
    ├── README.md             # User-facing documentation (this file)
    ├── references/           # Detailed guides (2k-5k words each)
    │   └── (empty, ready for extended docs)
    ├── examples/             # Working code samples
    │   └── (empty, ready for examples)
    └── scripts/              # Executable utilities
        └── (empty, ready for automation)
    ```
    
    ## Configuration
    
    **No configuration needed!** This skill uses runtime discovery to:
    - Detect installed platforms (Copilot CLI, Claude Code)
    - Find repository root automatically
    - Extract author info from git config
    - Determine optimal file locations
    
    ## Validation
    
    Every skill created is automatically validated for:
    - ✅ **YAML Frontmatter** - Required fields and format
    - ✅ **Description Format** - Third-person, trigger phrases
    - ✅ **Word Count** - 1,500-2,000 ideal, under 5,000 max
    - ✅ **Writing Style** - Imperative form, no second-person
    - ✅ **Progressive Disclosure** - Proper content organization
    
    ## Frameworks Used
    
    This skill leverages several established methodologies:
    
    - **Progressive Disclosure** - 3-level content hierarchy (metadata → SKILL.md → bundled resources)
    - **Bundled Resources Pattern** - References, examples, and scripts as separate files
    - **Anthropic Best Practices** - Official skill development standards
    - **Zero-Config Design** - Runtime discovery, no hardcoded values
    - **Template-Driven Generation** - Consistent structure across all skills
    
    ## Troubleshooting
    
    ### "Template not found" Error
    
    Ensure you're in the `cli-ai-skills` repository or have cloned it:
    
    ```bash
    git clone https://github.com/yourusername/cli-ai-skills.git
    cd cli-ai-skills
    ```
    
    ### "Platform not detected" Warning
    
    If platforms aren't detected:
    1. Choose "Repository only" installation
    2. Manually specify platform during setup
    3. Install globally later using provided commands
    
    ### Validation Failures
    
    If validation finds issues:
    - Review suggestions in the output
    - Choose automatic fixes for common problems
    - Manually edit files for complex issues
    - Re-run validation: `scripts/validate-skill-yaml.sh .github/skills/your-skill`
    
    ## Advanced Features
    
    ### Prompt Engineer Integration
    
    Enhance your skill descriptions with AI:
    1. Enable during Phase 2 (Prompt Refinement)
    2. Skill will invoke `prompt-engineer` automatically
    3. Review enhanced output before proceeding
    
    ### Bundled Resources
    
    For complex skills, use bundled resources:
    - **references/** - Detailed documentation (no word limit)
    - **examples/** - Working code samples users can run
    - **scripts/** - Automation utilities loaded on demand
    
    ### Version Management
    
    Update existing skills:
    ```bash
    scripts/update-skill-version.sh your-skill-name 1.1.0
    ```
    
    ## Contributing
    
    Created a useful skill? Share it:
    1. Ensure validation passes
    2. Add usage examples
    3. Update main README.md
    4. Submit a pull request
    
    ## Resources
    
    - **Writing Style Guide:** `resources/templates/writing-style-guide.md`
    - **Anthropic Official Guide:** https://github.com/anthropics/claude-plugins-official
    - **Templates Directory:** `resources/templates/`
    - **Validation Scripts:** `scripts/validate-*.sh`
    
    ## Support
    
    For issues or questions:
    - Check existing skills in `.github/skills/` for examples
    - Review `resources/skills-development.md` for methodology
    - Open an issue in the repository
    
    ---
    
    **Version:** 1.1.0
    **Platform:** GitHub Copilot CLI, Claude Code
    **Author:** Eric Andrade
    **Last Updated:** 2026-02-01
    
  • SKILL.md 21.6 KB
    ---
    name: skill-creator
    description: "To create new CLI skills following Anthropic's official best practices with zero manual configuration. This skill automates brainstorming, template application, validation, and installation processes while maintaining progressive disclosure patterns and writing style standards."
    category: meta
    risk: safe
    source: community
    tags: "[automation, scaffolding, skill-creation, meta-skill]"
    date_added: "2026-02-27"
    plugin:
      targets:
        codex: supported
        claude: supported
    ---
    
    # skill-creator
    
    ## Purpose
    
    To create new CLI skills following Anthropic's official best practices with zero manual configuration. This skill automates brainstorming, template application, validation, and installation processes while maintaining progressive disclosure patterns and writing style standards.
    
    ## When to Use This Skill
    
    This skill should be used when:
    - User wants to extend CLI functionality with custom capabilities
    - User needs to create a skill following official standards
    - User wants to automate repetitive CLI tasks with a reusable skill
    - User needs to package domain knowledge into a skill format
    - User wants both local and global skill installation options
    
    ## Core Capabilities
    
    1. **Interactive Brainstorming** - Collaborative session to define skill purpose and scope
    2. **Prompt Enhancement** - Optional integration with prompt-engineer skill for refinement
    3. **Template Application** - Automatic file generation from standardized templates
    4. **Validation** - YAML, content, and style checks against Anthropic standards
    5. **Installation** - Local repository or global installation with symlinks
    6. **Progress Tracking** - Visual gauge showing completion status at each step
    
    ## Step 0: Discovery
    
    Before starting skill creation, gather runtime information:
    
    ```bash
    # Detect available platforms
    COPILOT_INSTALLED=false
    CLAUDE_INSTALLED=false
    CODEX_INSTALLED=false
    
    if command -v gh &>/dev/null && gh copilot --version &>/dev/null 2>&1; then
        COPILOT_INSTALLED=true
    fi
    
    if [[ -d "$HOME/.claude" ]]; then
        CLAUDE_INSTALLED=true
    fi
    
    if [[ -d "$HOME/.codex" ]]; then
        CODEX_INSTALLED=true
    fi
    
    # Determine working directory
    REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
    SKILLS_REPO="$REPO_ROOT"
    
    # Check if in cli-ai-skills repository
    if [[ ! -d "$SKILLS_REPO/.github/skills" ]]; then
        echo "⚠️  Not in cli-ai-skills repository. Creating standalone skill."
        STANDALONE=true
    fi
    
    # Get user info from git config
    AUTHOR=$(git config user.name || echo "Unknown")
    EMAIL=$(git config user.email || echo "")
    ```
    
    **Key Information Needed:**
    - Which platforms to target (Copilot, Claude, Codex, or all three)
    - Installation preference (local, global, or both)
    - Skill name and purpose
    - Skill type (general, code, documentation, analysis)
    
    ## Main Workflow
    
    ### Progress Tracking Guidelines
    
    Throughout the workflow, display a visual progress bar before starting each phase to keep the user informed. The progress bar format is:
    
    ```
    [████████████░░░░░░] 60% - Step 3/5: Creating SKILL.md
    ```
    
    **Format specifications:**
    - 20 characters wide (use █ for filled, ░ for empty)
    - Percentage based on current step (Step 1=20%, Step 2=40%, Step 3=60%, Step 4=80%, Step 5=100%)
    - Step counter showing current/total (e.g., "Step 3/5")
    - Brief description of current phase
    
    **Display the progress bar using:**
    ```bash
    echo "[████░░░░░░░░░░░░░░] 20% - Step 1/5: Brainstorming & Planning"
    ```
    
    ### Phase 1: Brainstorming & Planning
    
    **Progress:** Display before starting this phase:
    ```bash
    echo "[████░░░░░░░░░░░░░░] 20% - Step 1/5: Brainstorming & Planning"
    ```
    
    Display progress:
    ```
    ╔══════════════════════════════════════════════════════════════╗
    ║     🛠️  SKILL CREATOR - Creating New Skill                  ║
    ╠══════════════════════════════════════════════════════════════╣
    ║ → Phase 1: Brainstorming                 [10%]               ║
    ║ ○ Phase 2: Prompt Refinement                                 ║
    ║ ○ Phase 3: File Generation                                   ║
    ║ ○ Phase 4: Validation                                        ║
    ║ ○ Phase 5: Installation                                      ║
    ╠══════════════════════════════════════════════════════════════╣
    ║ Progress: ███░░░░░░░░░░░░░░░░░░░░░░░░░░░  10%              ║
    ╚══════════════════════════════════════════════════════════════╝
    ```
    
    **Ask the user:**
    
    1. **What should this skill do?** (Free-form description)
       - Example: "Help users debug Python code by analyzing stack traces"
    
    2. **When should it trigger?** (Provide 3-5 trigger phrases)
       - Example: "debug Python error", "analyze stack trace", "fix Python exception"
    
    3. **What type of skill is this?**
       - [ ] General purpose (default template)
       - [ ] Code generation/modification
       - [ ] Documentation creation/maintenance
       - [ ] Analysis/investigation
    
    4. **Which platforms should support this skill?**
       - [ ] GitHub Copilot CLI
       - [ ] Claude Code
        - [ ] Codex
        - [ ] All three (recommended)
    
    5. **Provide a one-sentence description** (will appear in metadata)
       - Example: "Analyzes Python stack traces and suggests fixes"
    
    **Capture responses and prepare for next phase.**
    
    ### Phase 2: Prompt Enhancement (Optional)
    
    **Progress:** Display before starting this phase:
    ```bash
    echo "[████████░░░░░░░░░░] 40% - Step 2/5: Prompt Enhancement"
    ```
    
    Update progress:
    ```
    ╔══════════════════════════════════════════════════════════════╗
    ║ ✓ Phase 1: Brainstorming                                     ║
    ║ → Phase 2: Prompt Refinement             [30%]               ║
    ╠══════════════════════════════════════════════════════════════╣
    ║ Progress: █████████░░░░░░░░░░░░░░░░░░░░░  30%              ║
    ╚══════════════════════════════════════════════════════════════╝
    ```
    
    **Ask the user:**
    "Would you like to refine the skill description using the prompt-engineer skill?"
    - [ ] Yes - Use prompt-engineer to enhance clarity and structure
    - [ ] No - Proceed with current description
    
    If **Yes**:
    1. Check if prompt-engineer skill is available
    2. Invoke with current description as input
    3. Review enhanced output with user
    4. Ask: "Accept enhanced version or keep original?"
    
    If **No** or prompt-engineer unavailable:
    - Proceed with original user input
    
    ### Phase 3: File Generation
    
    **Progress:** Display before starting this phase:
    ```bash
    echo "[████████████░░░░░░] 60% - Step 3/5: File Generation"
    ```
    
    Update progress:
    ```
    ╔══════════════════════════════════════════════════════════════╗
    ║ ✓ Phase 1: Brainstorming                                     ║
    ║ ✓ Phase 2: Prompt Refinement                                 ║
    ║ → Phase 3: File Generation               [50%]               ║
    ╠══════════════════════════════════════════════════════════════╣
    ║ Progress: ███████████████░░░░░░░░░░░░░░░  50%              ║
    ╚══════════════════════════════════════════════════════════════╝
    ```
    
    **Generate skill structure:**
    
    ```bash
    # Convert skill name to kebab-case
    SKILL_NAME=$(echo "$USER_INPUT" | tr '[:upper:]' '[:lower:]' | tr ' ' '-')
    
    # Create directories
    if [[ "$PLATFORM" =~ "copilot" ]]; then
        mkdir -p ".github/skills/$SKILL_NAME"/{references,examples,scripts}
    fi
    
    if [[ "$PLATFORM" =~ "claude" ]]; then
        mkdir -p ".claude/skills/$SKILL_NAME"/{references,examples,scripts}
    fi
    
    if [[ "$PLATFORM" =~ "codex" ]]; then
        mkdir -p ".codex/skills/$SKILL_NAME"/{references,examples,scripts}
    fi
    ```
    
    **Apply templates:**
    
    1. **SKILL.md** - Use appropriate template:
       - `skill-template-copilot.md`, `skill-template-claude.md`, or `skill-template-codex.md`
       - Substitute placeholders:
         - `{{SKILL_NAME}}` → kebab-case name
         - `{{DESCRIPTION}}` → one-line description
         - `{{TRIGGERS}}` → comma-separated trigger phrases
         - `{{PURPOSE}}` → detailed purpose from brainstorming
         - `{{AUTHOR}}` → from git config
         - `{{DATE}}` → current date (YYYY-MM-DD)
         - `{{VERSION}}` → "1.0.0"
    
    2. **README.md** - Use `readme-template.md`:
       - User-facing documentation (300-500 words)
       - Include installation instructions
       - Add usage examples
    
    3. **References/** (optional but recommended):
       - Create `detailed-guide.md` for extended documentation (2k-5k words)
       - Move lengthy content here to keep SKILL.md under 2k words
    
    **File creation commands:**
    
    ```bash
    # Apply template with substitution
    sed "s/{{SKILL_NAME}}/$SKILL_NAME/g; \
         s/{{DESCRIPTION}}/$DESCRIPTION/g; \
         s/{{AUTHOR}}/$AUTHOR/g; \
         s/{{DATE}}/$(date +%Y-%m-%d)/g" \
        resources/templates/skill-template-copilot.md \
        > ".github/skills/$SKILL_NAME/SKILL.md"
    
    # Create README
    sed "s/{{SKILL_NAME}}/$SKILL_NAME/g" \
        resources/templates/readme-template.md \
        > ".github/skills/$SKILL_NAME/README.md"
    
    # Apply template for Codex if selected
    if [[ "$PLATFORM" =~ "codex" ]]; then
        sed "s/{{SKILL_NAME}}/$SKILL_NAME/g; \
             s/{{DESCRIPTION}}/$DESCRIPTION/g; \
             s/{{AUTHOR}}/$AUTHOR/g; \
             s/{{DATE}}/$(date +%Y-%m-%d)/g" \
            resources/templates/skill-template-codex.md \
            > ".codex/skills/$SKILL_NAME/SKILL.md"
    
        sed "s/{{SKILL_NAME}}/$SKILL_NAME/g" \
            resources/templates/readme-template.md \
            > ".codex/skills/$SKILL_NAME/README.md"
    fi
    ```
    
    **Display created structure:**
    ```
    ✅ Created:
       .github/skills/your-skill-name/ (if Copilot selected)
       .claude/skills/your-skill-name/ (if Claude selected)
       .codex/skills/your-skill-name/ (if Codex selected)
       ├── SKILL.md (832 lines)
       ├── README.md (347 lines)
       ├── references/
       ├── examples/
       └── scripts/
    ```
    
    ### Phase 4: Validation
    
    **Progress:** Display before starting this phase:
    ```bash
    echo "[████████████████░░] 80% - Step 4/5: Validation"
    ```
    
    Update progress:
    ```
    ╔══════════════════════════════════════════════════════════════╗
    ║ ✓ Phase 3: File Generation                                   ║
    ║ → Phase 4: Validation                    [70%]               ║
    ╠══════════════════════════════════════════════════════════════╣
    ║ Progress: █████████████████████░░░░░░░░░  70%              ║
    ╚══════════════════════════════════════════════════════════════╝
    ```
    
    **Run validation scripts:**
    
    ```bash
    # Validate YAML frontmatter
    scripts/validate-skill-yaml.sh ".github/skills/$SKILL_NAME"
    
    # Validate content quality
    scripts/validate-skill-content.sh ".github/skills/$SKILL_NAME"
    ```
    
    **Expected output:**
    ```
    🔍 Validating YAML frontmatter...
    ✅ YAML frontmatter valid!
    
    🔍 Validating content...
    ✅ Word count excellent: 1847 words
    ✅ Content validation complete!
    ```
    
    **If validation fails:**
    - Display specific errors
    - Offer to fix automatically (common issues)
    - Ask user to manually correct complex issues
    
    **Common auto-fixes:**
    - Convert second-person to imperative form
    - Reformat description to third-person
    - Add missing required fields
    
    ### Phase 5: Installation
    
    **Progress:** Display before starting this phase:
    ```bash
    echo "[████████████████████] 100% - Step 5/5: Installation"
    ```
    
    Update progress:
    ```
    ╔══════════════════════════════════════════════════════════════╗
    ║ ✓ Phase 4: Validation                                        ║
    ║ → Phase 5: Installation                  [90%]               ║
    ╠══════════════════════════════════════════════════════════════╣
    ║ Progress: ██████████████████████████░░░░░  90%              ║
    ╚══════════════════════════════════════════════════════════════╝
    ```
    
    **Ask the user:**
    "How would you like to install this skill?"
    
    - [ ] **Repository only** - Files created in `.github/skills/` (works when in repo)
    - [ ] **Global installation** - Create symlinks in `~/.copilot/skills/` (works everywhere)
    - [ ] **Both** - Repository + global symlinks (recommended, auto-updates with git pull)
    - [ ] **Skip installation** - Just create files
    
    **If global installation selected:**
    
    ```bash
    # Detect which platforms to install for
    INSTALL_TARGETS=()
    
    if [[ "$COPILOT_INSTALLED" == "true" ]] && [[ "$PLATFORM" =~ "copilot" ]]; then
        INSTALL_TARGETS+=("copilot")
    fi
    
    if [[ "$CLAUDE_INSTALLED" == "true" ]] && [[ "$PLATFORM" =~ "claude" ]]; then
        INSTALL_TARGETS+=("claude")
    fi
    
    if [[ "$CODEX_INSTALLED" == "true" ]] && [[ "$PLATFORM" =~ "codex" ]]; then
        INSTALL_TARGETS+=("codex")
    fi
    
    # Ask user to confirm detected platforms
    echo "Detected platforms: ${INSTALL_TARGETS[*]}"
    echo "Install for these platforms? [Y/n]"
    ```
    
    **Installation process:**
    
    ```bash
    # GitHub Copilot CLI
    if [[ " ${INSTALL_TARGETS[*]} " =~ " copilot " ]]; then
        ln -sf "$SKILLS_REPO/.github/skills/$SKILL_NAME" \
               "$HOME/.copilot/skills/$SKILL_NAME"
        echo "✅ Installed for GitHub Copilot CLI"
    fi
    
    # Claude Code
    if [[ " ${INSTALL_TARGETS[*]} " =~ " claude " ]]; then
        ln -sf "$SKILLS_REPO/.claude/skills/$SKILL_NAME" \
               "$HOME/.claude/skills/$SKILL_NAME"
        echo "✅ Installed for Claude Code"
    fi
    
    # Codex
    if [[ " ${INSTALL_TARGETS[*]} " =~ " codex " ]]; then
        ln -sf "$SKILLS_REPO/.codex/skills/$SKILL_NAME" \
               "$HOME/.codex/skills/$SKILL_NAME"
        echo "✅ Installed for Codex"
    fi
    ```
    
    **Verify installation:**
    
    ```bash
    # Check symlinks
    ls -la ~/.copilot/skills/$SKILL_NAME 2>/dev/null
    ls -la ~/.claude/skills/$SKILL_NAME 2>/dev/null
    ls -la ~/.codex/skills/$SKILL_NAME 2>/dev/null
    ```
    
    ### Phase 6: Completion
    
    **Progress:** Display completion message:
    ```bash
    echo "[████████████████████] 100% - ✓ Skill created successfully!"
    ```
    
    Update progress:
    ```
    ╔══════════════════════════════════════════════════════════════╗
    ║ ✓ Phase 5: Installation                                      ║
    ║ ✅ SKILL CREATION COMPLETE!                                  ║
    ╠══════════════════════════════════════════════════════════════╣
    ║ Progress: ██████████████████████████████  100%              ║
    ╚══════════════════════════════════════════════════════════════╝
    ```
    
    **Display summary:**
    
    ```
    🎉 Skill created successfully!
    
    📦 Skill Name: your-skill-name
    📁 Location: .github/skills/your-skill-name/
    🔗 Installed: Global (Copilot + Claude)
    
    📋 Files Created:
       ✅ SKILL.md (1,847 words)
       ✅ README.md (423 words)
       ✅ references/ (empty, ready for extended docs)
       ✅ examples/ (empty, ready for code samples)
       ✅ scripts/ (empty, ready for utilities)
    
    🚀 Next Steps:
       1. Test the skill: Try trigger phrases in CLI
       2. Add examples: Create working code samples in examples/
       3. Extend docs: Add detailed guides to references/
       4. Commit changes: git add .github/skills/your-skill-name && git commit
       5. Share: Push to repository for team use
    
    💡 Pro Tips:
       - Keep SKILL.md under 2,000 words (currently: 1,847)
       - Move detailed content to references/ folder
       - Add executable scripts to scripts/ folder
       - Update README.md with real usage examples
       - Run validation before committing: scripts/validate-skill-yaml.sh
    ```
    
    ## Error Handling
    
    ### Platform Detection Issues
    
    If platforms cannot be detected:
    ```
    ⚠️  Unable to detect GitHub Copilot CLI or Claude Code
    
    Would you like to:
    1. Install for repository only (works when in repo)
    2. Specify platform manually
    3. Skip installation
    ```
    
    ### Template Not Found
    
    If templates are missing:
    ```
    ❌ Error: Template not found at resources/templates/
    
    This skill requires the cli-ai-skills repository structure.
    
    Options:
    1. Clone cli-ai-skills: git clone <repo-url>
    2. Create minimal skill structure manually
    3. Exit and set up templates first
    ```
    
    ### Validation Failures
    
    If content doesn't meet standards:
    ```
    ⚠️  Validation Issues Found:
    
    1. YAML: Description not in third-person format
       Expected: "This skill should be used when..."
       Found: "Use this skill when..."
    
    2. Content: Word count too high (5,342 words, max 5,000)
       Suggestion: Move detailed sections to references/
    
    Fix automatically? [Y/n]
    ```
    
    ### Installation Conflicts
    
    If symlink already exists:
    ```
    ⚠️  Skill already installed at ~/.copilot/skills/your-skill-name
    
    Options:
    1. Overwrite existing installation
    2. Rename new skill
    3. Skip installation
    4. Install to different location
    ```
    
    ## Bundled Resources
    
    This skill includes additional resources in subdirectories:
    
    ### references/
    
    Detailed documentation loaded when needed:
    - `anthropic-best-practices.md` - Official Anthropic skill development guidelines
    - `writing-style-guide.md` - Writing standards and examples
    - `progressive-disclosure.md` - Content organization patterns
    - `validation-checklist.md` - Pre-commit quality checks
    
    ### examples/
    
    Working examples demonstrating skill usage:
    - `basic-skill-creation.md` - Simple skill creation walkthrough
    - `advanced-skill-bundled-resources.md` - Complex skill with references/
    - `global-installation.md` - Installing skills system-wide
    
    ### scripts/
    
    Executable utilities for skill maintenance:
    - `validate-all-skills.sh` - Batch validation of all skills in repository
    - `update-skill-version.sh` - Bump version and update changelog
    - `generate-skill-index.sh` - Auto-generate skills catalog
    
    ## Technical Implementation Notes
    
    **Template Substitution:**
    - Use `sed` for simple replacements
    - Preserve YAML formatting exactly
    - Handle multi-line descriptions with proper escaping
    
    **Symlink Strategy:**
    - Always use absolute paths: `ln -sf /full/path/to/source ~/.copilot/skills/name`
    - Verify symlink before considering installation complete
    - Benefits: Auto-updates when repository is pulled
    
    **Validation Integration:**
    - Run validation before installation
    - Block installation if critical errors found
    - Warnings are informational only
    
    **Git Integration:**
    - Extract author from `git config user.name`
    - Use repository root detection: `git rev-parse --show-toplevel`
    - Respect `.gitignore` patterns
    
    ## Quality Standards
    
    **SKILL.md Requirements:**
    - 1,500-2,000 words (ideal)
    - Under 5,000 words (maximum)
    - Third-person description format
    - Imperative/infinitive writing style
    - Progressive disclosure pattern
    
    **README.md Requirements:**
    - 300-500 words
    - User-facing language
    - Clear installation instructions
    - Practical usage examples
    
    **Validation Checks:**
    - YAML frontmatter completeness
    - Description format (third-person)
    - Word count limits
    - Writing style (no second-person)
    - Required fields present
    
    ## References
    
    - **Anthropic Official Skill Development Guide:** https://github.com/anthropics/claude-plugins-official/blob/main/plugins/plugin-dev/skills/skill-development/SKILL.md
    - **Repository:** https://github.com/yourusername/cli-ai-skills
    - **Writing Style Guide:** `resources/templates/writing-style-guide.md`
    - **Progress Tracker Template:** `resources/templates/progress-tracker.md`
    
    ## Limitations
    - Use this skill only when the task clearly matches the scope described above.
    - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
    - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.