analyze-and-plan

Extract metadata from SKILL.md frontmatter for valid Skill units.

Updated Apr 18, 2026

Search Tags:#repository #metadata #frontmatter #analyze #skill-unit #cpedia

Ready to run

npx skills add https://github.com/Royincog/cpedia --skill analyze-and-plan-royincog

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze-and-plan
Source: https://github.com/Royincog/cpedia/tree/main/.agents/skills/analyze-and-plan
Command: npx skills add https://github.com/Royincog/cpedia --skill analyze-and-plan-royincog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The repository's Skill units can be missed or misidentified during large-scale audits. This guide helps automatically detect valid Skill units by verifying the mandatory SKILL.md frontmatter and extracting core fields to enable consistent discovery.

Core Features & Use Cases

Validates Skill unit presence by ensuring SKILL.md exists at the root and includes name and description in YAML frontmatter.
Extracts metadata fields such as name, description, license, version, and dependencies for each Skill unit.
Generates structured outputs suitable for indexing, search, and documentation pipelines across multi-repo projects.

Quick Start

Analyze a repository to produce a structured Skill metadata report.

Frequently Asked Questions about analyze-and-plan

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

FAQPage Schema

How do I extract metadata from multiple Skill units in a repository?▼

Scanning a repository for SKILL.md frontmatter extracts metadata for each Skill unit. It validates units by checking for mandatory name and description fields, then generates structured YAML metadata for indexing.

What is the best way to validate Skill units during a large-scale repository audit?▼

Validating Skill units requires verifying SKILL.md exists at the root with YAML frontmatter. This prevents missing or misidentified units during large-scale audits by ensuring mandatory name and description fields are present.

How does YAML frontmatter parsing work for repository metadata extraction?▼

YAML frontmatter parsing locates SKILL.md files and extracts structured fields. It identifies valid Skill units by checking for mandatory name and description tags, then maps them to structured outputs for indexing and documentation.

Can I use this metadata extraction for repositories with multiple Skill units?▼

Yes, this metadata extraction applies to repositories with multiple Skill units. It iterates through each unit to validate SKILL.md frontmatter and generate individual YAML metadata reports including dependencies and toxicity assessments.

What fields are extracted when analyzing SKILL.md frontmatter?▼

Analyzing SKILL.md frontmatter extracts fields including name, tagline, description, category, keywords, version, license, dependencies, components, and toxicity evaluation to generate a comprehensive YAML metadata profile.

Why are Skill units missed or misidentified during repository scans?▼

Skill units are missed during repository scans when mandatory SKILL.md files lack proper YAML frontmatter. Validating the presence of name and description fields ensures consistent discovery and prevents misidentification across multi-repo projects.