New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Webconf Writing Style

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

A skill your agent uses 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…

MITAuto-check passedWriting & Content

Install Webconf Writing Style

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-writing-style -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-writing-style --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/The-Web-Conference-Skills/skills/webconf-writing-style .claude/skills/webconf-writing-style && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
webconf-writing-style
GitHub stars
1.2k
Token cost
~1.7k tokens
SKILL.md length
772 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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…

  • Works in 5 steps: One figure that earns its column:… → Prose-to-table conversions for related… → Push proof bodies and protocol detail to… → …
  • Revising a Web Conference (WWW) papers prose — building the web-native framing that answers why is this a WWW paper on page one
  • SKILL.md covers The page-one obligation:…, Register for a mixed panel, An introduction shape that… and Compression into 8…, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Webconf Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Brand voice and tone. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.

When your agent uses it

  • Revising a Web Conference (WWW) papers 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
  • Handling scale numbers and platform names with precision

Example prompts

  • “s prose — building the web-native framing that answers”
  • “/webconf-writing-style”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. One figure that earns its column: replace the architecture-boxes diagram nobody
  2. Prose-to-table conversions for related work contrasts and dataset statistics.
  3. Push proof bodies and protocol detail to the appendix, keeping statements and
  4. Kill roadmap paragraphs ("Section 2 discusses...") — sigconf headers already
  5. Cut the second and third examples of every point; web papers over-illustrate.

What it can do on your machine

Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Webconf Writing Style loads about 1.7k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 772 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 772 words, ~1,711 tokens.

Download SKILL.mdSave it as .claude/skills/webconf-writing-style/SKILL.md (or your agent's skills folder).
name
webconf-writing-style
description
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.

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 written truthfully, the problem is routing, not prose — go to webconf-topic-selection.

Register for a mixed panel

  • Define constructs at first use even when your subcommunity finds them obvious: "engagement (clicks per impression)," "polarization (as measured by ...)." Social-science co-reviewers check construct validity; systems co-reviewers check measurability. One parenthetical serves both.
  • Attach every adjective to a number or a mechanism. "Large-scale" means a stated node/edge/user/request count; "efficient" means a complexity bound or a measured cost; "real-world" means a named data source with a collection window.
  • Name platforms carefully. During double-blind review, an identifying platform ("our deployment at <company>") must be masked, but mask with properties, not vagueness: "a shopping platform with ~10^7 daily active users" preserves the evidential weight anonymously.
  • Ethics sentences are body text. One or two sentences on consent, ToS compliance, and aggregation level, in Section 3 where the data is introduced — not exiled to the appendix (see webconf-supplementary).

An introduction shape that fits this venue

text
¶1  The web mechanism and the problem it creates or enables   (why the Web)
¶2  Why existing approaches miss it — each named line of prior
    work gets a specific failure tied to the mechanism          (the gap)
¶3  The contribution, typed explicitly: algorithm / system /
    measurement / dataset / theory                              (what's new)
¶4  Evidence preview with scale attached: datasets, platforms,
    windows, headline deltas                                    (why believe)
¶5  Reusability: what transfers beyond this platform/corpus,
    plus artifact availability                                  (why care)

Contribution typing (¶3) matters more here than at single-community venues: a measurement paper judged as a methods paper fails, and vice versa. Say which one you wrote.

Compression into 8 self-contained pages

Reviewers may stop at page 8, so compression means re-homing, not shrinking fonts (acmart tampering is detectable and sanctioned):

  1. One figure that earns its column: replace the architecture-boxes diagram nobody quotes with the result figure reviewers screenshot.
  2. Prose-to-table conversions for related work contrasts and dataset statistics.
  3. Push proof bodies and protocol detail to the appendix, keeping statements and sketches in the body; the appendix is verification, not persuasion.
  4. Kill roadmap paragraphs ("Section 2 discusses...") — sigconf headers already navigate.
  5. Cut the second and third examples of every point; web papers over-illustrate.
Show full SKILL.md (308 more words)Show less

Sentence-level habits reviewers reward

  • Past tense for what you measured, present tense for what the method does, future tense almost never (rebuttal-bait).
  • Numbers with uncertainty where runs repeat: "34.2 ± 0.4" or "34.2 (95% CI 33.9-34.5)," and effect direction in words for the cross-disciplinary reader.
  • Limitations stated as scope, in the body's final section: "our identification holds for platforms exposing timestamps; feeds without them require..." — this venue reads honest scoping as strength, especially in Responsible-Web-adjacent tracks.

Titles and abstracts in this venue's register

Scan any recent WWW proceedings table of contents and two title patterns dominate: mechanism-first ("Correcting X-Bias in Y with Z") and question-first for measurement papers ("Is X a Y or a Z?" — the Kwak et al. Twitter title is the canonical instance). Patterns to avoid: bare system names with no claim ("WebFooNet"), stacked buzzwords ("Towards Trustworthy LLM-Empowered Graph-Enhanced..."), and titles promising more generality than the evidence holds — the title is the first overclaim reviewers can check. For abstracts, the compression test: a reader should recover mechanism, contribution type, scale of evidence, and one number from the abstract alone. If the abstract survives having every adjective deleted, it is ready; if deleting adjectives leaves nothing, it was decoration all the way down.

Self-edit gate before submission

  • Page 1 names the web-native mechanism in one sentence a chair could quote.
  • Contribution type declared; every adjective has its number or mechanism.
  • A non-specialist in the track's second discipline could restate your main claim after two pages.
  • Nothing claim-bearing lives past page 8; no roadmap padding remains.
  • Ethics and provenance sentences sit beside the data description.

Finally, keep the register stable across sections: a measurement-precise Section 3 followed by a marketing-voiced Section 6 ("our groundbreaking framework") reads as two authors who never met. The last pre-submission pass should be a single-owner voice edit of the whole 8 pages.

Output format

text
[Web-native sentence] <quote it, or "missing — routing risk">
[Contribution type] algorithm / system / measurement / dataset / theory
[Register fixes] <constructs undefined, adjectives unattached, platforms named>
[Compression moves] <re-homing applied, pages recovered>
[Remaining risks] <style issues a track panel will still flag>

© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in The-Web-Conference-Skills/skills/webconf-writing-style of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Webconf Writing Style next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Webconf Writing Style compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Webconf Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.7kAutomated safety check: PassMIT
Avoid AI Writingconorbronsdon/avoid-ai-writing4.9k3 repos~8.1kAutomated safety check: PassMIT
BrandOhh-889/skyroc79513 repos~733Automated safety check: PassMIT
Khazix WeChat Article WriterKKKKhazix/khazix-skills21k1 repos~2.9kAutomated safety check: PassMIT
Writing Guidelinesvercel-labs/agent-skills32k7 repos~309Automated safety check: PassNone
Unslop AI Writing Cleanuptheclaymethod/unslop518—~1.7kAutomated safety check: PassMIT

Similar skills

  • Avoid AI Writing

    conorbronsdon/avoid-ai-writing

    Audit and rewrite content to remove AI writing patterns ("AI-isms").

    4.9k GitHub starsUsed in 3 repos~8.1k tokens
    Writing & ContentAuto-check passed

  • Brand

    Ohh-889/skyroc

    Brand voice, visual identity, messaging frameworks, asset management, brand consistency.

    795 GitHub starsUsed in 13 repos~733 tokens
    Writing & ContentAuto-check passed

  • Khazix WeChat Article Writer

    KKKKhazix/khazix-skills

    Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.

    21k GitHub starsUsed in 1 repo~2.9k tokens
    Writing & ContentAuto-check passed

  • Writing Guidelines

    vercel-labs/agent-skills

    Official

    Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.

    32k GitHub starsUsed in 7 repos~309 tokens
    Writing & ContentAuto-check passed

  • Unslop AI Writing Cleanup

    theclaymethod/unslop

    Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.

    518 GitHub stars~1.7k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed

  • UX Writing

    content-designer/ux-writing-skill

    Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.

    224 GitHub starsUsed in 1 repo~3.8k tokens
    Writing & ContentAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

  • Aaag Data Analysis

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Literature Positioning

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Rebuttal

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Research Design

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Review Process

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Submission

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…

    1.2k GitHub stars~1.6k tokensUpdated 14 days ago
    Auto-check passed

Categories

Questions about Webconf Writing Style

What does Webconf Writing Style do?

A skill your agent uses 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…. Webconf Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.

When should I use Webconf Writing Style?

Webconf Writing Style fits situations like: revising a Web Conference (WWW) papers 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; handling scale numbers and platform names with precision.

How do I install Webconf Writing Style in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-writing-style -a claude-code`. Or copy the skill folder (The-Web-Conference-Skills/skills/webconf-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/webconf-writing-style in your project. Claude Code loads it when a task matches its description.

How do I install Webconf Writing Style in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-writing-style -a codex`. Or copy the skill folder (The-Web-Conference-Skills/skills/webconf-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/webconf-writing-style in your project. Codex loads it when a task matches its description.

Can I use Webconf Writing Style in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-writing-style -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/webconf-writing-style, .gemini/skills/webconf-writing-style, .github/skills/webconf-writing-style and .opencode/skills/webconf-writing-style in your project.

What does Webconf Writing Style need to run?

SKILL.md names no scripts, command-line tools or credentials: Webconf Writing Style is instructions for the agent only.

Does Webconf Writing Style access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Webconf Writing Style safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Webconf Writing Style use?

Webconf Writing Style is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Webconf Writing Style use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Webconf Writing Style?

Skills that share tags, products or a category with Webconf Writing Style: Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars), Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars) and Writing Guidelines (vercel-labs/agent-skills, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Webconf Writing Style?

brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.

Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.