writing-skills

Document and validate Skills using a strict TDD workflow.

16|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Marwan78888/Neuron-Cli --skill writing-skills-marwan78888
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Marwan78888/Neuron-Cli/tree/main/scratch/superpowers-main/skills/writing-skills
Command: npx skills add https://github.com/Marwan78888/Neuron-Cli --skill writing-skills-marwan78888

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing and validating Skills is error-prone; this guide standardizes how to author, test, and maintain Skills using a TDD approach.

Core Features & Use Cases

  • Ensures SKILL.md frontmatter includes required fields (name, description)
  • Guides RED-GREEN-REFACTOR workflow for Skill validation
  • Encourages progressive disclosure and lightweight inline content with heavy references when needed

Quick Start

Create a new SKILL.md for the Skill following the TDD-based workflow.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I document and validate reusable skills using TDD?

Document and validate reusable skills by applying a strict RED-GREEN-REFACTOR TDD workflow to authoring SKILL.md files. This standardizes frontmatter, enforces safety checks, and ensures content validation.

What is the required frontmatter structure for a SKILL.md file?

The required SKILL.md frontmatter structure must include mandatory name and description fields. YAML frontmatter validation also enforces specifying dependencies, components, and toxicity declarations.

How do I create a new skill using a test-driven workflow?

Create a new skill by following the test-driven workflow: write validation tests first, create the SKILL.md structure to pass them, then refactor. This enforces progressive disclosure and lightweight inline content.

Does skill authoring require declaring dependencies and components?

Yes, skill authoring requires declaring dependencies and components in the YAML frontmatter. The validation workflow enforces these safety checks to properly rationalize skill integration.

What is the best way to structure documentation for skill validation?

The best way to structure skill validation documentation is using progressive disclosure with lightweight inline content. Use heavy references when needed to pass strict TDD validation checks efficiently.