WORKFLOWS

Create and evaluate Claude Agent Skills with structured file hierarchies.

2|2|Updated Feb 9, 2017
One-click install
npx skills add https://github.com/sumik5/dotfiles --skill workflows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: WORKFLOWS
Source: https://github.com/sumik5/dotfiles/tree/main/claude-code/skills/authoring-skills/WORKFLOWS.md
Command: npx skills add https://github.com/sumik5/dotfiles --skill workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide documents evaluation-driven development, skill creation workflows, and iteration loops for Claude Skills.

Core Features & Use Cases

  • Evaluation-first: Build tests and scenarios before writing content.
  • Progressive disclosure: SKILL.md should be concise; details live in structured files.
  • Quality gates: Pre-release checklists and governance.

Quick Start

Create a new skill skeleton with SKILL.md and a minimal description.

Frequently Asked Questions about WORKFLOWS

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

FAQPage Schema
How do I create a Claude Agent Skill with proper naming and structure?

Skill authoring requires gerund naming (lowercase, hyphens, max 64 chars), third-person descriptions under 1024 chars with explicit triggers, and a SKILL.md under 500 lines. Progressive disclosure keeps the main file concise while detailed content lives in structured sub-files referenced one level deep.

What evaluation-driven development approach should I use when building Skills?

Evaluation-driven development builds tests and scenarios before writing content. This workflow ensures quality gates are met pre-release and helps authors iterate efficiently by establishing clear acceptance criteria upfront rather than testing after implementation.

How should I organize documentation and progressive disclosure in a Skill?

Progressive disclosure structures Skills with a concise SKILL.md overview and references to detailed files organized hierarchically one level deep. This keeps the main file scannable while making comprehensive information accessible without overwhelming initial readers.

What naming constraints and description guidelines must Skills follow?

Skills require lowercase hyphenated names (max 64 chars, no reserved words), third-person descriptions stating triggers and key terms within 1024 chars, and a table of contents for SKILL.md files exceeding standard length to support usability.

When should I use pre-release checklists and governance gates for Skills?

Pre-release quality gates validate that naming, descriptions, triggers, and file hierarchies meet standards before publication. Governance checkpoints catch structural and content issues early, reducing iteration cycles and ensuring consistent author experience.