**You own the skill's voice.** 1. Use the **plugin-dev:skill-development** skill (Claude Code's skill for authoring SKILL.md files). 2. Validate the skill: frontmatter has `name` and `description`, referenced files exist, cross-skill links resolve. 3. Test cases if structural. Skip if subjective. 4. Run **Opening a PR**. When in doubt, delete. Keep only prose that changes a decision. Tell it to do the thing and skip the reason. Explain only when the rule is confusing without one. Match tone t...
Pro scans all 21 files and shows the line behind each finding
Scanned 10/1/2026
Skills Directorynpx -y skills add arjitj2/open-pstack --skill playbooks --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Playbooks?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/arjitj2-playbooks)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
### Authoring or modifying a skill
**You own the skill's voice.**
1. Use the **plugin-dev:skill-development** skill (Claude Code's skill for authoring SKILL.md files).
2. Validate the skill: frontmatter has `name` and `description`, referenced files exist, cross-skill links resolve.
3. Test cases if structural. Skip if subjective.
4. Run **Opening a PR**.
When in doubt, delete. Keep only prose that changes 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) per the **encode-lessons-in-structure** principle skill. 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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
