One-click install
npx skills add https://github.com/cloudfieldcz/cf-powers --skill writing-skills-cloudfieldcz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/cloudfieldcz/cf-powers/tree/main/skills/writing-skills
Command: npx skills add https://github.com/cloudfieldcz/cf-powers --skill writing-skills-cloudfieldcz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing high-quality Skills is complex and error-prone without a repeatable process; this guide enforces a TDD approach to documentation to ensure Skills are discoverable, verifiable, and reusable.

Core Features & Use Cases

  • Provides a standardized Skill structure with YAML frontmatter (name, description) and a documented body.
  • Defines Skill Types (Discipline-enforcing, Technique, Pattern, Reference) and a deployment/readiness checklist.
  • Offers a complete Skill Creation Checklist (RED-GREEN-REFACTOR) and discovery workflow to reduce misconfigurations.

Quick Start

Create a new SKILL.md with frontmatter and a minimal body, then implement a full RED-GREEN-REFACTOR cycle and run pre-deploy validations.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write skill documentation using a TDD approach?

TDD-driven skill documentation applies a RED-GREEN-REFACTOR cycle to validate skill structure, rationalization tables, and YAML frontmatter. This ensures the documentation is verifiable, discoverable, and reusable before deployment.

What is the standard structure for creating valid skill documentation?

The standard structure for valid skill documentation requires a SKILL.md file containing YAML frontmatter with name and description fields, followed by a structured body. This enforces strict discovery metadata constraints and deployment readiness checks.

How do I validate skill metadata and frontmatter constraints before deployment?

To validate skill metadata and frontmatter constraints before deployment, you run pre-deploy validations defined in a deployment readiness checklist. This process confirms that YAML frontmatter satisfies structural constraints and discovery metadata is precise.

What types of skills can I create using a rationalization table?

Using a rationalization table, you can create four defined skill types: Discipline-enforcing, Technique, Pattern, and Reference. Each type follows the standardized TDD workflow to ensure proper categorization and deployment readiness.

Can I use this TDD workflow to update existing skills across different disciplines?

Yes, you can use this TDD workflow to update existing skills across disciplines. The process applies universally to skill creation and updates, ensuring red-green-refactor cycles and rationalization tables are maintained regardless of the specific domain.

When do I need to use a rationalization table in skill creation?

You need to use a rationalization table in skill creation when defining the deployment readiness and structural logic of the skill. It maps directly into the TDD cycle to reduce misconfigurations and ensure the skill satisfies strict discovery metadata requirements.