chore(skills): wire agent/skills to the skills CLI global store

Retroactive provenance registration: the 10 pi-era skill snapshots are
byte-identical to upstream (38 skills mattpocock/skills + find-skills
vercel-labs/skills), now canonically installed at ~/.agents/skills with
store lockfile ~/.agents/.skill-lock.json (39 entries, folder hashes).

omp is not a skills-CLI agent id, so the omp tier becomes manual wiring:
replace the 10 tracked skill directories with symlinks into the store
and link the remaining 29 upstream skills the same way (39 links). The
repo now records the enabled set, never content; skills update -g
propagates through the links. managed-skills tier untouched.

Docs: skill-store-wiring.md (+index). Snapshot of the old real dirs at
/tmp/agent-skills-snap-20261018 for the transition window.

agent/skills/implement

@@ -0,0 +1 @@
+/home/blank/.agents/skills/implement

agent/skills/implement/SKILL.md

@@ -1,17 +0,0 @@
----
-name: implement
-description: "Implement a piece of work based on a spec or set of tickets."
-disable-model-invocation: true
----
-
-Implement the work described by the user in the spec or tickets.
-
-If the user passes a ticket reference, fetch it from the issue tracker and state its title before starting. If the reference is ambiguous, ask.
-
-Call the Skill tool with "tdd" where possible, at pre-agreed seams.
-
-Run typechecking regularly, single test files regularly, and the full test suite once at the end.
-
-Once done, call the Skill tool with "code-review" to review the work.
-
-Commit your work to the current branch.

agent/skills/implement/agents/openai.yaml

@@ -1,5 +0,0 @@
-interface:
-  display_name: "Implement"
-  short_description: "Build work from a spec or tickets"
-policy:
-  allow_implicit_invocation: false