revalidate-catalog

Re-research and re-validate catalog table rows against GitHub APIs and URL checks.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/tariqwest/ai-client-catalog --skill revalidate-catalog-tariqwest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revalidate-catalog
Source: https://github.com/tariqwest/ai-client-catalog/tree/main/.agents/skills/revalidate-catalog
Command: npx skills add https://github.com/tariqwest/ai-client-catalog --skill revalidate-catalog-tariqwest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Catalog tables tracking software tools drift out of date as versions, licenses, popularity, and URLs change, requiring tedious manual verification of every row. ## Core Features & Use Cases - Scoped Revalidation: Re-check one row by ID, a filtered subset (e.g. vendor:Anthropic, type:Workspace app), or the entire catalog table. - Live Data Refresh: Fetches latest GitHub release tags, license SPDX IDs, and stargazer counts, plus HEAD checks on homepage and repository URLs to detect broken links. - Safe Writes: Supports dry-run reporting of stale, broken, and fetch-failed fields before upserting full 16-column rows back into the master Markdown table. - Use Case: Run a dry-run over all rows limited to version and popularity fields to preview drift, then write real updates for a single tool like codex. ## Quick Start Ask the assistant to revalidate the catalog row for qwen-code in dry-run mode and report any stale version, license, or popularity values. Note: this skill is a deprecated compatibility wrapper; the merged refresh-catalog skill is the preferred entry point.

Frequently Asked Questions about revalidate-catalog

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

FAQPage Schema
How do I revalidate a single row in the catalog table?

Run the helper with the --ids flag, for example node helpers/revalidate.js --ids '["qwen-code"]' --dry-run. This selects the row by normalized ID, re-fetches its fields, and reports drift without writing changes.

How do I revalidate only a subset of catalog rows by vendor or type?

Use the --filter flag with expressions like vendor:Anthropic, type:Workspace app, or license:MIT. Multiple comma-separated clauses are ANDed, and a ! prefix negates a clause.

Does the revalidation script handle GitHub API rate limits?

Yes, it sends a User-Agent header on GitHub API calls and supports a GITHUB_TOKEN environment variable for higher limits. On 429 or 403 responses it backs off and marks fields as rate-limited rather than overwriting stored values.

What happens when a homepage or GitHub URL is broken?

The script performs a HEAD request with curl following redirects and a 5-second timeout. 4xx, 5xx, or timeout responses mark the field as broken-url in the report while keeping the old value in the table.

Can I run revalidation without modifying the catalog file?

Yes, pass --dry-run to only report stale, broken, and fetch-failed fields with a diff preview of the first three stale rows. No writes occur, so git diff shows no changes to the master table.

Should I use revalidate-catalog or refresh-catalog?

Use refresh-catalog, which merged this skill's functionality as of 2026-08-11 and handles single-row, subset, and full-table updates. revalidate-catalog remains only as a backward-compatible wrapper forwarding to it.