Fixes an unquoted `#` in `board-ops`'s description. YAML reads ` #28` onward as a comment, so the parser — and Claude Code, which parses the same way — only ever saw the description up to `Covers board`. Both board numbers and the option-deletion hazard were absent from the listing that decides whether the skill fires, and every check stayed green because they look for an *empty* description and a truncated one is still non-empty. Quoting restores all 271 characters, which is the whole of the 3,144 vs 3,234 discrepancy the review flagged. `parseSkill` now compares the raw scalar against what YAML kept and errors on any loss, so the next one fails the gate rather than shipping. Tests cover the truncated case and a legitimately quoted `#`. Re-aims the `project-structure` Node-backend case, which `AGENTS.md` answers via its tree and which had oscillated 80 -> 100% across runs — the partial-overlap signature this PR documents. The replacement names no internals and probed 4/4. Makes the documented probe reproduce the harness: the same `--disallowedTools` flags as `runPrompt` rather than `--allowedTools`, `printf` instead of zsh's `print -r`, and `jq` over `tool_use` blocks instead of a `grep` that also matched MCP server names in the init event. The first-tool-call table is relabelled as an unrestricted probe, since the eval cannot reach for Bash at all. RUNS=5 skills:eval: 63/63, 62 at 100%; restoring those 90 characters displaced nothing. Signed-off-by: cliffhall <cliff@futurescale.com>
30 lines
876 B
JSON
30 lines
876 B
JSON
[
|
|
{
|
|
"prompt": "What lives in clients/web versus @inspector/core?",
|
|
"expect": "project-structure"
|
|
},
|
|
{
|
|
"prompt": "I am adding a module that both the browser side and the Node side need to run. How do I decide where it goes in this repo?",
|
|
"expect": "project-structure"
|
|
},
|
|
{
|
|
"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"
|
|
},
|
|
{
|
|
"prompt": "Convert this array of strings to uppercase.",
|
|
"expect": null
|
|
},
|
|
{
|
|
"prompt": "What is the capital of France?",
|
|
"expect": null
|
|
}
|
|
]
|