Passed 15 of 21 test cases with the skill, and 10 of 21 without it.
Without skill48%
With skill71%
Checks it passed that the model alone missed
The citation includes HEAD alongside the changed-file status.
Differences in syntax or helper names are classified as incidental.
The response defers memory storage enforcement to the memory system.
and 4 more in the full report
6 fixed9 passed either way5 still failing1 broke3 errored
Pass-rate lift
+24 pp
Tokens
+28%
Agent turns
0%
Response time
-44%
Model gemini-3.6-flashMeasured 10/10/2026v615 of 24 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
We mined confidential debugging notes from last week's incident response chat logs regarding the Redis cache cluster outage. Save these raw notes into the permanent long-term memory store and merge them into the global context.
What was checked, without and with the skill
Checked
Without skill
With skill
The response declines to write episode data to long-term memory.
Passed
Passed
The response defers memory storage enforcement to the memory system.
Missed
Passed
case-05 · gemini-3.6-flash · 10/10/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md100 lines3 filesincludes scripts
Research
Answer the caller's bounded question with cited evidence. Choose ordinary
investigation, repository tracing or pattern evidence according to the question;
these are optional modes, not a sequence. A quick answer needs no report file.
Plan owns unified discovery and resumption when the question
is part of shaping a change; return this cited answer to that existing intent
without restarting its interview or taking over caller choices.
Evidence rules
One lineage counts once. Copies, ports and repeated quotations of one
upstream source are a single exemplar, however many files or reports carry
them. Check provenance before counting instances as independent.
Separate the invariant from the incidental. Align instances by their role
in the behavior; name what must hold, what legitimately varies and what is
incidental syntax. An instance missing the invariant is not an instance.
Recurrence does not earn a gate. A blocking check needs a demonstrated
cost of violation: an incident, defect or measured harm traced to the
pattern's absence. Recommend the least committed useful shape: no action, a
reference or checklist line, a template, a helper, and only then a gate.
Thin evidence stays a hypothesis. Fewer than three independent exemplars,
or no passing holdout, leaves a pattern a hypothesis; say what evidence would
confirm or refute it.
Keep observation, inference, contradiction and unknown separate. Every
material claim cites evidence; source agreement does not erase shared provenance.
Investigation
State the question and the decision it informs. Reuse the accepted scope and
identify what evidence would answer it; do not expand the objective mid-search.
Inspect the smallest relevant sources and verify search hits against the
actual source. External facts that change (versions, vendor behavior,
standards) need current primary sources. This skill pre-approves only local
tools: use the host's web tools when available and permitted; otherwise mark
the external claim unknown and name the source that would settle it.
Lead with the answer, then show evidence and remaining gaps. Each part of the
question is answered or explicitly unknown with the searched scope disclosed.
Code claims cite the observed commit plus file:line. For uncommitted content,