writing-skills

Apply RED-GREEN-REFACTOR cycles to create and update skills with tests.

3|1|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/OmniNode-ai/omniclaude --skill writing-skills-omninode-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/writing-skills
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill writing-skills-omninode-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that new and updated skills are robust, well-tested, and resistant to rationalization by applying Test-Driven Development (TDD) principles to the skill creation process.

Core Features & Use Cases

  • TDD for Documentation: Applies the RED-GREEN-REFACTOR cycle to skill writing.
  • Bulletproofing Against Rationalization: Develops skills that agents reliably follow under pressure.
  • Use Case: When creating a new skill for enforcing coding standards, you would first write test scenarios to demonstrate agents failing to follow the standard (RED), then write the skill to make them comply (GREEN), and finally refine it to close loopholes agents might exploit (REFACTOR).

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
How do I use test-driven development for skill development to prevent agent rationalization?

Test-driven development for skill development mandates failing tests before implementation, applying RED-GREEN-REFACTOR cycles to ensure agents reliably follow instructions under pressure.

What is the best way to write agent skills that resist rationalization under pressure?

Writing agent skills that resist rationalization requires explicit counter-measures built via test-driven development, continuously verifying documentation compliance to close loopholes agents might exploit.

How do I apply the RED-GREEN-REFACTOR cycle when creating new skills?

Applying the RED-GREEN-REFACTOR cycle to skill creation involves writing test scenarios where agents fail a standard (RED), implementing the skill to achieve compliance (GREEN), and refining to close loopholes (REFACTOR).

Does test-driven development work for updating existing skills and documentation?

Yes, test-driven development applies to the entire skill lifecycle, from initial concept to refactoring, ensuring updated documentation remains robust and compliant through continuous verification.

When do I need to use TDD principles for skill documentation?

You need TDD principles for skill documentation when creating new skills or updating existing ones, ensuring robustness by mandating failing tests before implementation to verify compliance.

Why do my agents fail to follow coding standards even with detailed documentation?

Agents fail to follow coding standards when documentation lacks test-driven development enforcement, allowing rationalization; mandating failing tests before skill implementation bulletproofs against this behavior.