developing-claude-code-meta

Locate SKILL.md files and extract YAML frontmatter into structured metadata blocks.

Updated Dec 30, 2025
One-click install
npx skills add https://github.com/mikekelly/developing-claude-code-meta --skill developing-claude-code-meta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developing-claude-code-meta
Source: https://github.com/mikekelly/developing-claude-code-meta/tree/main
Command: npx skills add https://github.com/mikekelly/developing-claude-code-meta --skill developing-claude-code-meta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the identification of valid CLAUDE Skill units in a repository by requiring a root-level SKILL.md with a YAML frontmatter, and it standardizes the generation of machine-readable metadata for discovery and automation.

Core Features & Use Cases

  • Validates Skill units by detecting SKILL.md with mandatory name and description, then extracts metadata fields.
  • Generates a complete metadata payload for each Skill unit, including name, tagline, description, request, complexity, category, keywords, dependencies, and components.
  • Supports optional resources (scripts/, references/, assets/) and records their presence in components for downstream tooling.

Quick Start

Identify the Skill unit(s) in the repository and output a YAML metadata block for each.

Frequently Asked Questions about developing-claude-code-meta

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

FAQPage Schema
How do I generate metadata for CLAUDE Skill units in a repository?

To generate metadata for CLAUDE Skill units, the system locates a root-level SKILL.md file with YAML frontmatter and extracts fields like name, tagline, and description to output a structured YAML metadata block.

What is a valid Skill unit for automated discovery?

A valid Skill unit requires a root-level SKILL.md file containing mandatory YAML frontmatter fields, specifically a name and description, to pass validation for automated metadata extraction.

How do I extract YAML frontmatter for skill discovery and automation?

Extracting YAML frontmatter for skill discovery involves reading the SKILL.md file at the repository root and validating its contents against official definitions to generate a machine-readable metadata payload.

What happens if no valid Skill units are found in the repository?

If no valid Skill units are found during repository validation, the system returns the literal string NO_VALID_SKILLS_FOUND instead of outputting a YAML metadata block.

Does metadata generation record optional resources like scripts and references?

Metadata generation does record optional resources like scripts, references, and assets by detecting their presence and listing them in the components field of the output metadata for downstream tooling.