docs: address Copilot review round 3 on #2203
Replaces the last `project-structure` case that `AGENTS.md` answers — a helper used by the CLI and TUI belongs in `core/` per its own directory tree. This was also the only case below 100% in the previous suite, so the static reading and the score agreed. The replacement targets the skill's first stated purpose, locating code, which `AGENTS.md` gives no method for; it probed 3/3 and now measures 100%. Extends the truncation guard's tests to `when_to_use`. The guard loops over both fields but only `description` was pinned, so dropping the second from that list would have gone unnoticed. The new case pairs a quoted description with an unquoted `when_to_use` and asserts the description is not implicated. Scopes the negative-case requirement in the prose to model-invoked skills; round 2 scoped the checklist but left this sentence saying "every skill file". Refreshes the stale `~2.8k of 4k` listing figure. The other instance is past-tense about the three-to-nine experiment and stays, now said explicitly so two numbers do not look like a disagreement. Records the eval's real blind spot: all three cases review identified as `AGENTS.md`-answerable were scoring 80-100% when flagged, so a high score does not clear a case of overlap. The eval can show a case failing; it cannot show a passing case is well-aimed. RUNS=5 skills:eval: 63/63. local:gate passes, 34/34. Signed-off-by: cliffhall <cliff@futurescale.com>
This commit is contained in:
parent
880be3acdd
commit
104a05dd7f
1 changed files with 54 additions and 5 deletions
|
|
@ -187,7 +187,7 @@ that from happening:
|
|||
skill at all: it is absent from the listing and the Skill tool refuses it. The
|
||||
costs are asymmetric — a spurious load costs ~250 characters, a missed one
|
||||
costs a wrong base branch or an unsigned commit — and the budget is not tight
|
||||
(nine of the ten are model-invoked today and total ~2.8k of 4k). Reserve
|
||||
(nine of the ten are model-invoked today and total ~3.2k of 4k). Reserve
|
||||
`true` for a procedure that is genuinely only ever started deliberately —
|
||||
`release` is the only one left, because nobody cuts a release by implication.
|
||||
⚠️ **A `true` skill cannot be reached by another skill either.** If a
|
||||
|
|
@ -198,7 +198,8 @@ that from happening:
|
|||
of the ones already there: `project-structure` fell from 100% to 0% on two
|
||||
cases (n=4) and `testing` from 3/5 to 2/5, while the six new skills all
|
||||
measured 100% and every negative case stayed clean. So the ceiling is
|
||||
attention, not characters — we were at 2.8k of a 4k budget throughout. Adding
|
||||
attention, not characters — we were at 2.8k of a 4k budget throughout *that
|
||||
experiment* (it is ~3.2k now; the point is that nothing was near the cap). Adding
|
||||
a skill therefore has a cost paid by the *existing* ones, which only
|
||||
`skills:eval` can see. **Re-run the full eval after any flip _or description
|
||||
edit_**, not just the changed skill's own cases.
|
||||
|
|
|
|||
Loading…
Reference in a new issue