writing-skills
Write High-Quality AI Agent Skills
Também disponível em: Cygnusfear,Cycleaddict,ZhanlinCui,davila7,obra,Dimon94,DYAI2025,CodingCossack
This skill provides templates, decision trees, and best practices for creating and improving AI agent skills. It helps users avoid common mistakes and follow standardized patterns.
Baixar o ZIP da skill
Upload no Claude
Vá em Configurações → Capacidades → Skills → Upload skill
Ative e comece a usar
Testar
A utilizar "writing-skills". I want to create a skill for handling API errors
Resultado esperado:
A complete SKILL.md with: name: api-error-handler, description: 'Use when API request fails or returns error status', metadata with triggers: api-error, network-failure, 503, with references/ folder for detailed handling procedures
A utilizar "writing-skills". My skill description is 'This skill helps with file operations' - it's not triggering
Resultado esperado:
Optimized description: 'Use when user asks to read, write, or modify files. Triggers on: file-create, file-edit, file-delete, touch, mkdir, rm command'
Auditoria de Segurança
SeguroThis is a documentation and reference skill providing guidance on writing AI agent skills. All static findings are false positives - the scanner detected patterns in markdown documentation (code formatting with backticks, mentions of cryptographic terms, URLs in documentation) rather than actual executable code. The render-graphs.js is a build script for documentation generation, not runtime functionality.
Pontuação de qualidade
O Que Você Pode Construir
Creating a New Skill
Use the decision tree to select the right architecture tier and template for a new skill, then follow the template structure.
Improving Existing Skills
Diagnose why a skill is not being triggered or ignored by agents, then apply anti-rationalization or CSO techniques.
Standardizing Team Skills
Ensure all team skills follow consistent naming conventions, metadata standards, and directory structures.
Tente Estes Prompts
I need to create a new skill called [skill-name]. It should [what it does]. Use the Tier 1 template from the writing-skills reference.
My skill [skill-name] is not being triggered by Claude. The description is: [description]. Apply CSO optimization from writing-skills.
I have a discipline skill with rules that Claude keeps ignoring. The rules are: [rules]. Apply anti-rationalization techniques.
I need to create a complex skill with multiple concepts (200-1000 lines). Use Tier 2 expanded architecture with proper references.
Melhores Práticas
- Always start descriptions with 'Use when...' followed by specific trigger conditions
- Include at least 3 keywords in metadata.triggers for better discoverability
- Keep single-file skills under 200 lines; use references/ for longer content
- Split monolithic skills into multiple files using the tier system
Evitar
- Describing workflow instead of triggers (e.g., 'This skill helps you create files' instead of 'Use when user wants to create a file')
- Using generic skill names like 'helper' or 'utility' instead of descriptive gerunds
- Missing metadata.triggers field or having fewer than 3 trigger keywords
- Creating long monolithic SKILL.md files instead of modular references/