audit

Validates skill folder names, SKILL.md frontmatter, and catalog consistency under kit/skills/.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Broken skill layouts — a missing SKILL.md, a mismatched name: field, a nested skill, or a catalog row that no longer matches the source tree — abort the build and block pull requests. This skill reports every such problem at once, read-only, so the tree can be fixed before building or before CI fails. ## Core Features & Use Cases - Layout validation: Detects non-directory entries, missing SKILL.md files, nested skills, and folder names that violate the hos-<name> naming pattern. - Frontmatter checks: Reports missing name: fields and name values that disagree with the folder name. - Catalog consistency: Compares docs/skills.md and docs/skills.ja.md tables and boundary bullets against the actual skills under kit/skills/, in both directions. - Use Case: Before opening a pull request that adds or renames a skill, run the audit to list every layout and catalog problem in one report instead of discovering them one build failure at a time. ## Quick Start Ask the agent to run the audit skill to check every skill under kit/skills/ and report any layout or catalog problems before opening the pull request.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I validate skill folders before a build?

Run npm run skill-names or node .claude/skills/audit/scripts/audit.js. The script scans kit/skills/, prints one group per problem kind, and exits non-zero when any problem exists, so the tree can be fixed before building.

What naming rules apply to skill folder names?

Folder names must match the pattern hos-<name>, lowercase letters, digits, and hyphens up to 60 characters after the prefix. The folder name is the installed name and must equal the name: field declared in the SKILL.md frontmatter.

Does the audit script modify any files?

No, the audit is strictly read-only. It scans kit/skills/ and the two catalog documents, prints a grouped report, and sets a non-zero exit code on failure without writing anything to disk.

Why does the build fail after adding a new skill?

Common causes are a missing SKILL.md, a name: field that differs from the folder name, or catalog rows in docs/skills.md and docs/skills.ja.md not updated in both the table and boundary sections. The audit report groups all of these at once.

What does the audit not check?

It says nothing about a skill's content quality, wording, structure, or whether its description would make an agent pick it. It only keeps the layout and catalogs consistent, acting as the layout keeper rather than a reviewer.