writing-skills

Create a directory containing a SKILL.md file with YAML frontmatter defining name and description, followed by markdown instructions. Run baseline pressure scenarios without the skill first, then write content addressing the specific failures you observed.

Run pressure scenarios combining time, sunk cost, and authority pressures with subagents, first without the skill to capture baseline rationalizations, then with the skill to verify compliance. Iterate by closing loopholes until agents comply under maximum pressure.

Write the description in third person starting with "Use when..." followed by specific triggering conditions and symptoms. Never summarize the skill's workflow, since agents may follow the description instead of reading the full skill body.

Skip skill creation for one-off solutions, project-specific conventions, standard practices documented elsewhere, and mechanical constraints that can be enforced with validation or regex instead of documentation.

Agents rationalize away rules when facing time pressure, sunk costs, or authority conflicts. Counter this with explicit prohibition of specific workarounds, rationalization tables, red flag lists, and foundational principles like "violating the letter is violating the spirit."