**You own the skill's voice.** Agent-facing prose has a higher bar than human prose; unhelpful sentences become instructions. 1. Follow this repository's skill-authoring conventions: YAML frontmatter with `name` plus a trigger-rich `description`, supporting files beside the SKILL.md that needs them. 2. Validate the skill: frontmatter has `name` and `description`, referenced files exist, cross-links resolve. 3. Test cases if structural; skip if subjective. 4. Run **Opening a PR**. When in doub...
Installs into .claude/skills of the current project.
Are you the author of Playbooks?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/fabricioctelles-playbooks)
### Authoring or modifying a skill
**You own the skill's voice.** Agent-facing prose has a higher bar than human prose; unhelpful sentences become instructions.
1. Follow this repository's skill-authoring conventions: YAML frontmatter with `name` plus a trigger-rich `description`, supporting files beside the SKILL.md that needs them.
2. Validate the skill: frontmatter has `name` and `description`, referenced files exist, cross-links resolve.
3. Test cases if structural; skip if subjective.
4. Run **Opening a PR**.
When in doubt, delete; prose earns its keep by changing a decision. Tell it to do the thing and skip the reason. Explain only when the rule is confusing without one. Match tone to scope. Point at structural sources (types, READMEs, config); hardcoded details go stale (the [**encode-lessons-in-structure**](../references/principles.md#encode-lessons-in-structure) principle). Delegate to other skills by path; don't restate. A workflow you keep hitting but isn't captured → propose a new skill.
**Reply:** summary of the skill, key design decisions, validation notes.
