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
SkillScore82Maintained
Automatic
◆Research pack
Last verified 8/20/2026
What it changes
Passed 17 of 21 test cases with the skill, and 3 of 21 without it.
Without skill14%
With skill82%
Checks it passed that the model alone missed
Declines to edit graphic files or redraw plots directly
Prohibits paraphrasing reviewer text into new source quotes
Refuses to perform LaTeX editing or PDF recompilation directly
and 23 more in the full report
15 fixed3 passed either way4 still failing0 broke
Pass-rate lift
+68 pp
Tokens
+149%
Agent turns
0%
Response time
-28%
Model gemini-3.6-flashMeasured 8/20/2026v118 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 15
Prompt
We categorized a critical experimental flaw in stage 13. Which command should we run immediately to automatically update the workflow passport file before presenting choices to the author?
What was checked, without and with the skill
Checked
Without skill
With skill
Requires presenting evidence and choices to the user before running the back-edge command
Missed
Passed
Prohibits running passport add-back-edge prior to user selection
Missed
Passed
case-12 · 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.md289 lines16 filesincludes scripts
Review and rebuttal
Build a source-preserving review registry, issue matrix, revision plan,
evidence/change map, response draft, commitment ledger, unknown/failure record,
and delivery package. Treat prose generation as the last layer, not the first.
Read review-rebuttal-resource-map.md before
a real run. Read
references/workflow_contract.md before
creating or consuming canonical JSON. Read references.md
when selecting review/rule sources. The competitor evidence is
../../docs/competitors/review-rebuttal.md.
Non-negotiable boundaries
Consume venue-matching's selected handoff and review context. Verify selected
identity, selected_at timezone, selection_basis, user/delegated
authorization, chosen candidate ID, fit/risk row, unmodified rule envelopes,
source evidence path/as-of/source IDs, manuscript profile, and PDF
path/hash/pages/page size/profile/compliance. Never switch venue, reorder
tiers, or turn venue UNKNOWN into a fact.
Keep reviewer, editor, decision, and meta-review text verbatim in the
canonical registry. Atom labels, root causes, strategies, and generated
prose are interpretation layers; they never replace source text.
Record fetch time, source URL/type, round, reviewer ID, attachments and
AVAILABLE|UNKNOWN|UNAVAILABLE|STALE. A 401/403/429/5xx, timeout, login,
private invitation or network failure is UNAVAILABLE, not “no review.”
Never invent an experiment, analysis, citation, change, line number,
reviewer identity, venue rule or result. PLANNED and IN_PROGRESS may not
be phrased as completed. DONE requires a real change locator; completed
experiment/analysis additionally requires verifiable run provenance with a
matching SHA-256, not merely a local path.
Before marking a response package ready, run the atom/action contract gate so
source spans, reconstruction hashes, policy/ethics authorization and
perspective-specific self-review are machine-checked rather than trusted.
Paper-writing owns manuscript claims and edits. Result-analysis owns
evidence strength. Citation owns new-reference identity and claim support.
Figure owns visual honesty. Typesetting owns PDF rebuild/compliance. This
skill records and routes work; it does not impersonate those producers.
Stage 13 critical is narrow: only a routable root cause
Build evidence-bound journal or conference shortlists for Light stage 12. Use after typesetting delivers venue-handoff.json/PDF/compliance facts; when an author asks where to submit, journal selection, conference fit, scope or article-type matching, publication strategy, reach/match/safety tiers, transfer order, APC/OA/indexing/deadline constraints, or predatory/hijacked-journal risk. Produces a current-source candidate registry, fit/risk/unknown reports, and an unchosen decision packet; never r