Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when drafting or revising CSCW prose — group-level framing, concepts a field can reuse, participant voice handled with care, theory that earns its keep, and length discipline under the 5,000-12,000-word scrutiny band where contribution is weighed against every page.
.claude/skills/brycewang-stanford-cscw-writing-style/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 1% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 22% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 28% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 27% | 0% |
| case-12 | ✗→✓ | ▲ Improved | 23% | 0% |
A CSCW paper is judged by readers from several intellectual traditions at once — ethnographers, statisticians, system builders, social theorists — inside a journal process where the same reviewers may read the paper twice. The prose must therefore do two unusual things: make each tradition's part legible to the others, and hold up under a second, more skeptical read during Revise and Resubmit.
CSCW imposes no formal page limit. The 2026-cycle CFP instead put weight on a band: papers under roughly 5,000 words or over roughly 12,000 words attract extra scrutiny, and a paper whose length is incommensurate with its contribution can be desk rejected. Treat length as a claim you are making: every additional section asserts that the contribution needs it. Practical calibration:
sentence. If you cannot, cut until you can.
than it signals depth; move protocol detail to appendices.
workshop paper wearing a journal costume.
The single most common style failure at this venue is drift back to the individual user. Audit every claim sentence:
| Drifted (individual) | Anchored (collective) | | --- | --- | | "Users struggled to trust the bot's suggestions" | "Teams routed the bot's suggestions through a senior member before acting on them" | | "Participants felt burnout" | "The moderation team rotated exposure to harmful content to distribute burnout" | | "People adopted the feature" | "The community renegotiated its norms around what the feature made visible" | | "The tool improved efficiency" | "The tool redistributed articulation work from editors to contributors" |
If a finding cannot be written in the right-hand register, either the analysis stopped too early or the paper belongs at a different venue (cscw-topic-selection).
full of load-bearing vocabulary (awareness, articulation work, place vs. space). A new concept must be defined against — not merely alongside — the existing terms.
change either the analysis or the design discussion. A framework cited in the introduction and never touched again reads as ornament and will be flagged.
analytic weight the surrounding prose then does; a quote that merely restates the preceding sentence is filler. For sensitive communities, paraphrase or lightly alter quotes when verbatim text is reverse-searchable, and say that you did so.
the authors belong to or hold power over, a sentence about the researchers' relationship to the setting is analytic information, not confession.
Because R&R returns to the same reviewers, overclaiming is a double cost: it draws the objection in round one and the check in round two. Write claims that a hostile re-reader can verify against your own data sections:
moderators of crisis-support forums."
different verbs ("reported," "exhibited," "we read this as").
text[Protagonist] Is a group/community/organization the subject of the first claim sentence? yes / no [Stake] Does ¶2 say what breaks if the field keeps misunderstanding this — or just that "little is known"? [Concept] Is there one named, reusable idea? Can a reviewer paraphrase it in a sentence? [Methods+ethics] Are counts, settings, consent posture, and data-sensitivity handling visible by end of the introduction? [Length claim] Word count: <n>. One-sentence defense if outside 5,000-12,000.
Run the audit again on the revised manuscript before any R&R resubmission — the introduction is where reviewers first test whether the revision was real.
The word-band and template facts reflect the 2026-cycle CFP checked 2026-07-08; confirm they carry into the rolling model before citing them to a co-author.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→pass | 22,021 | 13,502 | -39% | 1 | 1 | 0% | 2,522 | 2,537 | +1% | 0 | 0 | — |
case-02 | fail→fail | 15,112 | 17,243 | +14% | 1 | 1 | 0% | 1,611 | 2,892 | +80% | 0 | 0 | — |
case-03 | fail→fail | 16,363 | 12,191 | -25% | 1 | 1 | 0% | 1,723 | 2,240 | +30% | 0 | 0 | — |
case-04 | fail→pass | 15,210 | 6,503 | -57% | 1 | 1 | 0% | 1,829 | 2,230 | +22% | 0 | 0 | — |
case-05 | fail→fail | 20,956 | 16,458 | -21% | 1 | 1 | 0% | 2,354 | 2,945 | +25% | 0 | 0 | — |
case-06 | fail→fail | 19,526 | 15,897 | -19% | 1 | 1 | 0% | 2,159 | 2,836 | +31% | 0 | 0 | — |
case-07 | pass→pass | 18,086 | 16,810 | -7% | 1 | 1 | 0% | 2,146 | 2,868 | +34% | 0 | 0 | — |
case-08 | pass→pass | 14,418 | 16,944 | +18% | 1 | 1 | 0% | 2,109 | 2,977 | +41% | 0 | 0 | — |
case-09 | fail→pass | 21,546 | 17,727 | -18% | 1 | 1 | 0% | 2,319 | 2,973 | +28% | 0 | 0 | — |
case-10 | fail→fail | 16,297 | 9,757 | -40% | 1 | 1 | 0% | 1,877 | 2,632 | +40% | 0 | 0 | — |
case-11 | fail→pass | 17,554 | 14,433 | -18% | 1 | 1 | 0% | 2,006 | 2,553 | +27% | 0 | 0 | — |
case-12 | fail→pass | 15,824 | 7,395 | -53% | 1 | 1 | 0% | 1,800 | 2,210 | +23% | 0 | 0 | — |
case-13 | fail→pass | 16,562 | 12,896 | -22% | 1 | 1 | 0% | 1,753 | 2,272 | +30% | 0 | 0 | — |
case-14 | fail→fail | 14,983 | 13,336 | -11% | 1 | 1 | 0% | 1,668 | 2,275 | +36% | 0 | 0 | — |
case-15 | fail→pass | 21,116 | 16,842 | -20% | 1 | 1 | 0% | 2,456 | 2,802 | +14% | 0 | 0 | — |
case-16 | pass→pass | 18,467 | 16,815 | -9% | 1 | 1 | 0% | 1,907 | 2,776 | +46% | 0 | 0 | — |
case-17 | pass→pass | 15,791 | 21,634 | +37% | 1 | 1 | 0% | 1,736 | 2,588 | +49% | 0 | 0 | — |
case-18 | pass→pass | 13,790 | 12,093 | -12% | 1 | 1 | 0% | 1,375 | 1,931 | +40% | 0 | 0 | — |
case-19 | pass→pass | 17,597 | 13,459 | -24% | 1 | 1 | 0% | 1,849 | 2,174 | +18% | 0 | 0 | — |
case-20 | pass→pass | 19,627 | 23,454 | +19% | 1 | 1 | 0% | 2,363 | 3,966 | +68% | 0 | 0 | — |
case-21 | pass→pass | 20,907 | 16,671 | -20% | 1 | 1 | 0% | 2,895 | 3,988 | +38% | 0 | 0 | — |
case-22 | pass→pass | 17,081 | 18,453 | +8% | 1 | 1 | 0% | 2,647 | 3,417 | +29% | 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 +32 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.