writing-skills

Apply the RED-GREEN-REFACTOR cycle to develop and verify agent skill documentation.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/novvoo/skill-router --skill writing-skills-novvoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/novvoo/skill-router/tree/main/agent/skills/writing-skills
Command: npx skills add https://github.com/novvoo/skill-router --skill writing-skills-novvoo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that new and updated skills are robust, effective, and prevent agents from rationalizing their way around critical rules, by applying Test-Driven Development (TDD) principles to skill documentation.

Core Features & Use Cases

  • TDD for Documentation: Adapts the RED-GREEN-REFACTOR cycle for writing and testing skills.
  • Pressure Scenario Testing: Develops realistic scenarios to test agent compliance under stress.
  • Rationalization Countermeasures: Identifies and explicitly addresses common excuses agents use to bypass rules.
  • Use Case: When creating a new skill for enforcing code review standards, you'd use this skill's methodology to write pressure scenarios that test if agents skip reviews under time constraints, then refine the skill to explicitly forbid such shortcuts.

Quick Start

Follow the TDD cycle to write and test your new skill documentation.

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 principles to write and test agent skills?

TDD principles for agent skills involve applying the RED-GREEN-REFACTOR cycle to write and refine documentation, ensuring robustness and compliance. You develop pressure scenarios first to verify logic before finalizing implementation.

Why do AI agents bypass rules and how can I prevent rationalization?

Agents bypass rules by rationalizing shortcuts under stress. You prevent rationalization by applying pressure scenario testing and rationalization tables to identify excuses, then adding explicit countermeasures to your skill documentation.

What are pressure scenarios in agent compliance testing?

Pressure scenarios in agent compliance testing are realistic stress situations used to verify if an agent skips critical rules. They test whether your skill documentation prevents the agent from rationalizing its way around constraints.

How do I ensure my skill documentation remains robust during updates?

To ensure skill documentation remains robust during updates, enforce the TDD RED-GREEN-REFACTOR cycle to verify changes. This addresses scenarios where agents might rationalize bypassing rules by testing compliance under pressure.

Can I test if an agent skips code reviews under time constraints?

Yes, you can test if an agent skips code reviews under time constraints by developing realistic pressure scenarios. This methodology verifies compliance and refines skills to explicitly forbid such rationalized shortcuts.