writing-skills

Apply Test-Driven Development cycles to create and refine Skill documentation.

2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/ucirello/sgai --skill writing-skills-ucirello
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/ucirello/sgai/tree/main/cmd/sgai/skel/.sgai/skills/meta/writing-skills
Command: npx skills add https://github.com/ucirello/sgai --skill writing-skills-ucirello

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that documentation (Skills) is rigorously tested and effective by applying Test-Driven Development (TDD) principles, preventing agents from misinterpreting or ignoring instructions.

Core Features & Use Cases

  • TDD for Documentation: Write tests (pressure scenarios) before writing the Skill documentation, ensuring it works as intended.
  • Iterative Refinement: Refactor Skills based on agent failures to close loopholes and improve clarity.
  • Use Case: When developing a new Skill for complex debugging, you would first create scenarios where an agent fails to debug correctly without the Skill. Then, you write the Skill to address those specific failures, ensuring it guides the agent effectively under pressure.

Quick Start

Use the writing-skills skill to test a new skill by running pressure scenarios before writing the SKILL.md.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I test agent documentation before deploying it?

Test agent documentation by applying Test-Driven Development principles to skill creation. Write pressure scenarios that expose agent failures before writing the Skill documentation, ensuring instructions guide behavior effectively under stress.

What is Test-Driven Development for AI agent skills?

Test-Driven Development for AI agent skills is a methodology enforcing a strict RED-GREEN-REFACTOR cycle. It requires creating failing pressure scenarios first, then writing or refining documentation to make the agent pass those tests and close loopholes.

Why does my AI agent ignore instructions in complex scenarios?

AI agents ignore instructions when documentation lacks rigorous testing against edge cases. Using a TDD approach for documentation closes loopholes by iteratively refactoring instructions based on specific agent failures observed during pressure scenarios.

How do I refine skill documentation to improve agent compliance?

Refine skill documentation by iteratively refactoring it based on agent failures. Continuously verify instructions against agent rationalizations during pressure scenarios to close loopholes and improve clarity for better compliance.

Can I use TDD for iterative improvement of existing agent behaviors?

Yes, you can use TDD for iterative improvement of existing agent behaviors. The methodology applies to the entire skill lifecycle, allowing you to refactor existing instructions under pressure by continuously verifying them against new failing scenarios.