--- type: reference title: omp Skill Store Wiring description: How omp's agent/skills directory is symlinked into the skills CLI global store, and where lockfile provenance lives. tags: - skills - symlinks - provisioning timestamp: 2026-10-18 verified: 2026-10-18 --- # omp Skill Store Wiring omp is NOT a registered agent in the `skills` CLI (79-agent registry checked in `dist/cli.mjs` 2026-10-18; see [Agent Support](/tools/vercel-labs-skills/agent-support.md)), so `skills add` never writes to `~/.omp/agent/skills/` on its own. The wiring is manual, retrofitted 2026-10-18: - **Canonical store:** `~/.agents/skills//` — real files, written by `npx skills add / --all -g` (universal agent, global scope). - **Provenance:** `~/.agents/.skill-lock.json` (store lockfile, version 3): per skill `source` (e.g. `mattpocock/skills`, `vercel-labs/skills`), `skillPath`, `skillFolderHash`, timestamps. 39 entries as of 2026-10-18: 38 from `mattpocock/skills`, `find-skills` from `vercel-labs/skills`. - **omp tier:** every entry in `agent/skills/` (this repo) is a **symlink** to `~/.agents/skills/` — 39 links. `manage_skill` writes real dirs into the separate tier `agent/managed-skills/`; that tier is untouched by this scheme. ## Consequences - `skills update -g` refreshes every skill for omp through the links; the repo records only the link set (which skills are enabled), never content. - A fresh workstation needs two steps: `npx skills add mattpocock/skills --all -g` (+ `find-skills` from `vercel-labs/skills`), then re-create the symlinks; `git pull` alone yields dangling links until the store exists. - `skills ls` from a repo whose layout contains `agent/skills` mislabels those links as Eve project skills (path collision with Eve's `agent/skills` dir); harmless attribution noise. ## Related * [Lock File](/tools/vercel-labs-skills/lock-file.md) — lockfile format and update checking * [Installation Scope](/tools/vercel-labs-skills/installation-scope.md) — symlink vs `--copy` methods