writing-skills

Create and refine agent skills using RED-GREEN-REFACTOR testing cycles.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Geargrindadmin/gg-agentic-harness --skill writing-skills-geargrindadmin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Geargrindadmin/gg-agentic-harness/tree/main/.agent/skills/writing-skills
Command: npx skills add https://github.com/Geargrindadmin/gg-agentic-harness --skill writing-skills-geargrindadmin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rigorous, test-driven development (TDD) framework for creating and refining agent skills, ensuring they are effective, discoverable, and robust against rationalization.

Core Features & Use Cases

  • TDD for Skills: Adapts the RED-GREEN-REFACTOR cycle to skill documentation.
  • Pressure Testing: Develops scenarios to test skills under realistic constraints (time, sunk cost, authority).
  • Rationalization Countermeasures: Identifies and addresses common excuses agents use to bypass rules.
  • Use Case: When developing a new skill for code review, you'd use this skill to first write test scenarios where an agent might skip review under time pressure, then write the skill to enforce review, and finally refactor to prevent rationalizations like "it's just a small change."

Quick Start

Use the writing-skills skill to create a new skill document following TDD principles.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I use TDD to write agent skills that agents reliably follow?

Test-driven development for agent skills applies the RED-GREEN-REFACTOR cycle to skill documentation, ensuring agents reliably follow instructions by pressure testing content against realistic constraints before finalizing.

What is the best way to prevent agent rationalization when creating skill documentation?

Preventing agent rationalization requires identifying common excuses agents use to bypass rules, then applying countermeasures during skill creation to address scenarios like skipping tasks under time pressure or sunk cost constraints.

How do I pressure test agent skills against realistic constraints?

Pressure testing agent skills involves developing scenarios that simulate realistic constraints such as time pressure, sunk cost, and authority, ensuring the skill documentation remains robust and enforceable under operational conditions.

Can I apply the RED-GREEN-REFACTOR cycle to skill documentation instead of code?

Yes, the RED-GREEN-REFACTOR cycle adapts directly to skill documentation by writing failing test scenarios first, creating skill content to pass those tests, then refactoring the documentation to eliminate rationalization loopholes.

Do I need prior testing experience to create agent skills with TDD?

Prior testing experience helps but is not required to create agent skills with TDD, as the methodology focuses on structuring documentation through iterative scenario testing and rationalization countermeasures rather than writing code tests.

When should I not use a TDD methodology for skill creation?

TDD methodology for skill creation is not ideal for rapid prototyping or exploratory drafting, since it requires defining test scenarios and rationalization countermeasures upfront before writing the actual skill documentation.