writing-skills

Apply RED-GREEN-REFACTOR cycles to author SKILL.md documentation.

14|5|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/cloudbro-kube-ai/k13d --skill writing-skills-cloudbro-kube-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/cloudbro-kube-ai/k13d/tree/main/skills/superpowers/writing-skills
Command: npx skills add https://github.com/cloudbro-kube-ai/k13d --skill writing-skills-cloudbro-kube-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing skills provide a structured, test-driven approach to creating and maintaining process documentation for skills, ensuring consistency, testability, and repeatable quality across teams.

Core Features & Use Cases

  • TDD-driven skill authoring: apply the RED-GREEN-REFACTOR cycle to skill creation, ensuring baseline failures are observed before writing content.
  • Structured SKILL.md templates: frontmatter with name and description, plus inline guidance for organization, references, and tooling.
  • Progressive disclosure and references: guidance on keeping inline content lean while linking to heavy references when needed; supports multi-domain skills with light references for discovery.
  • Quality and safety checks: guidance on rationalization capture, red flags, and deployment/testing workflows to prevent regressions.
  • Cross-skill reuse: instructions for cross-referencing other skills and modular organization to minimize context load.

Quick Start

Write a new SKILL.md for a targeted capability, then run RED-GREEN-REFACTOR cycles against baseline agent behavior to verify compliance 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 TDD to skill writing for agent documentation?▼

TDD-driven skill writing applies a RED-GREEN-REFACTOR cycle to validate documentation against baseline agent behavior, ensuring observed failures are remediated before deployment. You write a SKILL.md, run baseline tests, then refactor content for compliance.

What is progressive disclosure in SKILL.md frontmatter and inline content?▼

Progressive disclosure keeps inline SKILL.md content lean for fast discovery while linking to heavy references when deeper exploration is needed. This minimizes context load and supports multi-domain skills with light references.

How do I structure a SKILL.md template for reusable techniques?▼

SKILL.md templates use lightweight frontmatter with name and description, plus inline guidance for organization, references, and tooling. This structure ensures consistency, testability, and repeatable quality across teams.

Can I cross-reference other skills to minimize context load in documentation?▼

Cross-referencing other skills allows modular organization to minimize context load. The guide provides instructions for cross-referencing, enabling cross-skill reuse without duplicating heavy content inline.

What quality assurance checks are needed for skill deployment workflows?▼

Quality assurance checks include capturing rationalizations, monitoring red flags, and running deployment workflows to prevent regressions. These ensure baseline failures are observed and remediated during the RED-GREEN-REFACTOR cycle.

When should I not use TDD-driven skill writing guides?▼

Avoid TDD-driven skill writing when documentation does not require repeatable quality or testability against agent behavior. It is designed for structured process documentation needing compliance validation, not lightweight ad-hoc notes.