Agent skill · Documentation

webconf-writing-style

Use when drafting or revising a Web Conference (WWW) paper's prose — building the web-native framing that answers "why is this a WWW paper" on page one, writing for a mixed computing/social-science/economics readership, compressing into 8 self-contained pages, and handling scale numbers and platform names with precision.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-writing-style --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: The-Web-Conference-Skills/skills/webconf-writing-style/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Web Conference Writing Style A Web Conference paper is judged by readers who may sit in different disciplines within the same track panel, under a rule that the first 8 pages must carry the entire case. The house style that survives this: **lead with the web-native mechanism, quantify the scale early, and write constructs so an adjacent-field expert can check them.** ## The page-one obligation: web-nativeness The venue's most predictable review sentence is a version of "unclear why this is a WWW paper." Inoculate on page one by naming the property of the Web your contribution depends on, as a mechanism rather than a backdrop: | Weak (backdrop) | Strong (mechanism) | |---|---| | "We evaluate on web data" | "Anchor text distributes labels across sites, which our method exploits" | | "Recommendation is important online" | "Feedback loops between ranking and clicks bias naive estimators; we correct for the loop" | | "Misinformation spreads on platforms" | "Reposting graphs give exposure timestamps that identify the spread model" | | "We test at web scale" | "At 10^9 edges, quadratic attention is infeasible; our sketch keeps error < ε at linear cost" | If no such sentence can be writt

What's inside
Steps it walks through
  1. The page-one obligation: web-nativeness
  2. Register for a mixed panel
  3. An introduction shape that fits this venue
  4. Compression into 8 self-contained pages
  5. Sentence-level habits reviewers reward
  6. Titles and abstracts in this venue's register
  7. Self-edit gate before submission
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the webconf-writing-style skill do?

Use when drafting or revising a Web Conference (WWW) paper's prose — building the web-native framing that answers "why is this a WWW paper" on page one, writing for a mixed computing/social-science/economics readership, compressing into 8 self-contained pages, and handling scale numbers and platform names with precision.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-writing-style --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going