writing-tools

Enforce a red-green-refactor workflow for creating and editing skill documentation.

2|5|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/ulpi-io/togglebox --skill writing-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-tools
Source: https://github.com/ulpi-io/togglebox/tree/main/.claude/skills/writing-tools
Command: npx skills add https://github.com/ulpi-io/togglebox --skill writing-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, test-driven approach to creating, editing, and verifying skill documentation. It combines RED-GREEN-REFACTOR workflows, Anthropic best practices for token efficiency and progressive disclosure, and persuasion principles to produce bulletproof, reusable Skill Units.

Core Features & Use Cases

  • Enforces the RED-GREEN-REFACTOR cycle for skill creation and updates.
  • Guides YAML frontmatter requirements (name and description) and a concise SKILL.md body with structured sections.
  • Supports on-demand depth via references and assets to keep SKILL.md focused while enabling deeper guidance.

Quick Start

  • Create a new Skill by drafting SKILL.md with frontmatter and a concise body.
  • If needed, populate references/ to store deep guidance and examples.

Frequently Asked Questions about writing-tools

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

FAQPage Schema
How do I standardize skill documentation using a test-driven workflow?

Standardize skill documentation by enforcing a test-driven red-green-refactor workflow that validates baseline failures, iterates green implementations, and explicitly refactors across discipline, technique, and reference skill types.

What YAML frontmatter is required for a valid SKILL.md file?

A valid SKILL.md file requires YAML frontmatter containing name and description fields, followed by a concise body with structured sections to ensure standardized skill documentation.

How does progressive disclosure work when writing skill documentation?

Progressive disclosure keeps the SKILL.md body focused and concise while enabling deeper guidance on demand through optional references, scripts, and assets directories that support extended content.

Can I use this test-driven approach to edit existing skills, or is it only for creating new ones?

The test-driven red-green-refactor workflow applies to both creating and editing skills, validating baseline failures and iterating implementations across discipline, technique, and reference skill types.

What is the best way to structure skill documentation to maintain quality and token efficiency?

Structure skill documentation by combining a concise SKILL.md body with structured sections, YAML frontmatter, and on-demand references to achieve token efficiency and maintain quality through iterative refactoring.

When should I not use a test-driven approach for skill writing?

Avoid test-driven skill writing when rapid prototyping without validation is needed, as this workflow enforces baseline failure validation and iterative green implementations before refactoring.