6dd43e78ba
`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>
30 lines
822 B
JSON
30 lines
822 B
JSON
[
|
|
{
|
|
"prompt": "Move the board card for issue 2189 to In Review.",
|
|
"expect": "board-ops"
|
|
},
|
|
{
|
|
"prompt": "How do I set the Priority field on a card in the v2 project board?",
|
|
"expect": "board-ops"
|
|
},
|
|
{
|
|
"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
|
|
},
|
|
{
|
|
"prompt": "What year was the first Moon landing?",
|
|
"expect": null
|
|
}
|
|
]
|