Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
Agent skill
Sigcomm Author Response
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an ACM SIGCOMM rebuttal or executing a shepherd-run one-shot revision — triaging reviewer issues, writing a decision-focused anonymous rebuttal for the…
Install Sigcomm Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-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/SIGCOMM-Skills/skills/sigcomm-author-response .claude/skills/sigcomm-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 "sigcomm-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-author-response into .claude/skills/sigcomm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-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/SIGCOMM-Skills/skills/sigcomm-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 sigcomm-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-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/SIGCOMM-Skills/skills/sigcomm-author-response .agents/skills/sigcomm-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 "sigcomm-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-author-response into .agents/skills/sigcomm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-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 sigcomm-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-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/SIGCOMM-Skills/skills/sigcomm-author-response .cursor/skills/sigcomm-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 "sigcomm-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-author-response into .cursor/skills/sigcomm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-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 SIGCOMM-Skills/skills/sigcomm-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 sigcomm-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-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/SIGCOMM-Skills/skills/sigcomm-author-response .gemini/skills/sigcomm-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 "sigcomm-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-author-response into .gemini/skills/sigcomm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-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 sigcomm-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 sigcomm-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/SIGCOMM-Skills/skills/sigcomm-author-response .github/skills/sigcomm-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 "sigcomm-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-author-response into .github/skills/sigcomm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-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 sigcomm-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 sigcomm-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/SIGCOMM-Skills/skills/sigcomm-author-response .opencode/skills/sigcomm-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 "sigcomm-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-author-response into .opencode/skills/sigcomm-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-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.
Facts
- Skill name
sigcomm-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 502 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting an ACM SIGCOMM rebuttal or executing a shepherd-run one-shot revision — triaging reviewer issues, writing a decision-focused anonymous rebuttal for the…
- Works in 3 steps: Point-by-point response mapping each… → Change-marked manuscript so the shepherd… → List of changes at a high level, so a…
- Drafting an ACM SIGCOMM rebuttal
- SKILL.md covers First, know which reply you…, Writing the rebuttal, Executing the one-shot revision and Reviewer pushback patterns and…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sigcomm Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting an ACM SIGCOMM rebuttal or executing a shepherd-run one-shot revision — triaging reviewer issues, writing a decision-focused anonymous rebuttal for the discussion phase, and building the revision packet (point-by-point response, change-marked manuscript, and list of changes) against the required-changes contract.
Its SKILL.md is about 1.1k 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 Research & Science. 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
- Drafting an ACM SIGCOMM rebuttal
- Executing a shepherd-run one-shot revision — triaging reviewer issues
- Writing a decision-focused anonymous rebuttal for the discussion phase
- Building the revision packet (point-by-point response
Example prompts
- “/sigcomm-author-response”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Point-by-point response mapping each required change to exactly what you did and where.
- Change-marked manuscript so the shepherd and reviewers see the diff without hunting.
- List of changes at a high level, so a reader gets the shape before the detail.
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
Sigcomm Author Response loads about 1.1k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 502 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.
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). 502 words, ~1,080 tokens.
Download SKILL.mdSave it as
.claude/skills/sigcomm-author-response/SKILL.md (or your agent's skills folder).- name
- sigcomm-author-response
- description
- Use when drafting an ACM SIGCOMM rebuttal or executing a shepherd-run one-shot revision — triaging reviewer issues, writing a decision-focused anonymous rebuttal for the discussion phase, and building the revision packet (point-by-point response, change-marked manuscript, and list of changes) against the required-changes contract.
SIGCOMM Author Response
SIGCOMM has two distinct author-facing replies, and conflating them is a strategic error. The rebuttal is a short argument during the discussion phase; the one-shot revision is a month-long, shepherd-managed contract. Reopen the current CFP to confirm the mechanics before drafting.
First, know which reply you are writing
| Signal in the letter | You are in | The move |
|---|---|---|
| Reviews plus an invitation to respond, no verdict | Rebuttal / discussion phase | Answer the decision-critical objection concisely |
| A merits summary and a list of required changes | One-shot revision | Treat the list as a binding contract; resubmit with a packet |
| An early notification of rejection | Early reject | No reply reopens it; redirect the work |
Writing the rebuttal
- Answer the concern that decides the paper first: evaluation realism, a missing baseline, a correctness question, or a generalization doubt. Style complaints wait.
- Anchor every answer in evidence already in the submission — a table, a figure, an appendix measurement — rather than promising new experiments the reviewers cannot see.
- Stay anonymous: no institution, deployment name, or private link that breaks double-blind.
- Concede cleanly what cannot be fixed in the window, and scope a camera-ready wording change instead of overclaiming a result you cannot produce now.
- One precise, decision-focused reply per reviewer beats an exhaustive point-by-point that buries the objection that actually matters to the discussion.
Executing the one-shot revision
The revised paper can only be accepted or rejected, so the required-changes list is the grading rubric. Build the packet the CFP expects:
- Point-by-point response mapping each required change to exactly what you did and where.
- Change-marked manuscript so the shepherd and reviewers see the diff without hunting.
- List of changes at a high level, so a reader gets the shape before the detail.
Then work the contract, not the margins:
- Address every listed issue explicitly; a revision that improves adjacent things but dodges a listed item is the classic one-shot rejection.
- Engage the shepherd through HotCRP early — clarify an ambiguous requirement before you build the wrong fix, not after.
- Keep results honest to the new evidence; if a required experiment weakens a claim, rescope the claim rather than hiding the outcome.
Show full SKILL.md (144 more words)Show less
Reviewer pushback patterns and SIGCOMM-ready fixes
| Pushback | What it signals | SIGCOMM-ready fix |
|---|---|---|
| "Evaluated only in simulation" | Evaluation-realism doubt | Point to the testbed/trace result, or commit one in the revision and report it plainly |
| "Baseline is weak" | The strongest alternative was skipped | Add or defend the state-of-the-art comparison at matched conditions |
| "Only mean latency reported" | Tail behavior hidden | Report the relevant percentiles over repeated trials with stated variance |
| "Does it generalize beyond this topology?" | Mechanism looks tuned | Add a topology/parameter sweep, or scope the claim to what was tested |
Micro-example (revision)
Reviewer requires a comparison against the deployed state-of-the-art at matched throughput. Packet skeleton: (1) response entry naming the added baseline and the section/table that now holds it; (2) change-marked Section 5 with the new column; (3) change-list line "Added state-of-the-art baseline X at matched throughput (Table 2)." No unlisted claims sneak in.
Output format
[Reply type] rebuttal / one-shot revision / n-a (early reject)
[Priority issue] <the objection that decides the outcome>
[Evidence anchor] <table / figure / appendix / new run>
[Revision packet] response / marked diff / change list — status
[Shepherd touchpoint] <what to confirm before building>
[Forbidden content removed] <identity leaks, unlisted new claims>© 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 SIGCOMM-Skills/skills/sigcomm-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sigcomm 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 |
|---|---|---|---|---|---|---|
| Sigcomm Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag 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…
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…
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…
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…
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…
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…
Related
Categories
Questions about Sigcomm Author Response
What does Sigcomm Author Response do?
A skill your agent uses when drafting an ACM SIGCOMM rebuttal or executing a shepherd-run one-shot revision — triaging reviewer issues, writing a decision-focused anonymous rebuttal for the…. Sigcomm Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting an ACM SIGCOMM rebuttal or executing a shepherd-run one-shot revision — triaging reviewer issues, writing a decision-focused anonymous rebuttal for the discussion phase, and building the revision packet (point-by-point response, change-marked manuscript, and list of changes) against the required-changes contract.
When should I use Sigcomm Author Response?
Sigcomm Author Response fits situations like: drafting an ACM SIGCOMM rebuttal; executing a shepherd-run one-shot revision — triaging reviewer issues; writing a decision-focused anonymous rebuttal for the discussion phase; building the revision packet (point-by-point response.
How do I install Sigcomm Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-author-response -a claude-code`. Or copy the skill folder (SIGCOMM-Skills/skills/sigcomm-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sigcomm-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Sigcomm Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-author-response -a codex`. Or copy the skill folder (SIGCOMM-Skills/skills/sigcomm-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sigcomm-author-response in your project. Codex loads it when a task matches its description.
Can I use Sigcomm Author Response 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 sigcomm-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/sigcomm-author-response, .gemini/skills/sigcomm-author-response, .github/skills/sigcomm-author-response and .opencode/skills/sigcomm-author-response in your project.
What does Sigcomm Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Sigcomm Author Response is instructions for the agent only.
Does Sigcomm Author Response 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 Sigcomm Author Response 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 Sigcomm Author Response use?
Sigcomm 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.
How many tokens does Sigcomm Author Response use?
About 1.1k tokens (SKILL.md is roughly 4.3k 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 Sigcomm Author Response?
Skills that share tags, products or a category with Sigcomm Author Response: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sigcomm Author Response?
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.