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.
A skill your agent uses when reviews arrive for a SIGIR submission and the authors must decide how to answer — triaging IR-reviewer objections (weak baselines, missing significance tests, collection…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigir-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigir-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/SIGIR-Skills/skills/sigir-author-response .claude/skills/sigir-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 "sigir-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-author-response into .claude/skills/sigir-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-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/SIGIR-Skills/skills/sigir-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 sigir-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigir-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/SIGIR-Skills/skills/sigir-author-response .agents/skills/sigir-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 "sigir-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-author-response into .agents/skills/sigir-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-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 sigir-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigir-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/SIGIR-Skills/skills/sigir-author-response .cursor/skills/sigir-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 "sigir-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-author-response into .cursor/skills/sigir-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-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 SIGIR-Skills/skills/sigir-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 sigir-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigir-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/SIGIR-Skills/skills/sigir-author-response .gemini/skills/sigir-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 "sigir-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-author-response into .gemini/skills/sigir-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-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 sigir-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 sigir-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/SIGIR-Skills/skills/sigir-author-response .github/skills/sigir-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 "sigir-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-author-response into .github/skills/sigir-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-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 sigir-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 sigir-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/SIGIR-Skills/skills/sigir-author-response .opencode/skills/sigir-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 "sigir-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGIR-Skills/skills/sigir-author-response into .opencode/skills/sigir-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigir-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.
sigir-author-responseA skill your agent uses when reviews arrive for a SIGIR submission and the authors must decide how to answer — triaging IR-reviewer objections (weak baselines, missing significance tests, collection…
Sigir Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reviews arrive for a SIGIR submission and the authors must decide how to answer — triaging IR-reviewer objections (weak baselines, missing significance tests, collection choice), writing within whatever response mechanism the current SIGIR cycle actually offers, and planning the resubmission path if the answer is no.
Its SKILL.md is about 1.8k 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.
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.
Sigir Author Response loads about 1.8k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 865 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). 865 words, ~1,750 tokens.
.claude/skills/sigir-author-response/SKILL.md (or your agent's skills folder).First establish what response channel exists this cycle. SIGIR does not have a famous institutionalized rebuttal ritual the way ICLR or KDD do, and whether a given edition runs an author-response or discussion phase for full/short papers was not verifiable for 2026 (待核实 — check the track page and the OpenReview timeline of your own submission). This skill therefore covers three situations: a real response window, no window at all, and the post-rejection letter.
Treat it as a precision instrument, not a second paper. SIGIR reviewers are IR methodologists; the objections cluster predictably, and each cluster has a strongest honest answer:
| Objection cluster | Weak reply | Strong reply |
|---|---|---|
| "Baselines are outdated / not tuned" | "We will add X" | Name the tuning protocol already in the paper (grid, budget, dev split) and cite the table row proving parity of effort |
| "No significance testing" | "Differences are large" | Report the paired test you ran (test, correction, p or CI) with exact table coordinates; if you truly didn't run one, concede and state what you will report |
| "Only one collection" | "Others are future work" | Explain the claim's scope: which property of the collection the claim depends on, and why generalization is or is not asserted |
| "Metric choice hides the effect" | Defend the metric abstractly | Show the effect on the reviewer's preferred metric if it is computable from your runs — run files make this a one-line answer |
| "This is a known result" | Assert novelty | Contrast mechanisms against the specific cited paper: what it does, what yours does, what breaks if the delta is removed |
Rules of engagement:
Then the response happens before submission. Write the paper so the predictable objections above are pre-answered: a tuning-protocol paragraph, a significance-testing sentence under every close comparison, an explicit claim-scope sentence for the collection lineup. Budget half a page of the 9 for pre-emption; it is the cheapest acceptance probability you can buy at a venue where you may never get to talk back.
Reply skeleton per reviewer (aim: fits on one screen)
---------------------------------------------------
Thanks + one-line summary of what we changed/clarify.
[W1] <reviewer's words, 1 line>
-> Answer with coordinates. (Table/§/Fig)
-> If conceded: what we will do, where it will go.
[W2] ...
Closing: the one thing we most want re-weighed, stated once.Anti-patterns that reliably backfire with IR reviewers:
IR is a small field: the reviewer you bruise this cycle chairs your session next year. Calibrate register per line, not per document:
Too hot: "R2 clearly has not read Section 5, where this is addressed." Too cold: "We thank the reviewer for this insightful comment and will carefully consider it in future work." Right: "§5.2 ¶3 reports this experiment (Table 4, rows 2-3); we agree the pointer from §3 was too subtle and will add a forward reference."
The pattern: locate, concede the findability problem even when the content exists, and commit to the small fix. Reserve firm disagreement for factual errors, and spend it at most once per reviewer — a response that disputes everything is read as disputing nothing.
Because run files exist (if sigir-artifact-evaluation was followed), several
reviewer requests are answerable in hours without new training:
ir_measures.[Response channel] confirmed window / none this cycle / post-rejection
[Reviewer map] R1: <stance, key ask> | R2: ... | R3: ...
[Triage] answerable-with-coordinates / concede-and-fix / out-of-scope
[New-evidence budget] <what, if anything, gets computed during the window>
[Resubmission route] next SIGIR cycle / SIGIR-AP R&R / ECIR / CIKM / WSDM / TOIS
[One ask] <the single re-weighing request to close with>© 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 SIGIR-Skills/skills/sigir-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Sigir 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 |
|---|---|---|---|---|---|---|
| Sigir Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT | |
| Hermes Agent Skill AuthoringNousResearch/hermes-agent | 252k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Icsme Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | 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 |
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.
NousResearch/hermes-agent
Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an IEEE ICSME author response during the double-anonymous author-response period, covering the early-decision cut that decides whether you respond at all…
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 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 reviews arrive for a SIGIR submission and the authors must decide how to answer — triaging IR-reviewer objections (weak baselines, missing significance tests, collection…. Sigir Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reviews arrive for a SIGIR submission and the authors must decide how to answer — triaging IR-reviewer objections (weak baselines, missing significance tests, collection choice), writing within whatever response mechanism the current SIGIR cycle actually offers, and planning the resubmission path if the answer is no.
Sigir Author Response fits situations like: reviews arrive for a SIGIR submission and the authors must decide how to answer — triaging IR-reviewer objections (weak baselines; missing significance tests; collection choice); writing within whatever response mechanism the current SIGIR cycle actually offers.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigir-author-response -a claude-code`. Or copy the skill folder (SIGIR-Skills/skills/sigir-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sigir-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 sigir-author-response -a codex`. Or copy the skill folder (SIGIR-Skills/skills/sigir-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sigir-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 sigir-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/sigir-author-response, .gemini/skills/sigir-author-response, .github/skills/sigir-author-response and .opencode/skills/sigir-author-response in your project.
SKILL.md names no scripts, command-line tools or credentials: Sigir 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.
Sigir 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.8k tokens (SKILL.md is roughly 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 Sigir Author Response: Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Hermes Agent Skill Authoring (NousResearch/hermes-agent, 252k stars), Icsme Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Fast 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.