Skip to main content Inicio Creadores baotoq go-shortener tools-skill-creator
tools-skill-creator This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities. Automates the entire skill creation workflow from brainstorming to installation.
Ir a la instalación Skills Marketplace Descubre y explora habilidades de IA creadas por la comunidad.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Mostrar detalles del prompt Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/baotoq/go-shortener --skill tools-skill-creatorEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Descargar Zip Descargando... Más de este repositorio architecture-domain-analysis Identifies subdomains and suggests bounded contexts in any codebase following DDD Strategic Design. Use when analyzing domain boundaries, identifying business subdomains, assessing domain cohesion, mapping bounded contexts, or when the user asks about DDD strategic design, domain analysis, or subdomain classification.
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
architecture-saga-orchestration Implement saga patterns for distributed transactions and cross-aggregate workflows. Use when coordinating multi-step business processes, handling compensating transactions, or managing long-running workflows.
Explorador de archivos
7 archivos Ocupaciones relacionadas SOC
Basado en la clasificación ocupacional SOC
name tools-skill-creator description This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities. Automates the entire skill creation workflow from brainstorming to installation. version 1.3.0 author Eric Andrade created "2025-02-01T00:00:00.000Z" updated "2026-02-04T00:00:00.000Z" platforms ["github-copilot-cli","claude-code","codex"] category meta tags ["automation","scaffolding","skill-creation","meta-skill"] risk safe license MIT metadata {"version":"1.3.0","domain":"architecture","triggers":"create skill, build skill, custom skill, skill creation, scaffolding","role":"specialist","scope":"implementation","output-format":"code"}
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
Interactive Brainstorming - Collaborative session to define skill purpose and scopePrompt Enhancement - Optional integration with prompt-engineer skill for refinementTemplate Application - Automatic file generation from standardized templatesValidation - YAML, content, and style checks against Anthropic standardsInstallation - Local repository or global installation with symlinksProgress Tracking - Visual gauge showing completion status at each step
Step 0: Discovery
Before starting skill creation, gather runtime information:
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
pwd
"$REPO_ROOT "
if
"$SKILLS_REPO /.github/skills"
then
echo
"⚠️ Not in cli-ai-skills repository. Creating standalone skill."
true
fi
echo
"Unknown"
echo
""
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
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"
╔══════════════════════════════════════════════════════════════╗
║ 🛠️ 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% ║
╚══════════════════════════════════════════════════════════════╝
What should this skill do? (Free-form description)
Example: "Help users debug Python code by analyzing stack traces"
When should it trigger? (Provide 3-5 trigger phrases)
Example: "debug Python error", "analyze stack trace", "fix Python exception"
What type of skill is this?
Which platforms should support this skill?
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"
╔══════════════════════════════════════════════════════════════╗
║ ✓ 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?"
Check if prompt-engineer skill is available
Invoke with current description as input
Review enhanced output with user
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"
╔══════════════════════════════════════════════════════════════╗
║ ✓ Phase 1: Brainstorming ║
║ ✓ Phase 2: Prompt Refinement ║
║ → Phase 3: File Generation [50%] ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: ███████████████░░░░░░░░░░░░░░░ 50% ║
╚══════════════════════════════════════════════════════════════╝
Generate skill structure:
SKILL_NAME=$(echo "$USER_INPUT " | tr '[:upper:]' '[:lower:]' | tr ' ' '-' )
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
SKILL.md - Use appropriate template:
skill-template-copilot.md, skill-template-claude.md, or skill-template-codex.mdSubstitute 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"
README.md - Use readme-template.md:
User-facing documentation (300-500 words)
Include installation instructions
Add usage examples
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
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"
sed "s/{{SKILL_NAME}}/$SKILL_NAME /g" \
resources/templates/readme-template.md \
> ".github/skills/$SKILL_NAME /README.md"
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"
╔══════════════════════════════════════════════════════════════╗
║ ✓ Phase 3: File Generation ║
║ → Phase 4: Validation [70%] ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: █████████████████████░░░░░░░░░ 70% ║
╚══════════════════════════════════════════════════════════════╝
scripts/validate-skill-yaml.sh ".github/skills/$SKILL_NAME "
scripts/validate-skill-content.sh ".github/skills/$SKILL_NAME "
🔍 Validating YAML frontmatter...
✅ YAML frontmatter valid!
🔍 Validating content...
✅ Word count excellent: 1847 words
✅ Content validation complete!
Display specific errors
Offer to fix automatically (common issues)
Ask user to manually correct complex issues
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"
╔══════════════════════════════════════════════════════════════╗
║ ✓ Phase 4: Validation ║
║ → Phase 5: Installation [90%] ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: ██████████████████████████░░░░░ 90% ║
╚══════════════════════════════════════════════════════════════╝
Ask the user:
"How would you like to install this skill?"
If global installation selected:
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
echo "Detected platforms: ${INSTALL_TARGETS[*]} "
echo "Install for these platforms? [Y/n]"
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
if [[ " ${INSTALL_TARGETS[*]} " =~ " claude " ]]; then
ln -sf "$SKILLS_REPO /.claude/skills/$SKILL_NAME " \
"$HOME /.claude/skills/$SKILL_NAME "
echo "✅ Installed for Claude Code"
fi
if [[ " ${INSTALL_TARGETS[*]} " =~ " codex " ]]; then
ln -sf "$SKILLS_REPO /.codex/skills/$SKILL_NAME " \
"$HOME /.codex/skills/$SKILL_NAME "
echo "✅ Installed for Codex"
fi
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!"
╔══════════════════════════════════════════════════════════════╗
║ ✓ Phase 5: Installation ║
║ ✅ SKILL CREATION COMPLETE! ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: ██████████████████████████████ 100% ║
╚══════════════════════════════════════════════════════════════╝
🎉 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 guidelineswriting-style-guide.md - Writing standards and examplesprogressive-disclosure.md - Content organization patternsvalidation-checklist.md - Pre-commit quality checks
examples/ Working examples demonstrating skill usage:
basic-skill-creation.md - Simple skill creation walkthroughadvanced-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 repositoryupdate-skill-version.sh - Bump version and update changeloggenerate-skill-index.sh - Auto-generate skills catalog
Technical Implementation Notes
Use sed for simple replacements
Preserve YAML formatting exactly
Handle multi-line descriptions with proper escaping
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
Run validation before installation
Block installation if critical errors found
Warnings are informational only
Extract author from git config user.name
Use repository root detection: git rev-parse --show-toplevel
Respect .gitignore patterns
Quality Standards
1,500-2,000 words (ideal)
Under 5,000 words (maximum)
Third-person description format
Imperative/infinitive writing style
Progressive disclosure pattern
300-500 words
User-facing language
Clear installation instructions
Practical usage examples
YAML frontmatter completeness
Description format (third-person)
Word count limits
Writing style (no second-person)
Required fields present
References 