loom-registrylisted

# Loom Registry Use the `loom` CLI as the control plane for a local, Git-backed Agent Skill registry. Keep the registry root explicit, consume its JSON envelope, and preserve Loom's planning and approval boundaries. ## Route The Request Use this Skill when the user is working with any of these local Loom concepts: - a Skill registry or `loom` CLI command; - Skill sources, lifecycle, lint, eval, release anchors, diff, or rollback; - agent targets, workspace bindings, projections, activation, or visibility; - registry sync, operation backlog, history, replay, health, or diagnostics. Do not use this Skill for Loom.com videos, screen recording, video links, sharing, editing, captions, transcripts, or viewer analytics. If the request says only “Loom” and the context is video, route it to the Loom.com capability instead. Do not create or advertise a `loom` Skill alias. ## Establish The Registry Boundary 1. Run a read-only JSON command and require a valid `cli_contract_version` in the range declared by `loom.skill.toml` (`>=1.0.0,<2.0.0`). If the field is missing, invalid, or outside that range, stop all mutations; use only `loom --version`/`--help` for diagnosis and install the matching Loom release and shipped `loom-registry` Skill together. Check `loom <command> --help` for the command surface needed by the request. Never guess flags. 2. Obtain the intended registry root from the user or existing project context. Use a path such as `$HOME/.loom-registry` only when it is th