skills-audit

Scan SKILL.md frontmatter and apply lint, hierarchy, and health checks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jforksy/claude-skills --skill skills-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skills-audit
Source: https://github.com/jforksy/claude-skills/tree/main/skills-audit
Command: npx skills add https://github.com/jforksy/claude-skills --skill skills-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits and validates the entire skills ecosystem, ensuring consistent structure, cross-references, and health metrics across all skills.

Core Features & Use Cases

  • Full audit of all skills to identify orphaned or misconfigured items
  • Linting of individual skills to enforce frontmatter and metadata standards
  • Generate a hierarchy view of skills to visualize ownership and dependencies
  • Health dashboard snippets to track global metrics

Quick Start

Run /skills-audit to perform a full audit across all skills. Example: /skills-audit lint gtm-icp

Frequently Asked Questions about skills-audit

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

FAQPage Schema
How do I audit Claude skills metadata for missing frontmatter and broken cross-references?

You can audit Claude skills by scanning all SKILL.md frontmatter in the local skills directory, building a metadata map, and running lint, hierarchy, and health checks to validate frontmatter completeness, parent relationships, and cross-references.

What is the best way to check skills hierarchy and identify orphaned items in my local directory?

The best way to check skills hierarchy and identify orphaned items is to run a full ecosystem audit that scans all local skill files, maps parent-child relationships, and reports any misconfigured or orphaned metadata entries.

Can I lint individual skills to enforce metadata standards without modifying the files?

Yes, you can lint individual skills to enforce frontmatter and metadata standards while keeping files unmodified. The audit process reads from the local skills directory and writes no changes, reporting validation findings only.

Does the skills audit require any external dependencies or specific environment setup?

The skills audit requires no external dependencies or complex environment setup. It operates natively by reading directly from the ~/.claude/skills/ directory to evaluate your local skills ecosystem health and cohesion.