writing-skills

Implements a Test-Driven Development framework for authoring agent skills with RED-GREEN-REFACTOR cycles.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/arthrod/conejo-skills --skill writing-skills-arthrod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/arthrod/conejo-skills/tree/main/skills/writing-skills
Command: npx skills add https://github.com/arthrod/conejo-skills --skill writing-skills-arthrod

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of unreliable or poorly understood process documentation by applying Test-Driven Development (TDD) principles to the creation and maintenance of agent skills.

Core Features & Use Cases

  • TDD for Documentation: Provides a rigorous RED-GREEN-REFACTOR cycle for writing skills, ensuring they are tested against real agent behavior before deployment.
  • Rationalization Countermeasures: Includes systematic methods to identify and block agent rationalizations that lead to rule-breaking.
  • Use Case: Use this when you need to create a new skill or update an existing one to ensure it is bulletproof, verifiable, and resistant to agent shortcuts.

Quick Start

Use the writing-skills skill to guide the creation of a new skill by first running a baseline pressure scenario to document agent failures.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I apply TDD to process documentation for agent skills?

To apply TDD to process documentation, you use a RED-GREEN-REFACTOR cycle that pressure tests agent behavior against baseline failures before deployment. This verifies that your skills are bulletproof and resistant to agent shortcuts.

Why does my agent rationalize and break rules during skill execution?

Agents rationalize and break rules when process documentation lacks rigorous testing against real agent behavior. Applying a TDD framework with iterative pressure testing systematically identifies and blocks these rationalizations.

What is the best way to verify agent skills before deployment?

The best way to verify agent skills is running a baseline pressure scenario to document failures, then adhering to the RED-GREEN-REFACTOR cycle. This ensures all skills are bulletproof and fully tested before deployment.

Do I need any dependencies to use a TDD framework for writing agent skills?

No dependencies are required to use this TDD framework for writing agent skills. You can immediately start pressure testing your process documentation to identify agent rationalizations and refine your skills.

When should I avoid using a TDD approach for authoring agent skills?

You should avoid using a TDD approach for agent skills when you need rapid, unverified prototyping without baseline failure testing. Skipping the RED-GREEN-REFACTOR cycle means sacrificing systematic rationalization countermeasures and quality assurance.