skill-pipeline-synclisted

# Skill Pipeline Sync > Turns the vault (source of truth) into executable skills, safely and idempotently. ## Purpose The vault is authoritative; `~/.claude/skills` is generated. This skill runs the compiler so edits to a spec become a live skill without hand-editing the runtime. ## When to use - Right after creating or editing any skill under `agent-os/Skills/`. - When `~/.claude/skills` looks stale or out of sync with the vault. ## When NOT to use - To *author* a new skill from raw material — that's ``skill-builder``. Run this *after* the spec exists. ## Inputs - Skill specs: `agent-os/Skills/<Category>/<id>/SKILL.md` with valid frontmatter. ## Outputs - `~/.claude/skills/<slug>/` (SKILL.md + metadata.json + assets) - `agent-os/Skills/validation-report.md` - `agent-os/Skill Relationships.md` - `~/.claude/skills/GLOSSARY.md` — human-facing catalogue of every runtime skill - `~/.claude/skills/.vault-root` — the vault's absolute path, so a compiled skill can find its own **source** (see below) ## Source resolution (`.vault-root`) The runtime is generated and is **not a git repo**, so a script inside a compiled skill can't answer "where do I edit this?" or "has my source been committed?" on its own. `compile` stamps the missing half: ``` sourceDir = join(read("~/.claude/skills/.vault-root"), "agent-os", metadata.source) ``` `metadata.json` already carries the vault-**relative** `source` (e.g. `Skills/Coding/site-harvest`); `.vault-root` supplies the root. Idempoten