writing-skills

Automate SKILL.md creation and verification with TDD-inspired practices.

3|1|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/I-Onlabs/claude-code-skills --skill writing-skills-i-onlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/I-Onlabs/claude-code-skills/tree/main/writing-skills
Command: npx skills add https://github.com/I-Onlabs/claude-code-skills --skill writing-skills-i-onlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps Skill authors treat documentation as a repeatable, tested process, ensuring SKILL.md is concise, discoverable, and deploy-ready.

Core Features & Use Cases

  • Structured frontmatter-driven SKILL.md with a progressive-disclosure body that Claude can load on demand.
  • Red-Green-Refactor workflow for Skill creation, editing, and verification, including testing patterns with subagents.
  • Clear deployment readiness checks, quality gates, and governance to prevent untested, ambiguous, or poorly-organized Skills.

Quick Start

Draft the SKILL.md with a concise frontmatter and a minimal, actionable plan to test the skill 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 principles to write and verify SKILL.md documentation?

Apply TDD to SKILL.md documentation by using a Red-Green-Refactor workflow to draft, test, and verify skill content before deployment. This enforces YAML frontmatter requirements and progressive-disclosure structure for safe, discoverable skills.

What is progressive-disclosure structure for skill docs and when do I need it?

Progressive-disclosure structure is a documentation pattern that keeps SKILL.md concise upfront while allowing Claude to load detailed body sections on demand. You need it when authoring skills that require both discoverability and deep contextual guidance.

How do I set up quality assurance checks for skill authoring and deployment readiness?

Set up quality assurance checks for skill authoring by defining governance gates that evaluate YAML frontmatter compliance, structural clarity, and test verification. These checks prevent untested, ambiguous, or poorly-organized skills from reaching deployment.

Does this skill authoring workflow support testing patterns with subagents?

Yes, the skill authoring workflow supports testing patterns with subagents as part of its Red-Green-Refactor cycle. Subagents are used to verify skill behavior and enforce evaluation guidelines before a skill is considered deploy-ready.

What's the best way to structure YAML frontmatter for a reusable SKILL.md file?

The best way to structure YAML frontmatter for a reusable SKILL.md file is to enforce strict metadata requirements that ensure discoverability and safe deployment. This frontmatter drives the automated verification and governance checks across the skill lifecycle.

Why does my skill documentation fail deployment readiness checks?

Skill documentation fails deployment readiness checks when it lacks required YAML frontmatter, violates progressive-disclosure structure, or misses evaluation guidelines. The governance process blocks untested, ambiguous, or poorly-organized skills from deployment.