Model gemini-3.6-flashMeasured 8/20/2026v118 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
We need to run an ad-hoc local environment sanity check specifically for Python and R toolchains before running an intake scan. What command performs this standalone environment check?
What was checked, without and with the skill
Checked
Without skill
With skill
Executes python scripts/structure_governance_gate.py --doctor python r.
Missed
Passed
case-11 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md257 lines7 filesincludes scripts
Project structure lifecycle
Own the visible project tree and its migration evidence. Do not mistake a
tidy directory for reproducible research.
Read
references/project-lifecycle-resource-map.md
before an existing-repository migration. It defines artifacts, policy, access
levels, provenance, and cross-skill ownership. Use
references/structure-profiles.json for
small profile minima and
templates/project-policy.template.json
for explicit project/file policy.
Use scripts/structure_governance_gate.py before delivery to validate profile
choice, existing-project read-only safety, template residuals, secret scan,
environment doctor, authorization binding, applied-manifest binding, and
rollback evidence.
Non-negotiable boundary
Treat inventory as read-only access, not authorization to move.
Never overwrite, delete, run git rm --cached, initialize DVC, rewrite
configuration, or move a symlink automatically.
Never use --force as consent. The lifecycle has no force bypass.
Preserve all .light/ content. memory-pm alone creates or edits passport,
project card, decision log, version history, terminology, and handoff files.
Keep absent facts UNKNOWN. A path such as data/raw does not prove size,
sensitivity, immutability, recomputability, or Git policy.
Do not turn this overlay into a DAG node. Emit no light.findings.v1; add no
STAGE_GATES, ROUTES, stage number, or back-edge.
State that structural conformance does not prove data quality, experiment
reproducibility, statistical validity, or paper quality.
Never ship a generated or migrated tree with unresolved template placeholders,
unhandled secret-scan hits, or missing required Python/R/environment checks.
Build auditable peer-review revision and author-response packages for Light stage 13. Use after receiving reviewer comments, a decision or meta-review; when drafting a rebuttal or response letter; when triaging major/minor revisions; when simulating a pre-submission review; or when a rejection may require a user-chosen 13→3 novelty, 13→5 experiment, or 13→8 writing back-edge. Consumes the selected venue/context and real PDF facts, preserves reviewer wording, atomizes issues, binds claims/evidenc