lythoskill-deck

# lythoskill-deck: Declarative Skill Deck Governance > What matters is not how many skills you have, but which ones the agent sees at the same time. ## Core Model `skill-deck.toml` declares desired state. `deck link` makes the working set (default `.claude/skills/`) match — creates symlinks for declared skills, removes everything else. Deny-by-default: undeclared skills do not exist in the agent's view. ``` Cold Pool (~/.agents/skill-repos/) → deck add → skill-deck.toml → deck link → .claude/skills/ (all downloaded skills) (declare) (desired state) (reconcile) (working set — what agent sees) ``` ## Multi-File Phase Decks (BEST PRACTICE) When a task spans different skill sets, use **separate deck files per phase** instead of editing a single toml: ```bash # Phase 1 — brand design deck link --deck phase1-brand.toml --cold-pool ~/.agents/skill-repos # Phase 2 — content creation (atomic switch, Phase 1 skills gone) deck link --deck phase2-content.toml --cold-pool ~/.agents/skill-repos # Done — restore parent deck deck link --deck ./skill-deck.toml ``` Each phase deck is independently auditable. Never add/remove entries in-place when switching contexts — a wrong edit silently breaks the previous phase's composition. The reconciler handles the transition: old symlinks removed, new ones created, no state leaks. ## Seed Bootstrap Start with a minimal deck (only lythoskill-deck as innate). The agent reads deck SKILL.md → learns schema → ...