Esta página todavía está en inglés. La traducción al español está en progreso.
Creating Skills
Skills are reusable instruction sets that teach Claude how to perform specific tasks. EvoNexus includes 126 built-in skills — you can create your own.Using the Skill Creator
The fastest way:skill-creator plugin walks you through:
- Name and prefix — follows the naming convention (e.g.,
prod-weekly-team-report) - Description — the trigger phrase that activates the skill
- Instructions — what Claude should do when the skill is invoked
Manual Creation
Skills live in.claude/skills/ organized by prefix.
File Structure
SKILL.md Format
Key Points
- The
descriptionfield is the trigger. Claude matches user intent against skill descriptions to decide which skill to activate. Make it specific and include common trigger phrases. - The
namefield is the skill identifier. - The body contains the full instructions Claude follows when the skill is activated.
Naming Convention
Skills use a prefix that indicates their category:Example: Creating a “Weekly Report” Skill
- Create the directory:
- Create
SKILL.md:
- Test it — just describe the task:
Tips
- Be specific in descriptions. “Generate financial reports” is too vague. “Generate financial statements (income statement, balance sheet, cash flow) with period-over-period comparison” tells Claude exactly when to activate.
- Include trigger phrases. Add common ways users might ask for the skill: “Use when the user says ‘X’, ‘Y’, or ‘Z’.”
- Reference other skills. Skills can call other skills — e.g., a weekly report skill can reference the Stripe integration skill for financial data.
- Test iteratively. Create the skill, test it, refine the instructions based on the output quality.