lyahx/hstack/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. Use the skill-creator skill for authoring and iterating on SKILL.md files. It ships in the skill-creator plugin from the claude-plugins-official marketplace, not in Claude Code itself. If it is not installed, say so once and author the skill directly against the rules in this playbook instead of silently dropping the step.
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; prose earns its keep by changing a decision. Match tone to scope. Point at structural sources (types, READMEs, config); hardcoded details go stale (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.