Responsive Units
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
Agent skill
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting the Web Conference (WWW) rebuttal inside its one-week window, triaging reviews from the venue's mixed systems/mining/social-science reviewer pool, answering…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-author-response --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-author-response .claude/skills/webconf-author-response && rm -rf skills-srcUse ~/.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/
Install the "webconf-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-author-response into .claude/skills/webconf-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-author-response", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-author-responseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-author-response --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/The-Web-Conference-Skills/skills/webconf-author-response .agents/skills/webconf-author-response && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "webconf-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-author-response into .agents/skills/webconf-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-author-response", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-author-response --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/The-Web-Conference-Skills/skills/webconf-author-response .cursor/skills/webconf-author-response && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "webconf-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-author-response into .cursor/skills/webconf-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-author-response", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path The-Web-Conference-Skills/skills/webconf-author-response--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-author-response --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/The-Web-Conference-Skills/skills/webconf-author-response .gemini/skills/webconf-author-response && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "webconf-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-author-response into .gemini/skills/webconf-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-author-response", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-author-responseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-author-response -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/The-Web-Conference-Skills/skills/webconf-author-response .github/skills/webconf-author-response && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "webconf-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-author-response into .github/skills/webconf-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-author-response", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-author-response -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-author-response --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/The-Web-Conference-Skills/skills/webconf-author-response .opencode/skills/webconf-author-response && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "webconf-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-author-response into .opencode/skills/webconf-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-author-response", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
webconf-author-responseA skill your agent uses when drafting the Web Conference (WWW) rebuttal inside its one-week window, triaging reviews from the venue's mixed systems/mining/social-science reviewer pool, answering…
Webconf Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting the Web Conference (WWW) rebuttal inside its one-week window, triaging reviews from the venue's mixed systems/mining/social-science reviewer pool, answering misread-track objections, protecting anonymity, and deciding what can honestly be promised for the camera-ready versus what needs new evidence.
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.
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.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Webconf Author Response loads about 1.7k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 714 words of instructions outside code blocks.
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.
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.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 714 words, ~1,665 tokens.
.claude/skills/webconf-author-response/SKILL.md (or your agent's skills folder).The 2026 rebuttal window ran November 24 - December 1, 2025 — seven days, scheduled over a major holiday week in North America, between the October 7 paper deadline and the January 13 notification. Plan writing capacity for that specific week the moment the paper goes in. Exact mechanics (length caps, per-review vs. single response, revised-PDF permission) were not published in the sources this pack could verify; confirm them in the review platform the day reviews arrive, before drafting.
Web Conference reviews come from a track-scoped pool, and the venue's defining property is that neighboring tracks read the same paper differently. A recommendation paper reviewed in "User modeling, personalization and recommendation" gets offline-metric and baseline questions; the same paper in "Social networks and social media" gets construct-validity and user-harm questions. Before answering anything, classify each review:
| Reviewer stance | Diagnostic signal | Response strategy |
|---|---|---|
| In-track expert | Names specific baselines/datasets you skipped | Concede or supply numbers; never hand-wave |
| Adjacent-track lens | Questions assume a different evidence standard | Restate the track's contribution type, then answer on their terms |
| Web-fit skeptic | "Why is this a WWW paper?" | Point to the web-native element: platform data, web-scale constraint, user behavior |
| Feasibility doubter | "Would this survive real traffic / real crawls?" | Cite the appendix's systems details by section number |
The "why is this a WWW paper" objection is the venue's signature rejection reason and deserves its own paragraph in almost every rebuttal: name the property of the Web (openness, adversarial content, platform incentives, hyperlink structure, live user feedback) without which the contribution would not exist.
review class option prints line numbers for exactly this).<company>."[Common thread] (2-4 sentences shared across reviewers)
All reviewers asked about X; the short answer is Y (Sec 4.2, lines 512-530).
[R1 - in-track]
Q: missing baseline B. A: added; B underperforms ours by <delta> on the same
split (protocol identical to Table 2). Will appear in Table 2.
Q: dataset freshness. A: crawl window and snapshot date are in App. A; we will
surface them in Sec 3.1.
[R2 - adjacent track]
Your reading applies the <other-track> bar of <standard>. Our claim is a
<contribution type> claim; under the track's CFP scope, the evidence in Sec 5
addresses it because <reason>. On your specific concern: <direct answer>.
[R3 - web-fit skeptic]
The method exploits <web-native property>; without it, <what breaks>. Non-web
analogues (e.g., <venue>) do not face <constraint>.One discipline per answer: quote the reviewer's actual sentence, answer it in the first line, then justify. Reviewers reread rebuttals in minutes, not hours.
Reviewer sentence: "The improvements may come from the larger embedding table rather than the proposed crawl-time signal."
Weak answer (defensive, unfalsifiable):
We respectfully disagree. Our method is fundamentally different from simply increasing capacity, as explained in Section 4. The crawl-time signal is a key novel contribution and the results clearly demonstrate its effectiveness.
Strong answer (evidence-anchored, one new number, page-cited):
Table 3 row 4 already controls for this: the parameter-matched ablation (identical embedding budget, signal removed) loses 3.8 points (p. 7, lines 689-702). We add one cell for completeness: doubling the baseline's embedding table recovers only 0.4 of those points. We will fold this cell into Table 3 and state the parameter counts in the caption.
The differences that matter: the strong answer names the existing evidence by coordinates, adds the smallest experiment that decides the question, and ends with a concrete, budget-compatible camera-ready commitment. It also never uses "novel," "fundamentally," or "clearly" — calibration words that track chairs discount automatically.
Nothing can be added between December 1 and the January 13 notification; do not
email chairs with supplements. If the outcome is rejection, the same cycle still
offered later routes in 2026 — short papers (November deadlines) closed before
notification, but the next edition's research tracks and the current edition's
workshop calls remain; route via webconf-workflow.
[Rebuttal plan] <n> reviews: <in-track/adjacent/web-fit/feasibility counts>
[Common thread] <the one issue answered once for everyone>
[New evidence] <small additions only, with source of numbers>
[Concessions] <what is admitted and how the camera-ready will phrase it>
[Anonymity check] pass / fail
[Unverified mechanics] <length cap / format items confirmed in-platform>© 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
Just SKILL.md in The-Web-Conference-Skills/skills/webconf-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Webconf Author Response 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Webconf Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT | |
| Fast Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Icassp Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Aaai Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~924 | Automated safety check: Pass | MIT | |
| Socc Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT |
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting USENIX FAST author responses, covering the short pre-notification rebuttal during the author-response period and — distinctively — the one-shot-revision change…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an ICASSP rebuttal or author response to reviews, covering the recently added and short author-response window, the single-blind setting where reviewers already…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an ACM SoCC author response (rebuttal) during a round's response window, covering the single written turn, answering both the systems and the data/measurement…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting a TACAS (ETAPS) author response for the rebuttal window, covering the short single-round rebuttal, answering soundness and benchmark-fairness objections with…
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…
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…
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…
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…
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…
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…
A skill your agent uses when drafting the Web Conference (WWW) rebuttal inside its one-week window, triaging reviews from the venue's mixed systems/mining/social-science reviewer pool, answering…. Webconf Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting the Web Conference (WWW) rebuttal inside its one-week window, triaging reviews from the venue's mixed systems/mining/social-science reviewer pool, answering misread-track objections, protecting anonymity, and deciding what can honestly be promised for the camera-ready versus what needs new evidence.
Webconf Author Response fits situations like: drafting the Web Conference (WWW) rebuttal inside its one-week window; triaging reviews from the venues mixed systems/mining/social-science reviewer pool; answering misread-track objections; protecting anonymity.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-author-response -a claude-code`. Or copy the skill folder (The-Web-Conference-Skills/skills/webconf-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/webconf-author-response in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-author-response -a codex`. Or copy the skill folder (The-Web-Conference-Skills/skills/webconf-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/webconf-author-response in your project. Codex loads it when a task matches its description.
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-author-response -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-author-response, .gemini/skills/webconf-author-response, .github/skills/webconf-author-response and .opencode/skills/webconf-author-response in your project.
SKILL.md names no scripts, command-line tools or credentials: Webconf Author Response is instructions for the agent only.
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.
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.
Webconf Author Response is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Webconf Author Response: Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Fast Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars), Icassp Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Aaai Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.