skill-curator

Author and maintain Claude/Cowork skills with consistent YAML frontmatter and canonical structure.

2|Updated Feb 28, 2024
One-click install
npx skills add https://github.com/coagus/php-api-builder --skill skill-curator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-curator
Source: https://github.com/coagus/php-api-builder/tree/main/.claude/skills/skill-curator
Command: npx skills add https://github.com/coagus/php-api-builder --skill skill-curator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill Curator provides a canonical framework for authoring and maintaining Claude/Cowork skill documentation, ensuring consistent frontmatter, predictable structure, and clear guidelines for references and versioning.

Core Features & Use Cases

  • Canonical skill structure: SKILL.md frontmatter with name and description, plus an actionable body.
  • Optional resources: references/, assets/, and scripts/ directories when needed.
  • Versioning and cross-referencing: guidelines for semver bumps and relative linking to sibling skills.

Quick Start

Create a new folder under .claude/skills with a SKILL.md containing a name and description, then optionally add references/ for deep-dives and a changelog for version tracking.

Frequently Asked Questions about skill-curator

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

FAQPage Schema
How do I structure a Claude skill with YAML frontmatter?

To structure a Claude skill, create a SKILL.md file with YAML frontmatter containing name and description fields, followed by an actionable body. Optional references, assets, and scripts directories can be added for deeper resources.

What is the canonical structure for authoring Claude skills?

The canonical structure for authoring Claude skills requires a SKILL.md file with YAML frontmatter including name and description, an actionable body, and optional directories for references, assets, scripts, and a changelog for version tracking.

How do I version and cross-reference Claude skills?

Versioning and cross-referencing Claude skills involves applying semantic versioning bumps in a changelog and using relative links to connect sibling skills within the .claude/skills directory structure.

Do I need a references directory to create a valid skill?

A references directory is not required to create a valid skill. The only mandatory elements are a SKILL.md file with YAML frontmatter containing the name and description fields, plus an actionable body.

What's the best way to maintain consistent documentation across multiple skills?

The best way to maintain consistent documentation is to follow canonical skill structure guidelines, ensuring predictable YAML frontmatter, proper section ordering, semver versioning, and relative cross-linking between sibling skills.

Why does my skill documentation need a changelog and trigger phrasing?

A changelog provides version tracking through semantic versioning, while trigger phrasing ensures the skill activates correctly. Both are part of maintaining consistent and predictable skill documentation structure.