writing-skills

Automate SKILL.md creation and validation with RED-GREEN-REFACTOR tests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bjconlan/burndown --skill writing-skills-bjconlan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/bjconlan/burndown/tree/main/.gemini/skills/writing-skills
Command: npx skills add https://github.com/bjconlan/burndown --skill writing-skills-bjconlan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing skills require a disciplined, test-driven approach to creating and validating process documentation; this guide provides a framework to write, test, and refine Skill units to ensure consistency and readiness before deployment.

Core Features & Use Cases

  • Provides a structured template to create new skills, edit existing ones, and verify readiness before release
  • Enforces the RED-GREEN-REFACTOR cycle, explicit rationalization capture, and deployment checklists
  • Includes references to best practices and progressive disclosure patterns to manage large Skill bodies

Quick Start

Create a minimal SKILL.md for a new technique, then run a baseline RED test before deployment.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I use a test-driven approach to write process documentation?

A test-driven approach to process documentation applies the RED-GREEN-REFACTOR workflow to write, test, and refine skills, ensuring repeatable quality checks and consistency before deployment.

What is the best way to structure SKILL.md frontmatter for validation?

To structure SKILL.md frontmatter for validation, include the required name and description fields, then write verification tests to enforce readiness before release.

How do I validate skill readiness before deployment?

You validate skill readiness before deployment by running a baseline RED test on a minimal SKILL.md, then progressing through the RED-GREEN-REFACTOR cycle and checking deployment checklists.

Can I use progressive disclosure to manage large skill bodies?

Yes, you can use progressive disclosure patterns to manage large skill bodies, allowing you to structure complex documentation into easily consumable sections without overwhelming the reader.

Does skill authoring require explicit rationalization capture?

Yes, skill authoring requires explicit rationalization capture to document the reasoning behind design decisions, ensuring process docs maintain consistency and pass repeatable quality checks.