skill-health-check

Validate skill.md YAML frontmatter, line limits, and coordination metadata in skills/ repositories.

8|1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/bordenet/superpowers-plus --skill skill-health-check-bordenet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-health-check
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/observability/skill-health-check
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill skill-health-check-bordenet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structural issues in skill files often go unnoticed, causing broken pipelines and failed CI checks. This skill provides cheap, automated lint to catch missing front‑matter fields, line‑count violations, and coordination metadata problems before they break builds.

Core Features & Use Cases

  • YAML front‑matter validation: ensures required fields (name, source, triggers, description) exist.
  • Line‑count enforcement: flags any skill.md exceeding 250 lines.
  • Coordination metadata check: requires group, order, and internal keys.
  • Failure Modes warning: alerts when a ## Failure Modes section is missing.
  • Use case: Run after bulk changes to the skills/ folder to prevent merge‑time errors.

Quick Start

Ask the assistant to run the skill‑health‑check on the repository to validate all skill files.

Frequently Asked Questions about skill-health-check

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

FAQPage Schema
How do I validate YAML frontmatter in skill definition files?

Validate YAML frontmatter in skill definition files by running a structural lint check that ensures required fields like name, source, triggers, and description exist before they break builds.

What is the best way to lint skill.md files for structural issues?

Linting skill.md files for structural issues involves checking YAML frontmatter, enforcing a 250-line count limit, and verifying coordination metadata to prevent broken pipelines and failed CI checks.

Do I need Ruby to parse YAML and check skill file structure?

You need a Ruby environment to parse YAML when checking skill file structure, but the validation can be executed via provided shell commands without requiring any external dependencies.

How do I check coordination metadata in a skills directory?

Check coordination metadata in a skills directory by validating that required keys like group, order, and internal exist within the YAML frontmatter of all skill.md files.

Why does my CI pipeline fail after bulk changes to skill files?

CI pipelines fail after bulk changes to skill files when structural issues like missing frontmatter fields, line-count violations over 250 lines, or missing Failure Modes sections go unnoticed.

Can I detect missing Failure Modes sections in skill definition files?

You can detect missing Failure Modes sections in skill definition files by running a structural lint check that alerts when the required section is absent from the skill.md document.