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 drafting an EMNLP author response in the ACL Rolling Review discussion window — triaging replies by soundness versus excitement, deciding what evidence can be added…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills emnlp-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/EMNLP-Skills/skills/emnlp-author-response .claude/skills/emnlp-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 "emnlp-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-author-response into .claude/skills/emnlp-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-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/EMNLP-Skills/skills/emnlp-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 emnlp-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills emnlp-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/EMNLP-Skills/skills/emnlp-author-response .agents/skills/emnlp-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 "emnlp-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-author-response into .agents/skills/emnlp-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-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 emnlp-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills emnlp-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/EMNLP-Skills/skills/emnlp-author-response .cursor/skills/emnlp-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 "emnlp-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-author-response into .cursor/skills/emnlp-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-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 EMNLP-Skills/skills/emnlp-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 emnlp-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills emnlp-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/EMNLP-Skills/skills/emnlp-author-response .gemini/skills/emnlp-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 "emnlp-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-author-response into .gemini/skills/emnlp-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-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 emnlp-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 emnlp-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/EMNLP-Skills/skills/emnlp-author-response .github/skills/emnlp-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 "emnlp-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-author-response into .github/skills/emnlp-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-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 emnlp-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 emnlp-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/EMNLP-Skills/skills/emnlp-author-response .opencode/skills/emnlp-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 "emnlp-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/EMNLP-Skills/skills/emnlp-author-response into .opencode/skills/emnlp-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emnlp-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.
emnlp-author-responseA skill your agent uses when drafting an EMNLP author response in the ACL Rolling Review discussion window — triaging replies by soundness versus excitement, deciding what evidence can be added…
Emnlp Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting an EMNLP author response in the ACL Rolling Review discussion window — triaging replies by soundness versus excitement, deciding what evidence can be added mid-review, staying anonymous, and writing for the area chair's meta-review and the post-commitment Senior Area Chairs, not the reviewers alone.
Its SKILL.md is about 1.6k 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.
Emnlp Author Response loads about 1.6k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 799 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). 799 words, ~1,649 tokens.
.claude/skills/emnlp-author-response/SKILL.md (or your agent's skills folder).Use this when ARR reviews land. In the May 2026 cycle the author response and author-reviewer discussion ran July 7-13, with meta-reviews released July 30 and EMNLP commitment due August 2 — a pipeline where the response is written once but read three times: by reviewers who may update, by the AC composing the meta-review, and by the conference SACs who see the whole record after commitment. Confirm the current window mechanics on the live ARR pages before drafting.
Sort every reviewer point by which score it threatens:
The response box takes text and, in ARR practice, a revised PDF may accompany a resubmission rather than a same-cycle response — do not build the plan around uploading new material unless the current cycle's instructions explicitly allow it. Within text:
| Addition | Safe? | Why |
|---|---|---|
| Numbers from runs completed during the window | Usually | Reviewers can weigh them; label as new |
| A significance test on already-reported results | Yes | It re-analyzes existing evidence |
| A promised camera-ready rewrite | Yes, if scoped | Commit to wording, not to new experiments |
| A brand-new experimental direction | No | Unreviewable in-window; save it for revise-and-resubmit |
| Links to external results pages | No | Anonymity and auditability both break |
R2.1 (baseline tuning, soundness): Correct that §5.2 did not state the search budget.
Both systems received identical 32-trial random search over the grid in App. C; we
will state this in §5.2. Under matched budgets the gap is 2.1 F1 (±0.4 over 5 seeds,
paired bootstrap p=0.003, already in Table 3).
R2.4 (only high-resource languages, scope): We agree and will retitle the claim to
the six tested languages. We note Swahili and Tamil results in App. E show the same
direction at lower magnitude — we will surface this in §7 rather than claim
generality we did not test.The pattern: number every reply to a numbered concern; concede early where the reviewer is right; convert each concession into a specific, checkable edit; anchor every number to a location in the submitted record.
<system>?" Either the comparison exists under another
name (say so), or explain the confound that makes it uninformative, or run it if the
window permits. "Out of scope" without a reason is read as "we would lose."Three-reviewer packets regularly split: R1 wants more languages, R3 thinks the language set is already too broad for the method's claims. Do not answer each in isolation — the AC will read both replies side by side and see you agreeing with everyone. Instead:
A special case is the score-text mismatch: a review whose text is mild but whose overall recommendation is harsh (or vice versa). Respond to the text — it is the only part you can engage — and let the mismatch itself be visible to the AC without commenting on it.
Some packets should not be argued with. If all three reviewers converge on a missing piece of evidence that cannot be produced in the window — a new annotation effort, a second domain, a human study — the strongest move is a short, gracious response that corrects factual errors only, followed by revise-and-resubmit into a later cycle where the same reviewers will see the gap actually closed. A maximal rebuttal that concedes nothing, against a unanimous packet, damages the record that the SACs will later read at commitment time.
[Concern map] <Rx.y -> soundness / excitement / misreading / taste>
[Reply drafts] <numbered, evidence-anchored, concession-explicit>
[New-in-window evidence] <what was computed, labeled as new>
[Camera-ready commitments] <specific edits promised>
[Residual risk after response] <what remains unresolved and why>© 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 EMNLP-Skills/skills/emnlp-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Emnlp 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 |
|---|---|---|---|---|---|---|
| Emnlp Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | 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 | |
| Acl Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Eacl Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Icsme 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.
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 ACL author response inside an ACL Rolling Review cycle on OpenReview, covering the response window before meta-review, reviewer discussion dynamics…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an EACL author response during the ACL Rolling Review rebuttal window, covering how to triage reviewer points, address the action editor who writes the…
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 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 an EMNLP author response in the ACL Rolling Review discussion window — triaging replies by soundness versus excitement, deciding what evidence can be added…. Emnlp Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting an EMNLP author response in the ACL Rolling Review discussion window — triaging replies by soundness versus excitement, deciding what evidence can be added mid-review, staying anonymous, and writing for the area chair's meta-review and the post-commitment Senior Area Chairs, not the reviewers alone.
Emnlp Author Response fits situations like: drafting an EMNLP author response in the ACL Rolling Review discussion window — triaging replies by soundness versus excitement; deciding what evidence can be added mid-review; staying anonymous; writing for the area chairs meta-review and the post-commitment Senior Area Chairs.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill emnlp-author-response -a claude-code`. Or copy the skill folder (EMNLP-Skills/skills/emnlp-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/emnlp-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 emnlp-author-response -a codex`. Or copy the skill folder (EMNLP-Skills/skills/emnlp-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/emnlp-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 emnlp-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/emnlp-author-response, .gemini/skills/emnlp-author-response, .github/skills/emnlp-author-response and .opencode/skills/emnlp-author-response in your project.
SKILL.md names no scripts, command-line tools or credentials: Emnlp 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.
Emnlp 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.6k tokens (SKILL.md is roughly 6.6k 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 Emnlp Author Response: Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Hermes Agent Skill Authoring (NousResearch/hermes-agent, 252k stars), Acl Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Eacl 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.