Files
command-center/omp-docs/skills/store-wiring.md
T
Frank 651924a4bc docs(skills): collapse three overlapping skills trees into one verified tree
Three parallel trees documented the same ecosystem: omp-docs/skills/
(two overview pages), tools/npx-skills/ (10 pi-era npm pages), and
tools/vercel-labs-skills/ (11 CLI pages), plus a fourth leaderboard page
at engineering/skills-ecosystem.md. Verbatim overlap (identical SKILL.md
field tables in skills-spec.md vs skill-format.md; 13-agent vs 68-agent
copies of the same upstream table). Consolidated to four concept pages:

- skills/agent-skills.md: standard, format, loading, authoring (merges
  skills-spec, skill-format, skill-file-structure, skill-loading,
  best-practices, skills-vs-extensions)
- skills/skills-cli.md: CLI reference (merges commands, source-formats,
  installation-scope, skill-discovery, lock-file, env-variables,
  agent-support, related-links)
- skills/store-wiring.md: moved, fleet ops, links retargeted
- skills/ecosystem.md: replaces skills-ecosystem.md; stale 2026-08-12
  top-50 table dropped, replaced with a live top-10 re-queried from the
  skills.sh API tonight and the API contract re-verified (zero-based,
  200/page, {skills,total,hasMore,page}, total 9909)

All facts re-verified 2026-10-19 against primary sources:
agentskills.io, vercel-labs/skills README + src/cli.ts (command set,
--full-depth) + src/skill-lock.ts (v3 lock, XDG path, wipe-on-old),
live skills.sh API. Deleted superseded core/index-doc.md (old pi-era
docs index). Retargeted all inbound links (tools/index, engineering x3,
packages x3, pi/skills, core/index). Pi-era npm skill packaging is
listed as archived under /pi/.

Refs #29
2026-10-19 02:58:52 -07:00

63 lines
2.4 KiB
Markdown

---
type: reference
title: omp Skill Store Wiring
description: Division of skill tiers on Dank workstations — skills CLI global store, omp agents provider, and the authored repo tier.
tags:
- skills
- provisioning
- dotfiles
timestamp: 2026-10-18
verified: 2026-10-18
---
# omp Skill Store Wiring
Three tiers, one owner each:
| Tier | Path | Owner | Content |
|---|---|---|---|
| Canonical store | `~/.agents/skills/` | `skills` CLI | upstream skills, 38 as of 2026-10-18 (all `mattpocock/skills`) |
| Provenance | `~/.agents/.skill-lock.json` | `skills` CLI | v3 lockfile: `source`, `skillPath`, `skillFolderHash` per skill |
| Authored | `agent/skills/` (this repo) | Frank, via PR | hand-customized overrides; today only `grilling` |
## How omp loads them
omp is NOT a registered agent in the `skills` CLI (79-agent registry checked
2026-10-18; see [Skills CLI](/skills/skills-cli.md)) —
`skills add` never writes anywhere under `~/.omp`. Instead omp's own `agents`
provider reads the store **directly**: `skills.enableAgentsUser` (default true)
loads `~/.agents/skills/*/SKILL.md`. No per-skill symlinks in the repo — the
repo does not mirror the store; it only holds authored overrides.
Precedence (omp `omp://skills.md`): authored `agent/skills/` (native, priority
100) beats the agents provider; identical copies collapse by realpath, differing
same-named copies survive namespaced (`agents/<name>`) with a startup warning.
Therefore: **when authoring an override, remove the skill from the store**
(`npx skills remove <name> -g`) so the lockfile stays truthful and no
namespaced twin haunts the listing. `grilling` was extracted this way 2026-10-18.
## Updating upstream skills
```bash
npx -y skills update -g # refreshes everything the lockfile tracks
npx skills check # drift report vs GitHub tree SHAs
```
Fresh workstation (omp side is two commands — store restore + authored tier
arrives with the repo clone):
```bash
npx -y skills add mattpocock/skills --all -g
npx -y skills add vercel-labs/skills --skill find-skills --agent universal -g
npx -y skills remove grilling -g # authored copy ships in the repo
```
## Managed tier
`agent/managed-skills/` (auto-learn, priority 5) is separate and untouched by
all of the above; authored skills always win name collisions against it.
## Related
* [Skills CLI](/skills/skills-cli.md) — lock file, update checking, and the full agent registry