writing-skills

Create and validate test-driven Skill documentation with YAML frontmatter and SKILL.md bodies.

793|52|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/corvo007/MioSub --skill writing-skills-corvo007
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/corvo007/MioSub/tree/main/.agent/skills/writing-skills
Command: npx skills add https://github.com/corvo007/MioSub --skill writing-skills-corvo007

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing consistent, test-driven Skill documentation helps teams create reusable, robust guidance and reduces operator rationalization during deployment.

Core Features & Use Cases

  • Enforces frontmatter with name and description, and a structured SKILL.md body
  • Provides templates for frontmatter, flow, and loading patterns
  • Use cases include creating new Skills, editing existing ones, and validating readiness before deployment

Quick Start

Create a minimal Skill that captures a known failure pattern and run a baseline test to verify compliance

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write test-driven documentation for Claude skills?

Test-driven documentation for Claude skills is created by enforcing YAML frontmatter with name and description, maintaining a concise SKILL.md body, and running baseline tests to verify compliance before deployment.

What is test-driven skill documentation and when do I need it?

Test-driven skill documentation is a structured workflow that prevents operator rationalization during deployment by enforcing frontmatter, concise SKILL.md bodies, and optional references to scripts or assets while respecting token budgets.

How do I validate skill readiness before deploying across Claude-style agents?

You validate skill readiness by capturing a known failure pattern, creating a minimal Skill, and running a baseline test to verify compliance with frontmatter, body structure, and token budget requirements.

What's the best way to structure SKILL.md files to respect Claude token budgets?

The best way to structure SKILL.md files is by keeping a concise body, applying YAML frontmatter with name and description, and using optional references to scripts or assets to optimize Claude Search and token usage.

Can I use test-driven documentation workflows for editing existing skills?

Yes, test-driven documentation workflows can be applied to editing existing skills by validating their YAML frontmatter, SKILL.md body conciseness, and reference structures to ensure deployment readiness.

Why does skill rationalization occur during agent deployment and how do I prevent it?

Skill rationalization occurs when deployment lacks structured constraints, and you prevent it by enforcing test-driven documentation with YAML frontmatter, concise SKILL.md bodies, and baseline compliance tests.