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/grilling

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

agent/skills/grilling/SKILL.md

@@ -1,30 +0,0 @@
----
-name: grilling
-description: Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
----
-
-Interview the user relentlessly until you reach a shared understanding. Map this as a **design tree**: every decision branches into the decisions that hang off it.
-
-Work the tree in **rounds**. The **frontier** is every decision whose prerequisites are already settled: the questions you can ask _now_ without guessing at answers you haven't heard yet. Ask the whole frontier in one round: number each question and give your recommended answer. Then wait for the user's answers before the next round.
-
-Format a round like so:
-
-```
-❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
-
-➡️ <your recommended answer>
-
----
-
-❓ **Q2** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
-
-➡️ <your recommended answer>
-```
-
-Word each question so "yes" accepts your recommended answer.
-
-Each round the user answers reshapes the tree: settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a _later_ round, not this one.
-
-Finding _facts_ is your job, never the user's. When a frontier question needs a fact from the environment (filesystem, tools, etc.), dispatch a sub-agent to find it; don't ask the user for anything you could look up yourself. Don't block on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait for the sub-agent to report; ask the rest of the frontier now. The _decisions_ are the user's: put each to them and wait.
-
-The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Do not act on it until the user confirms you have reached a shared understanding.

agent/skills/grilling/agents/openai.yaml

@@ -1,3 +0,0 @@
-interface:
-  display_name: "Grilling"
-  short_description: "Stress-test thinking a round of questions at a time"