writing-skills

Apply Test-Driven Development cycles to create and maintain agent process documentation.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/chokky-education/science-club-web --skill writing-skills-chokky-education
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/chokky-education/science-club-web/tree/main
Command: npx skills add https://github.com/chokky-education/science-club-web --skill writing-skills-chokky-education

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent or ineffective process documentation by applying Test-Driven Development (TDD) principles to the creation and maintenance of agent skills.

Core Features & Use Cases

  • TDD-Based Authoring: Ensures skills are only created or updated after observing a baseline failure in an agent's performance.
  • Loophole Closure: Provides a systematic framework for identifying agent rationalizations and adding explicit counters to ensure compliance.
  • Use Case: When you need to ensure an agent consistently follows a complex multi-step review process, use this Skill to define the failure scenario, write the documentation, and verify the agent's compliance under pressure.

Quick Start

Invoke the writing-skills skill to begin the RED-GREEN-REFACTOR cycle for your new documentation project.

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 process documentation before deployment?

Agent process documentation is tested by observing a baseline failure in performance before creating or updating the guide, ensuring empirical verification of effectiveness through baseline failure testing and loophole analysis.

What is TDD-based authoring for agent skills?

TDD-based authoring adapts Test-Driven Development to process documentation by applying a RED-GREEN-REFACTOR cycle, ensuring guides are only written after observing a baseline agent failure that the documentation must resolve.

How do I stop an agent from rationalizing and skipping multi-step review processes?

To stop agent rationalization, apply a systematic loophole closure framework that identifies rationalizations and adds explicit counters to the documentation, ensuring strict compliance under pressure.

When do I need to use TDD for maintaining agent reference guides?

TDD is needed for maintaining agent reference guides when you require high agent compliance and empirical verification of documentation effectiveness, specifically when an agent fails to follow a complex multi-step process.

Does writing-skills require any specific testing frameworks to run?

No specific testing frameworks are required as dependencies. The skill applies the TDD cycle internally to the creation of agent-specific process documentation without external testing framework dependencies.

What is the best way to verify if my documentation effectively changes agent behavior?

The best way to verify documentation effectiveness is baseline failure testing, which observes the agent failing without the guide, then confirms compliance and loophole closure after the documentation is applied.