sp-writing-skills

Turn skill documentation authoring into a RED-GREEN-REFACTOR test-driven process.

23|2|Updated Mar 1, 2026

Search Tags:#documentation #test-driven development #skill metadata #agent compliance #skills authoring #rationalization counter #flowchart guidance

Ready to run

npx skills add https://github.com/tta-lab/ttal-cli --skill sp-writing-skills-tta-lab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sp-writing-skills
Source: https://github.com/tta-lab/ttal-cli/tree/main/skills/sp-writing-skills
Command: npx skills add https://github.com/tta-lab/ttal-cli --skill sp-writing-skills-tta-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Writing skill documentation can fail under pressure because agents rationalize around vague rules or misunderstand the intended discipline.

Core Features & Use Cases

TDD-for-documentation workflow: Use RED-GREEN-REFACTOR to ensure agents comply with the rules expressed in the skill.
Discovery-optimized skill metadata: Craft a YAML frontmatter description that encodes when to use the skill without summarizing the workflow, improving retrieval accuracy.
Loophole resistance: Add explicit negations, foundational principles, rationalization tables, and red-flag counters so compliance holds under time, authority, sunk-cost, and exhaustion pressure.

Quick Start

Use sp-writing-skills to design or edit a skill when agents keep violating the intended rule under realistic pressure scenarios, and you must verify the fix before deployment.

Frequently Asked Questions about sp-writing-skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write agent skills that resist rationalization under pressure?▼

To write skills that resist rationalization, apply a test-driven documentation workflow using RED-GREEN-REFACTOR cycles. This validates compliance rules and loophole resistance under time, authority, sunk-cost, and exhaustion pressure scenarios before deployment.

What is test-driven development for skill documentation?▼

Test-driven development for skill documentation is a workflow that validates agent compliance by writing baseline failure tests, fixing the skill to pass them, and refactoring to eliminate rationalization loopholes.

How do I write YAML frontmatter descriptions for better skill discoverability?▼

To improve skill discoverability, craft a YAML frontmatter description that encodes when to use the skill without summarizing the workflow. This prevents vague metadata from degrading retrieval accuracy.

How do I add rationalization counters to skill metadata?▼

You add rationalization counters to skill metadata by including explicit negations, foundational principles, and red-flag counters in the documentation. This ensures compliance holds when agents face realistic pressure scenarios.

When should I use a test-driven approach for skills authoring?▼

Use a test-driven approach for skills authoring when agents keep violating the intended rule under realistic pressure scenarios, and you must verify the compliance fix before deployment.

What are the limitations of using standard documentation for agent compliance?▼

Standard documentation fails under pressure because agents rationalize around vague rules or misunderstand the intended discipline, lacking the explicit counters and test structure needed to validate loophole resistance.