writing-skills

Write and verify SKILL.md guides using RED-GREEN-REFACTOR cycles.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/ccakmak60/agentforge --skill writing-skills-ccakmak60
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/ccakmak60/agentforge/tree/main/.trae/skills/writing-skills
Command: npx skills add https://github.com/ccakmak60/agentforge --skill writing-skills-ccakmak60

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing high-quality process documentation for skills is error-prone and often underutilized during pressure; this skill applies test-driven development principles to documentation to ensure skills are defined, tested, and bulletproof before deployment.

Core Features & Use Cases

  • Enforces a discipline-driven skill creation workflow (RED-GREEN-REFACTOR) to capture actual agent behavior and close loopholes.
  • Guides skill authors to document baseline rationalizations, failures, and explicit counters to prevent circumvention under stress.
  • Provides a structured frontmatter and progressive-disclosure patterns to keep the core content lightweight while linking to deeper references.

Quick Start

Begin with a baseline RED test, then write a minimal SKILL.md and re-run tests to ensure agent compliance.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How does test-driven development for process documentation work?

Test-driven development for process documentation applies RED-GREEN-REFACTOR cycles to skill writing. You start with a failing baseline RED test, write a minimal SKILL.md, and iteratively run tests to ensure agent compliance before deployment.

How do I write bulletproof process docs using subagents?

To write bulletproof process docs, use subagents to test your SKILL.md under pressure. This approach captures actual agent behavior, documents baseline rationalizations, and closes loopholes by tracking failures across multiple scenarios.

What is the best way to structure a SKILL.md file for TDD?

The best way to structure a SKILL.md for TDD is using explicit frontmatter with name and description, followed by structured sections. Progressive-disclosure patterns keep core content lightweight while linking to deeper references.

Do I need any specific dependencies to use TDD for skill writing?

No specific dependencies are required to use TDD for skill writing. You only need to follow the RED-GREEN-REFACTOR workflow, starting with a baseline RED test and iterating through green and refactor cycles.

Why does my process documentation fail under pressure?

Process documentation fails under pressure when it lacks baseline rationalizations and explicit counters. Applying TDD principles enforces a discipline-driven workflow that prevents circumvention by documenting failures and tracking rationalization across scenarios.

When do I need test-driven documentation for my skills?

You need test-driven documentation when creating or editing SKILL.md-based guides for deployment. It ensures your skills are defined, tested, and bulletproof by enforcing RED-GREEN-REFACTOR cycles before the content is considered deployment-ready.