writing-skills

Apply the RED-GREEN-REFACTOR workflow to transform documentation into testable Skill Units.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/involvex/image-wizard-cli --skill writing-skills-involvex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/involvex/image-wizard-cli/tree/main/.gemini/skills/writing-skills
Command: npx skills add https://github.com/involvex/image-wizard-cli --skill writing-skills-involvex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing skills are often under-tested references that drift over time and fail to prevent repeating mistakes. This skill formalizes TDD-like discipline for process documentation by turning guidelines into testable Skill Units and capturing failure patterns, rationalizations, and counters to keep guidance accurate and reusable.

Core Features & Use Cases

  • RED-GREEN-REFACTOR workflow for skill creation, validation, and refinement.
  • Minimal, frontmatter-driven SKILL.md structure with inline guidance and optional references for heavy material.
  • Progressive disclosure patterns that load heavy references only when needed, reducing token usage.
  • Standardized metadata for discoverability and cross-skill references, plus testing-first mindset for reliable deployment.
  • Suitable for teams documenting patterns, checklists, and reference material across projects.

Quick Start

Draft a failing baseline scenario, then write a minimal skill that passes the scenario and iterate until no new rationalizations emerge.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I apply TDD patterns to process documentation?

Testing process documentation involves applying the RED-GREEN-REFACTOR workflow to turn guidelines into testable Skill Units. You draft a failing baseline scenario, write a minimal skill that passes it, and iterate until no new rationalizations emerge.

What is the RED-GREEN-REFACTOR workflow for skill creation?

The RED-GREEN-REFACTOR workflow for skill creation is a testing-first discipline that transforms documentation into validated Skill Units. RED captures failure patterns, GREEN writes minimal passing guidance, and REFACTOR refines progressive disclosure content to keep references accurate and reusable.

How do I structure a SKILL.md file to reduce token usage?

Structure a SKILL.md file with minimal frontmatter, clear problem statements, and progressive disclosure patterns to reduce token usage. This frontmatter-driven approach loads heavy references only when needed, keeping inline guidance concise and reliable for deployment.

Why does process documentation drift over time and fail to prevent mistakes?

Process documentation drifts over time because guidelines are often under-tested references lacking failure pattern capture. Without a testing-first mindset capturing rationalizations and counters, documentation fails to prevent repeating mistakes and loses accuracy across projects.

Can I use this approach to document team checklists and reference material?

Yes, you can use this approach to document team checklists and reference material across projects. The workflow formalizes TDD-like discipline for process documentation, making it suitable for teams documenting patterns by capturing failure patterns and rationalizations to keep guidance accurate.

What metadata fields are required for skill discoverability?

Required metadata fields for skill discoverability include standardized frontmatter fields, category alignment, keywords, and safety checks. Enforcing these metadata fields ensures cross-skill references work properly and allows users to find relevant guidance reliably.