Menú
Guide for creating effective skills. Use 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.
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.
Basado en la clasificación ocupacional SOC
This skill should be used when the user asks to "onboard", "analyze this repo", "understand this codebase", "familiarize yourself", "what is this project", or needs to deeply understand a codebase's architecture, patterns, and conventions before starting work.
Analyze the current repo deeply and suggest agentic workflows tailored to its architecture, patterns, and pain points. Use when user calls /aw-planner.
Read a GitHub issue with all comments and linked content to add as working context. Use when the user provides a GitHub issue URL or reference.
Generate a comprehensive manual testing guide for completed work, with note sections for user feedback that the agent reviews afterward. Use when the user wants to manually test changes before shipping.
Review PR comments, validate which are actionable and correct, and propose fixes for valid ones. Use when user wants to address feedback on a pull request.
Convert Markdown text to Zendesk-compatible HTML. Use when user needs to format content for Zendesk tickets, macros, triggers, or automations.
| name | skill-creator |
| description | Guide for creating effective skills. Use 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. |
| source | anthropics/skills |
| license | Apache-2.0 |
Skills are modular packages that extend Claude's capabilities by providing specialized knowledge, workflows, and tools.
The context window is a shared resource. Only add context Claude doesn't already have. Challenge each piece: "Does Claude really need this?"
skill-name/
├── SKILL.md (required)
│ ├── YAML frontmatter (name, description)
│ └── Markdown instructions
└── Bundled Resources (optional)
├── scripts/ - Executable code
├── references/ - Documentation
└── assets/ - Templates, images
---
name: my-skill-name
description: A clear description of what this skill does and when to use it
---
# My Skill Name
[Instructions for Claude when this skill is active]
## Examples
- Example usage 1
- Example usage 2
## Guidelines
- Guideline 1
- Guideline 2
Gather concrete examples of how the skill will be used. Ask:
Analyze examples to identify:
Create the skill directory structure with SKILL.md and resource folders.
Use the skill on real tasks, notice struggles, improve.
Keep SKILL.md under 500 lines. Split content:
# PDF Processing
## Quick start
[code example]
## Advanced features
- **Form filling**: See [FORMS.md](FORMS.md)
- **API reference**: See [REFERENCE.md](REFERENCE.md)
Skills are for AI agents, not humans.