find-catalog-gaps

Identify tools referenced in audits but missing from CATALOG.md.

2|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/mattbutlerengineering/ai-tooling --skill find-catalog-gaps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-catalog-gaps
Source: https://github.com/mattbutlerengineering/ai-tooling/tree/main/.claude/skills/find-catalog-gaps
Command: npx skills add https://github.com/mattbutlerengineering/ai-tooling --skill find-catalog-gaps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Find tools that probably belong in CATALOG.md but aren't there, via referenced-but-not-catalogued detection + a foundational-tools checklist. Use to audit the catalog for missing heavyweight tools. Triggers - "find catalog gaps", "what's missing from the catalog", "audit catalog completeness".

Core Features & Use Cases

  • Detects tools that are referenced but not catalogued (detector F) and uses a foundational checklist to surface heavyweight tooling lacking catalog entries.
  • Generates a candidate list for human vetting, guiding decision-makers to extend CATALOG.md with new entries after review.
  • Supports ongoing catalog hygiene by enabling quick audits of completeness and consistency across tool references.

Quick Start

Run the find-catalog-gaps script to surface catalog gaps and prepare review notes.

Frequently Asked Questions about find-catalog-gaps

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

FAQPage Schema
How do I find tools that are missing from my CATALOG.md?

To find catalog gaps, run a detection process that compares tool references in audits against CATALOG.md entries. It surfaces missing heavyweight tools by checking for referenced-but-not-catalogued items and evaluating a foundational checklist to produce candidates for human vetting.

What is the best way to audit catalog completeness for missing tool references?

Auditing catalog completeness involves running an automated script that uses detector F and a foundational checklist to identify referenced tools lacking catalog entries. This surfaces candidates for human vetting to guide new catalog entry creation and maintain hygiene.

How does referenced-but-not-catalogued detection work for tool catalogs?

Referenced-but-not-catalogued detection works by scanning audit data for tool references and overlaps, then cross-referencing these against CATALOG.md. It flags heavyweight tools appearing in audits but lacking corresponding catalog entries for human review.

Can I use this catalog gap detection for ongoing tooling hygiene?

Yes, you can use this catalog gap detection for ongoing tooling hygiene by running quick audits of completeness and consistency across tool references. It generates candidate lists of missing heavyweight tools to guide catalog entry updates.

Do I need any dependencies to run the catalog gap finder?

No dependencies are required to run the catalog gap finder. The script operates independently to surface missing heavyweight tools from audits and prepare review notes for human vetting.