writing-skills

Apply test-driven development to validate SKILL.md documentation and frontmatter.

4|1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/pynbj1001/alpha-sense --skill writing-skills-pynbj1001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/pynbj1001/alpha-sense/tree/main/skills/15.%20superpowers/skills/writing-skills
Command: npx skills add https://github.com/pynbj1001/alpha-sense --skill writing-skills-pynbj1001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill documentation workflow helps teams ensure consistent quality by applying test-driven development to skill creation and verification, catching gaps before deployment.

Core Features & Use Cases

  • TDD-based skill creation workflow that ties tests to skill documentation.
  • Frontmatter-driven discovery with required name and description.
  • Structured SKILL.md sections guiding content: overview, usage, validation, and safety checks.

Quick Start

Create a new SKILL.md with proper frontmatter, draft the skill content following the RED-GREEN-REFACTOR cycle, and run the baseline tests to verify behavior.

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 skill documentation?

TDD for skill documentation validates the SKILL.md workflow by defining baseline tests that fail without the skill and pass when it meets frontmatter and content standards, ensuring consistent quality before deployment.

What is the RED-GREEN-REFACTOR cycle for writing skill documentation?

The RED-GREEN-REFACTOR cycle for skill documentation involves drafting content to fail validation tests, updating SKILL.md to satisfy frontmatter and content requirements, and refining the structure for safety and quality checks.

How do I validate YAML frontmatter when creating a SKILL.md file?

Validating YAML frontmatter requires ensuring the SKILL.md file includes mandatory name and description fields, which the TDD workflow then uses to drive discovery and execute baseline verification tests.

What are the required sections for a well-structured SKILL.md description body?

A well-structured SKILL.md description body requires sections guiding content for an overview, usage, validation, and safety checks, ensuring the skill passes safety and quality validations during the TDD workflow.

Why does my skill verification fail without a properly structured SKILL.md file?

Skill verification fails without a properly structured SKILL.md file because baseline tests are designed to fail when required frontmatter or structured content sections are missing or do not meet defined content standards.