docs: tune skill eval cases and document how to write them

`skills:eval` was at 38/46 with several skills measuring 0-33%. The low
scores were mostly bad eval cases rather than bad descriptions, for two
reasons that were nowhere written down:

- The harness runs each case with `--max-turns 1`, so the skill has to be
  the model's FIRST tool call. A prompt asking "how does X work here", or
  naming a concrete file, sends the model to Read/Grep first — a better
  answer to the question, scored as a miss. Every 0% case was one of these.
- `AGENTS.md` is resident on every turn, so a prompt it already answers is
  answered without any skill and the case can never pass.

Replace the cases that measured the wrong thing, expand every model-invoked
skill from 3 to 5 positives (negatives kept) so one flake cannot cross the
threshold, and reshape `local-dev`'s description to the action-first form.

Add `docs/skill-authoring.md` with the case shapes that fire, the ones that
cannot, and the probe-then-measure loop.

RUNS=5 npm run skills:eval: 63/63 at or above threshold, 60 at 100%,
all 18 negatives clean.

Closes #2202

Signed-off-by: cliffhall <cliff@futurescale.com>

.claude/skills/board-ops/evals/evals.json

@@ -11,6 +11,14 @@
     "prompt": "The project board rejected my Status option ID. How do I get the current ones?",
     "expect": "board-ops"
   },
+  {
+    "prompt": "I'm about to edit the options on one of the board's single-select fields. Should I do anything first?",
+    "expect": "board-ops"
+  },
+  {
+    "prompt": "Several cards lost their Priority value after the field was edited. How do I put it back?",
+    "expect": "board-ops"
+  },
   {
     "prompt": "Explain the difference between TCP and UDP.",
     "expect": null

.claude/skills/issue-create/evals/evals.json

@@ -11,6 +11,14 @@
     "prompt": "Before I file this, how do I check nobody has reported it already?",
     "expect": "issue-create"
   },
+  {
+    "prompt": "I found a bug while working on something else. How do I get it tracked in this repo?",
+    "expect": "issue-create"
+  },
+  {
+    "prompt": "What do I need to do beyond `gh issue create` for a new issue to be properly tracked here?",
+    "expect": "issue-create"
+  },
   {
     "prompt": "What is the chemical symbol for potassium?",
     "expect": null

.claude/skills/issue-triage/evals/evals.json

@@ -4,13 +4,21 @@
     "expect": "issue-triage"
   },
   {
-    "prompt": "What Priority should issue 2189 be given?",
+    "prompt": "How do I decide what Priority an incoming issue deserves?",
     "expect": "issue-triage"
   },
   {
     "prompt": "Audit the project board for anything that has drifted.",
     "expect": "issue-triage"
   },
+  {
+    "prompt": "How do I find the issues that aren't on either board yet?",
+    "expect": "issue-triage"
+  },
+  {
+    "prompt": "After scoring an issue against the rubric, what do I do with the score?",
+    "expect": "issue-triage"
+  },
   {
     "prompt": "Who wrote the novel Moby-Dick?",
     "expect": null

.claude/skills/local-dev/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: local-dev
-description: Getting the Inspector running locally, and the reasoning behind its dependency rules. Which install to run and which script starts each client (web, cli, tui, launcher); why v2 is not an npm workspace; how the @inspector/core alias works; and why the placement rules in AGENTS.md are what they are — what each one is defending against, what it looked like when it was violated, and how to tell you have hit one.
+description: Install, build and run the Inspector locally, and place a dependency correctly. Use when starting the web, cli, tui or launcher client; when asking whether a build or rebuild is needed before a run script works; when an install, an @inspector/core import or a client bundle fails at run time; when adding or bumping a dependency and choosing which package.json declares it; or when a bundler external, a version skew or a git worktree is the suspect.
 disable-model-invocation: false
 ---
 

.claude/skills/local-dev/evals/evals.json

@@ -15,6 +15,10 @@
     "prompt": "How do I run the CLI from the built launcher in this repo instead of via npx?",
     "expect": "local-dev"
   },
+  {
+    "prompt": "I just pulled and a client's dependencies look out of sync. What do I need to run?",
+    "expect": "local-dev"
+  },
   {
     "prompt": "Write a haiku about autumn.",
     "expect": null

.claude/skills/pr-flow/evals/evals.json

@@ -11,6 +11,14 @@
     "prompt": "The DCO check is red on my branch. How do I fix the commits I already pushed?",
     "expect": "pr-flow"
   },
+  {
+    "prompt": "Copilot left a pile of review comments on my PR. How do I answer them so nothing gets lost?",
+    "expect": "pr-flow"
+  },
+  {
+    "prompt": "My PR is open and green. Walk me through getting it merged and closed out here.",
+    "expect": "pr-flow"
+  },
   {
     "prompt": "What does this regex match? /^[a-z]+$/",
     "expect": null

.claude/skills/pre-push-gate/evals/evals.json

@@ -4,13 +4,21 @@
     "expect": "pre-push-gate"
   },
   {
-    "prompt": "The Storybook stage of the gate fails in my worktree even though the tests pass. What is wrong?",
+    "prompt": "The gate's Storybook stage is failing for me. How do I diagnose it?",
     "expect": "pre-push-gate"
   },
   {
     "prompt": "Everything in the gate started timing out at once. What causes that?",
     "expect": "pre-push-gate"
   },
+  {
+    "prompt": "How do I check whether a stage of the gate really passed?",
+    "expect": "pre-push-gate"
+  },
+  {
+    "prompt": "The gate failed at the lint stage. How do I work out what is wrong?",
+    "expect": "pre-push-gate"
+  },
   {
     "prompt": "What is 17 multiplied by 23?",
     "expect": null

.claude/skills/project-structure/evals/evals.json

@@ -4,11 +4,19 @@
     "expect": "project-structure"
   },
   {
-    "prompt": "I'm adding a helper both the CLI and the web client need. Which directory does it belong in?",
+    "prompt": "Does a new Node-only backend piece for the web client belong in core or in the web client itself?",
     "expect": "project-structure"
   },
   {
-    "prompt": "Which package owns the OAuth secret storage backends?",
+    "prompt": "Does browser-only transport code belong in core or in the web client?",
+    "expect": "project-structure"
+  },
+  {
+    "prompt": "I have a new file and I'm not sure where it goes. How do I decide in this repo?",
+    "expect": "project-structure"
+  },
+  {
+    "prompt": "Does a helper that only the CLI and TUI use belong in core or in one of the clients?",
     "expect": "project-structure"
   },
   {

.claude/skills/test-servers/evals/evals.json

@@ -11,6 +11,14 @@
     "prompt": "I renamed a file under test-servers/src and the fixture is still running the old code. Why?",
     "expect": "test-servers"
   },
+  {
+    "prompt": "Which protocol era should I connect with when I run one of these fixtures by hand?",
+    "expect": "test-servers"
+  },
+  {
+    "prompt": "I need a fixture combination that doesn't exist yet. How do I add one?",
+    "expect": "test-servers"
+  },
   {
     "prompt": "Sort this list alphabetically: banana, apple, cherry.",
     "expect": null

.claude/skills/testing/evals/evals.json

@@ -1,16 +1,24 @@
 [
-  {
-    "prompt": "I just added clients/tui/__tests__/serverList.test.ts. What command runs only the TUI suite?",
-    "expect": "testing"
-  },
-  {
-    "prompt": "In clients/web/src/components/Foo.test.tsx I need to assert on a Mantine transition mid-flight. How?",
-    "expect": "testing"
-  },
   {
     "prompt": "Which test tier in this repo spawns the built binary rather than importing it?",
     "expect": "testing"
   },
+  {
+    "prompt": "How do I run just the TUI suite, and is there one command that runs everything?",
+    "expect": "testing"
+  },
+  {
+    "prompt": "How do I write a test for a TUI component in this repo?",
+    "expect": "testing"
+  },
+  {
+    "prompt": "How am I supposed to invoke the CLI from a new test in this repo?",
+    "expect": "testing"
+  },
+  {
+    "prompt": "How do I run the web integration tests, and do they run as part of the normal test command?",
+    "expect": "testing"
+  },
   {
     "prompt": "What does this regex do? /^\\d{3}-\\d{4}$/",
     "expect": null