Expand description
Load the Prometheus skill pack into the database.
WHAT LIVES WHERE, AND WHY
Skill metadata goes in the database; skill bodies stay on disk. A
SKILL.md body can be hundreds of KB and is only needed when a skill actually
runs, so storing it in every catalog row would make listing skills expensive
for no benefit. The row carries source_path instead, and the runner reads
the body from disk when it is needed.
Config files SEED the database; they are not consulted at runtime afterwards. That is what lets a runtime API change take effect immediately on both an embedded device and a remote server — no restart, no file-polling loop.
WALKING THE PACK IS NOT NAIVE
The tree contains 211 SKILL.md files but only 140 canonical skills.
skills/imported/ holds vendored duplicates (a submodule may ship its own
.claude/, .cursor/ and .codex/ copies of the same skill), and
.cursor/ .opencode/ .windsurf/ at the repo root are generated
per-platform mirrors. Walking everything would triple-count the catalog, so
only skills/ is walked and imported/ is skipped — matching what the
pack’s own install-skills-flat.sh does.
Structs§
- Discovered
Skill - One skill found on disk, ready to persist.
Functions§
- discover
- Walk a pack checkout and return every canonical skill.
- parse_
skill_ md - Parse one SKILL.md into a
Skill.