writing-skills

Create and refine agent skills using a Test-Driven Development methodology.

7|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/ftzi/livespec --skill writing-skills-ftzi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/ftzi/livespec/tree/main/.agents/skills/writing-skills
Command: npx skills add https://github.com/ftzi/livespec --skill writing-skills-ftzi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rigorous, test-driven framework for creating and refining agent skills, ensuring they are discoverable, effective, and resistant to common rationalizations.

Core Features & Use Cases

  • TDD for Skills: Adapts the RED-GREEN-REFACTOR cycle to skill documentation.
  • Pressure Testing: Develops scenarios to test skill compliance under realistic constraints (time, sunk cost, authority).
  • Rationalization Countermeasures: Identifies and explicitly addresses common excuses agents use to bypass rules.
  • Use Case: You need to create a new skill for code review. This skill guides you through writing failing test scenarios, documenting agent rationalizations, writing the skill to address those failures, and then testing it under pressure to ensure it's robust.

Quick Start

Use the writing-skills skill to create a new skill by following the TDD process.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
What is the best way to refine agent documentation to prevent rule bypasses?

The best way to refine agent documentation to prevent rule bypasses is through iterative refactoring guided by pressure testing, which explicitly addresses agent rationalizations and ensures robust compliance under realistic constraints.

How do I test agent skills using a Test-Driven Development approach?

To test agent skills using TDD, adapt the RED-GREEN-REFACTOR cycle to skill documentation by writing failing pressure scenarios first, then documenting the skill to pass them, and finally refactoring for robust compliance.

What are common rationalizations agents use to bypass skill rules?

Common rationalizations agents use to bypass skill rules involve excuses related to time constraints, sunk cost, and authority pressure. Identifying these rationalizations explicitly allows you to build countermeasures directly into the skill documentation.

What is pressure testing for skill compliance?

Pressure testing for skill compliance involves developing scenarios with realistic constraints like time, sunk cost, and authority to evaluate whether the agent adheres to skill documentation rules under difficult conditions.

How do I create reference skills and discipline-enforcing patterns for agents?

Creating reference skills and discipline-enforcing patterns involves using iterative refactoring and rationalization identification to ensure the agent documentation is robust, discoverable, and effective against common bypasses.

What is the best way to refine agent documentation to prevent rule bypasses?

The best way to refine agent documentation to prevent rule bypasses is through iterative refactoring guided by pressure testing, which explicitly addresses agent rationalizations and ensures robust compliance under realistic constraints.