Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when a CSCW paper draws Revise and Resubmit or Revise for External Review — triaging reviewer requests, running the weeks-long revision as a project, and writing the point-by-point response letter that the same reviewers will read before they reread anything else.
.claude/skills/brycewang-stanford-cscw-author-response/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | 8% | 0% |
| case-01 | ✗→✓ | ▲ Improved | 4% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 7% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 53% | 0% |
| case-15 | ✗→✓ | ▲ Improved | 3% | 0% |
There is no rebuttal box at CSCW. The venue's response instrument is the revision plus response letter of a journal: you get weeks or months, you may change anything in the manuscript, and the people reading the result are the reviewers who wrote the critiques. That combination — real time, real changes, remembered context — makes the response letter the highest-leverage document of the whole pipeline.
Extract every distinct request from every review into a ledger, then classify:
| Class | Definition | Response posture | | --- | --- | --- | | Do | Legitimate, feasible in the window | Do it fully; show where | | Do differently | Legitimate concern, wrong prescription | Fix the underlying concern; explain the substitution explicitly | | Decline | Would harm the paper or exceed the study's license | Decline once, with reasons — never silently | | Cannot | Requires data/access that no longer exists | Say so plainly; offer the honest partial (new limitation text, added analysis of existing data) |
Two CSCW-specific triage realities:
interpretive study for reliability statistics; a qualitative reviewer may ask a trace study for member voice. Handle these as "do differently": meet the underlying worry (analytic credibility; human grounding) within your tradition's own rigor, and teach the standard you are meeting in one respectful sentence.
deployment wave may be impossible mid-revision. Decide in week one whether to collect, substitute, or descope a claim — this decision gates everything else.
decision letter (confirm the date; under rolling it is set per paper).
a letter written before the changes stabilize will misdescribe them.
before/after references, and reviewers may check.
Structure that survives a skeptical same-reviewer read:
textDear Editor and Reviewers, Summary of changes (½ page max): the 3-5 revisions that changed the paper's substance, plainly stated. Per-reviewer, per-point: R1.1 [quote or faithfully paraphrase the request] Response: what we did / why we did something else / why we declined. Location: §4.2, ¶3; Appendix C, Table 7. R1.2 ... R2.1 ... Changes not requested by any reviewer: list them — silent edits discovered later cost trust.
Letter discipline:
re-argued contributions signals evasion to someone who has read it all before.
unverifiable; "§4.2 now reports the attrition counts (new Table 3)" is.
this letter's tone in their ear.
the letter, no identifying artifacts in newly added materials.
framing overclaimed; we have rescoped the claim to the six communities studied" converts a weakness into demonstrated judgment.
The internal-round variant is smaller but the same shape: a short letter, the specific repairs, done fast. Its purpose is to make the paper worth reviewers' time — fix exactly what the screeners flagged and resist the urge to renovate.
text[Ledger] every request answered exactly once (no orphans, no repeats)? y/n [Locations] every claimed change verified at its cited section/page? y/n [Diff] unrequested changes listed? y/n [Tone] letter read aloud by a co-author not involved in drafting it? y/n [Anonymity] new text, tables, and supplements swept? y/n [Deadline] resubmission date and format confirmed against the decision letter? y/n
In the last verified cycle roughly four of five R&R papers that resubmitted were accepted (152 of 196; checked 2026-07-08) — the loop rewards teams that treat it as the venue's main event rather than an appeal.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-04 | fail→pass | 24,570 | 12,662 | -48% | 1 | 1 | 0% | 2,853 | 3,079 | +8% | 0 | 0 | — |
case-01 | fail→pass | 28,554 | 22,201 | -22% | 1 | 1 | 0% | 4,246 | 4,400 | +4% | 0 | 0 | — |
case-02 | pass→pass | 26,998 | 25,471 | -6% | 1 | 1 | 0% | 3,720 | 3,807 | +2% | 0 | 0 | — |
case-03 | fail→fail | 24,767 | 30,602 | +24% | 1 | 1 | 0% | 2,880 | 5,260 | +83% | 0 | 0 | — |
case-05 | fail→fail | 18,881 | 11,745 | -38% | 1 | 1 | 0% | 2,338 | 2,890 | +24% | 0 | 0 | — |
case-06 | pass→pass | 17,504 | 12,986 | -26% | 1 | 1 | 0% | 2,160 | 2,167 | +0% | 0 | 0 | — |
case-07 | fail→pass | 20,704 | 14,276 | -31% | 1 | 1 | 0% | 2,412 | 2,571 | +7% | 0 | 0 | — |
case-08 | fail→pass | 16,933 | 15,786 | -7% | 1 | 1 | 0% | 1,711 | 2,614 | +53% | 0 | 0 | — |
case-09 | pass→pass | 16,872 | 20,017 | +19% | 1 | 1 | 0% | 1,930 | 2,953 | +53% | 0 | 0 | — |
case-10 | pass→pass | 19,730 | 14,288 | -28% | 1 | 1 | 0% | 2,081 | 3,114 | +50% | 0 | 0 | — |
case-11 | pass→pass | 22,231 | 17,483 | -21% | 1 | 1 | 0% | 2,376 | 3,056 | +29% | 0 | 0 | — |
case-12 | pass→pass | 15,761 | 14,253 | -10% | 1 | 1 | 0% | 1,753 | 2,196 | +25% | 0 | 0 | — |
case-13 | pass→pass | 20,662 | 20,295 | -2% | 1 | 1 | 0% | 2,416 | 3,463 | +43% | 0 | 0 | — |
case-14 | pass→pass | 14,286 | 16,296 | +14% | 1 | 1 | 0% | 2,357 | 2,759 | +17% | 0 | 0 | — |
case-15 | fail→pass | 22,138 | 9,424 | -57% | 1 | 1 | 0% | 2,573 | 2,640 | +3% | 0 | 0 | — |
case-16 | fail→fail | 25,364 | 29,615 | +17% | 1 | 1 | 0% | 3,339 | 5,292 | +58% | 0 | 0 | — |
case-17 | fail→fail | 24,781 | 22,462 | -9% | 1 | 1 | 0% | 2,821 | 4,002 | +42% | 0 | 0 | — |
case-18 | fail→pass | 20,762 | 16,358 | -21% | 1 | 1 | 0% | 2,424 | 3,303 | +36% | 0 | 0 | — |
case-19 | pass→pass | 28,012 | 18,792 | -33% | 1 | 1 | 0% | 2,862 | 3,924 | +37% | 0 | 0 | — |
case-20 | pass→pass | 21,803 | 18,364 | -16% | 1 | 1 | 0% | 2,795 | 3,986 | +43% | 0 | 0 | — |
case-21 | fail→fail | 16,304 | 25,425 | +56% | 1 | 1 | 0% | 2,530 | 3,760 | +49% | 0 | 0 | — |
case-22 | fail→fail | 22,386 | 28,364 | +27% | 1 | 1 | 0% | 2,983 | 4,486 | +50% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +27 percentage points is the difference between those two pass rates over the 22 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.