writing-skills

Apply test-driven development cycles to validate SKILL.md documentation.

4|Updated Oct 3, 2025
One-click install
npx skills add https://github.com/apexbusiness-systems/APEX-OmniHub --skill writing-skills-apexbusiness-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/apexbusiness-systems/APEX-OmniHub/tree/main/.cursor/superpowers/skills/writing-skills
Command: npx skills add https://github.com/apexbusiness-systems/APEX-OmniHub --skill writing-skills-apexbusiness-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to writing and validating Skill documentation by enforcing a test-driven development style, ensuring frontmatter correctness, and enabling progressive disclosure patterns for reusable knowledge.

Core Features & Use Cases

  • Structured SKILL.md authoring: Enforces YAML frontmatter with name and description and a well-organized body that supports modular references.
  • Test-driven documentation cycles: Guides writers to generate failing baseline documentation, iterate with subagents to achieve compliance, and deploy with confidence.
  • Quality governance patterns: Introduces red flags, rationalization tracking, and deployment readiness checks to maintain rigor across Skills.

Quick Start

To begin, create a Skill folder with a SKILL.md containing a valid YAML frontmatter and a concise guide. Then follow the RED-GREEN-REFACTOR loop to validate the Skill against baseline tests 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 apply test-driven development to process documentation?

Test-driven process documentation uses a red-green-refactor loop to generate failing baseline docs, iterate with subagents for compliance, and deploy validated skills. This reduces rationalization and ensures bulletproof process documentation.

What is the correct YAML frontmatter structure for SKILL.md files?

SKILL.md authoring requires valid YAML frontmatter with name and description fields, followed by a well-organized body supporting modular references. This structure enforces progressive disclosure patterns for reusable knowledge.

How do I validate skill documentation before deploying across Claude-like agents?

Validate skill documentation using deployment readiness checks and quality governance patterns. These introduce red flags and rationalization tracking to maintain rigor before deploying skills across Claude-like agents.

Can I use subagents to iterate on failing documentation during the writing process?

Yes, the test-driven documentation cycle guides writers to generate failing baseline documentation and iterate with subagents to achieve compliance. This ensures frontmatter correctness and structure before deployment.

What is the best way to structure skill documentation for reusable knowledge?

Structure skill documentation by enforcing YAML frontmatter correctness and a well-organized body supporting modular references. This enables progressive disclosure patterns for reusable knowledge across teams.

When should I use a red-green-refactor workflow for skill writing?

Use a red-green-refactor workflow when creating new skills, editing existing skills, or verifying skills before deployment. It enforces structure, frontmatter correctness, and a repeatable cycle to reduce rationalization.