writing-skills

To stop agents from skipping process documentation under pressure, apply test-driven authoring by running failing baseline scenarios, then harden instructions with explicit negations and rationalization tables. This enforces compliance by observing failures without the Skill first.

Test-driven Skill authoring is a process of running RED-GREEN-REFACTOR baseline checks to validate documentation rules. You observe agent failures without the Skill, then update the text to enforce compliance until the agent reliably follows instructions under pressure.

Harden agent instructions against loopholes by adding explicit negations, rationalization tables, and red flags. Re-verify compliance by testing the Skill against realistic multi-pressure scenarios until rationalizations are blocked.

Write Skill metadata for agent discovery by establishing correct names and descriptions focused on CSO discovery requirements. This helps agents select the right Skill by defining clear, search-oriented guidance for the task it performs.

Use test-driven documentation when creating, editing, or deploying Skill instructions, especially for discipline-enforcing rules agents may be tempted to bypass. It is needed when instructions must reliably hold under realistic multi-pressure scenarios.

Organize long Skill instructions by using documentation architecture to determine when to inline content versus reference other files. This structures complex instructions into modular components for better agent comprehension and compliance.