audit-library-health
The audit-library-health skill runs a series of diagnostic commands to verify that an AI agent skills library is consistent, properly documented, and ready for distribution. Use this skill when validating a skills library before sharing or installing it, checking for broken installs, outdated skills, missing documentation, and catalog integrity issues.
git clone --depth 1 https://github.com/MoizIbnYousaf/Ai-Agent-Skills /tmp/audit-library-health && cp -r /tmp/audit-library-health/skills/audit-library-health ~/.claude/skills/audit-library-healthSKILL.md
# Audit Library Health ## Goal Verify that a skills library is consistent, up-to-date, and ready to share or install from. ## Guardrails - Always use `--format json` for structured output when automating health checks. - Always use `--dry-run` before running `build-docs` to check if docs are already in sync. - Never push a library to a shared repo without passing `validate` and `doctor` first. - Use `--fields` to limit output when inspecting large catalogs. ## Workflow 1. Run the validation script to check catalog integrity. ```bash npx ai-agent-skills validate ``` This checks: required fields, folder consistency, frontmatter validity, collection integrity, and generated doc sync. 2. Run doctor to check installed skills health. ```bash npx ai-agent-skills doctor --format json ``` 3. Check for skills that may need updates. ```bash npx ai-agent-skills check --format json ``` 4. Verify generated docs are in sync. ```bash npx ai-agent-skills build-docs --dry-run --format json ``` If `currentlyInSync` is false, regenerate: ```bash npx ai-agent-skills build-docs ``` 5. Review the curation queue for skills needing attention. ```bash npx ai-agent-skills curate review --format json ``` ## Health Checklist - [ ] `validate` passes with no errors - [ ] `doctor` reports no broken installs - [ ] `build-docs --dry-run` shows docs are in sync - [ ] No skills with empty `whyHere` fields - [ ] All house skills have matching folders in `skills/` - [ ] `skills.json` total matches actual skill count ## Gotchas - `validate` and `doctor` are read-only — they never mutate the library. - `check` makes network requests to verify upstream sources. It may be slow or timeout on unreachable repos. - The `curate review` queue is derived from missing fields and stale verification dates — it is a heuristic, not a mandate.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.
>-
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
Use when regenerating README.md and WORK_AREAS.md in a managed library workspace. Always dry-run first to preview changes.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.