sparkleware-catalog

Enriches registry with live GitHub signals to generate a catalog and delta report weekly.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill sparkleware-catalog-atrium-hermes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sparkleware-catalog
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/sparkleware-catalog
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill sparkleware-catalog-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly enrichment of the static skill registry with live GitHub signals to produce a machine-readable, up-to-date catalog of skill packs.

Core Features & Use Cases

  • Registry enrichment: join the canonical skill-packs.json with live repo signals (stars, last push) and manifest counts to surface accurate pack health.
  • Catalog generation: output skill-packs-catalog.json and a human-friendly article for operators, dashboards, and external tools like Sparkleware.
  • Delta awareness: detect reachability, drift between registry and live manifests, and provide stable outputs for downstream consumers.

Quick Start

Run the sparkleware-catalog skill to refresh skill-packs-catalog.json from skill-packs.json.

Frequently Asked Questions about sparkleware-catalog

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

FAQPage Schema
How do I automate a live skill-packs catalog from a static registry and GitHub data?

You can automate a live skill-packs catalog by joining a static skill-packs.json registry with live GitHub repo signals and manifest counts to generate a versioned, machine-readable catalog output.

What is skill registry enrichment and how does it detect manifest drift?

Skill registry enrichment compares a canonical skill-packs.json file against live GitHub manifests to detect reachability, identify drift between registry entries and live repos, and calculate total live skills across packs.

How do I generate a machine-readable catalog file from GitHub repo metadata?

Query GitHub via the gh api for repo metadata and manifests, join the results with your static registry, and write a versioned catalog payload to skill-packs-catalog.json alongside a human-readable article.

Can I schedule weekly catalog updates and receive delta notifications for registry changes?

Yes, the catalog enrichment operates on a weekly cadence to detect reachability, drift, and total live skills, emitting a structured notification when changes occur between the baseline and delta outputs.

Does the catalog generation process require any external dependencies or components?

No external dependencies or components are required; the process relies entirely on reading skill-packs.json and querying GitHub via gh api to build the versioned catalog payload.

Why does my skill-packs catalog show drift between the registry and live manifests?

Drift occurs when the static skill-packs.json registry entries no longer match the live GitHub manifest counts or repo metadata signals, indicating the registry needs enrichment to restore accuracy.