writing-skills

Codify YAML frontmatter and three-level progressive disclosure for Claude Skill authoring.

Updated Sep 1, 2025
One-click install
npx skills add https://github.com/walsh-investment/clean-slate-import --skill writing-skills-walsh-investment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/walsh-investment/clean-slate-import/tree/main/.claude/skills/writing-skills
Command: npx skills add https://github.com/walsh-investment/clean-slate-import --skill writing-skills-walsh-investment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured blueprint and best practices for authoring Claude Skills that are concise, well-organized, and auditable, reducing onboarding time and errors.

Core Features & Use Cases

  • Guidance on YAML frontmatter with name and description, enforcing triggering conditions and a three-level progressive disclosure model.
  • Emphasis on RED-GREEN-REFACTOR testing workflows and rationalization tracking to ensure robust Skill design.
  • Templates and patterns for consistent Skill structure (SKILL.md, references/, scripts/, assets/) enabling scalable Skill libraries.

Quick Start

Draft a new Skill by creating SKILL.md with frontmatter name and description, then populate the top-level sections following the three-level loading approach.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I structure Claude Skills using progressive disclosure and YAML frontmatter?▼

Structure Claude Skills by codifying frontmatter-driven authoring with a three-level progressive disclosure model. Start with YAML frontmatter containing name and description, then populate top-level sections to standardize creation and ensure consistent metadata.

What is the best way to standardize Skill creation and updates across Skill families?▼

The best way to standardize Skill creation is enforcing a structured blueprint with YAML frontmatter, clear triggering conditions, and lightweight references for progressive loading. This ensures consistent metadata and auditable structures across Skill families.

How does test-driven development apply to writing Skills?▼

Test-driven development applies to Skill writing through RED-GREEN-REFACTOR testing workflows and rationalization tracking. This approach ensures robust Skill design by validating triggering conditions and structural integrity before deployment.

What files and directories do I need to build a scalable Skill library?▼

Building a scalable Skill library requires consistent templates and patterns including SKILL.md, references, scripts, and assets directories. This structure enables organized progressive loading and reduces onboarding time and errors.

Do I need a specific testing workflow to create a new Skill?▼

Yes, a RED-GREEN-REFACTOR testing workflow is recommended to ensure robust Skill design. You draft SKILL.md with frontmatter, then validate the concise problem-focused description and Quick Start actionable instruction against triggering conditions.

Why does my Skill description need to be problem-focused with a single actionable Quick Start?▼

A problem-focused description and single actionable Quick Start are enforced to ensure concise, well-organized, and auditable Skills. This structure reduces onboarding time by providing immediate clarity on the Skill's purpose and execution.