Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when organizing the material around an ACM SIGCOMM paper — deciding what lives in the 12-page body versus references versus optional appendices, keeping the main paper…
Install Sigcomm Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-supplementary --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-supplementary .claude/skills/sigcomm-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-supplementary into .claude/skills/sigcomm-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-supplementary", 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-supplementaryType 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-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-supplementary --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-supplementary .agents/skills/sigcomm-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-supplementary into .agents/skills/sigcomm-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-supplementary", 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-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-supplementary --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-supplementary .cursor/skills/sigcomm-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-supplementary into .cursor/skills/sigcomm-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-supplementary", 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-supplementary--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-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigcomm-supplementary --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-supplementary .gemini/skills/sigcomm-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-supplementary into .gemini/skills/sigcomm-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-supplementary", 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-supplementaryInstalls 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-supplementary -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-supplementary .github/skills/sigcomm-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-supplementary into .github/skills/sigcomm-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-supplementary", 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-supplementary -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-supplementary --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-supplementary .opencode/skills/sigcomm-supplementary && 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-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGCOMM-Skills/skills/sigcomm-supplementary into .opencode/skills/sigcomm-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigcomm-supplementary", 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-supplementary- GitHub stars
- 1.2k
- Token cost
- ~950 tokens
- SKILL.md length
- 432 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when organizing the material around an ACM SIGCOMM paper — deciding what lives in the 12-page body versus references versus optional appendices, keeping the main paper…
- Organizing the material around an ACM SIGCOMM paper — deciding what lives in the 12-page body versus references versus optional appendices
- SKILL.md covers What goes where, The appendix-necessity rule…, Placement table and Keep the body self-contained, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Keeping the main paper self-contained
What it does
Sigcomm Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when organizing the material around an ACM SIGCOMM paper — deciding what lives in the 12-page body versus references versus optional appendices, keeping the main paper self-contained, anticipating the shepherd's appendix-necessity approval, and placing extended measurements and proofs outside the cap without hiding load-bearing content.
Its SKILL.md is about 950 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
- Organizing the material around an ACM SIGCOMM paper — deciding what lives in the 12-page body versus references versus optional appendices
- Keeping the main paper self-contained
- Anticipating the shepherds appendix-necessity approval
- Placing extended measurements and proofs outside the cap without hiding load-bearing content
Example prompts
- “/sigcomm-supplementary”
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 Supplementary loads about 950 tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 432 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). 432 words, ~950 tokens.
Download SKILL.mdSave it as
.claude/skills/sigcomm-supplementary/SKILL.md (or your agent's skills folder).- name
- sigcomm-supplementary
- description
- Use when organizing the material around an ACM SIGCOMM paper — deciding what lives in the 12-page body versus references versus optional appendices, keeping the main paper self-contained, anticipating the shepherd's appendix-necessity approval, and placing extended measurements and proofs outside the cap without hiding load-bearing content.
SIGCOMM Supplementary
Use this when splitting a SIGCOMM paper across body, references, and appendices. The controlling rule: the 12 single-spaced pages before references must carry the argument on their own; appendices and references sit outside the cap but do not rescue an incomplete body. Reopen the current CFP to confirm this edition's appendix handling.
What goes where
- Body (≤ 12 single-spaced pages, figures and tables included): the measured problem, the design principle, the mechanism, and the decision-critical evaluation. A reviewer must understand and believe the contribution without turning to an appendix.
- References (outside the cap): as many as needed; never trimmed for space or anonymity.
- Appendices (optional, after references, outside the cap): extended measurement sweeps, additional topologies, proofs or derivations, detailed configuration, and workload specifics — support, not substitute.
The appendix-necessity rule changes the calculus
Unlike venues where appendices are a free overflow bin, SIGCOMM's shepherd approves whether each appendix is necessary at camera-ready. Write appendices you can defend as load-bearing, and never park a step the argument depends on where a shepherd might cut it. A safe test: if removing an appendix would make a body claim unverifiable, that content probably belongs in the body or the artifact, not in a droppable appendix.
Placement table
| Content | Home | Why |
|---|---|---|
| The core mechanism and its principle | Body | The contribution reviewers evaluate |
| The one or two decision-critical figures | Body | The evidence the accept/reject turns on |
| Extra topology / parameter sweeps | Appendix | Depth without crowding the 12 pages |
| Full configuration and workload spec | Appendix or artifact | Reproducibility detail, referenced from the body |
| Proof or derivation for an analytical claim | Appendix | Body keeps the statement and a sketch |
| Raw logs and per-run tables | Artifact | Never the paper's job to hold these |
Show full SKILL.md (148 more words)Show less
Keep the body self-contained
- Every appendix and artifact item must be cross-referenced from the body at least once; orphaned supplementary material is invisible and, at camera-ready, deletable.
- Order appendix sections to mirror the body's flow so a reader navigates by section, not by hunting.
- State results in the body and defer only the support — a reader who never opens an appendix should still be able to reconstruct why the contribution holds.
Vignette: splitting a congestion-control paper
A submission proposes a new congestion signal with a testbed evaluation and a small stability argument. The body keeps the measured motivation, the signal and its principle, the two decision-critical tail-latency figures, and a one-paragraph stability sketch. The appendix holds the full stability derivation, a switch-buffer sweep, and the fairness-across-flows tables; the artifact carries the driver and logs. Nothing the accept decision depends on lives only in a droppable place.
Output format
[Body self-contained] yes / no (what breaks without an appendix)
[Body budget] within 12 single-spaced pre-reference pages? yes/no
[Placement map] <content -> body / appendix / artifact>
[Appendix necessity] each appendix defensible to a shepherd? yes/no
[Cross-reference gaps] <orphaned supplementary items>© 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-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sigcomm Supplementary 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 Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~950 | 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 Supplementary
What does Sigcomm Supplementary do?
A skill your agent uses when organizing the material around an ACM SIGCOMM paper — deciding what lives in the 12-page body versus references versus optional appendices, keeping the main paper…. Sigcomm Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when organizing the material around an ACM SIGCOMM paper — deciding what lives in the 12-page body versus references versus optional appendices, keeping the main paper self-contained, anticipating the shepherd's appendix-necessity approval, and placing extended measurements and proofs outside the cap without hiding load-bearing content.
When should I use Sigcomm Supplementary?
Sigcomm Supplementary fits situations like: organizing the material around an ACM SIGCOMM paper — deciding what lives in the 12-page body versus references versus optional appendices; keeping the main paper self-contained; anticipating the shepherds appendix-necessity approval; placing extended measurements and proofs outside the cap without hiding load-bearing content.
How do I install Sigcomm Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-supplementary -a claude-code`. Or copy the skill folder (SIGCOMM-Skills/skills/sigcomm-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sigcomm-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Sigcomm Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-supplementary -a codex`. Or copy the skill folder (SIGCOMM-Skills/skills/sigcomm-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sigcomm-supplementary in your project. Codex loads it when a task matches its description.
Can I use Sigcomm Supplementary 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-supplementary -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-supplementary, .gemini/skills/sigcomm-supplementary, .github/skills/sigcomm-supplementary and .opencode/skills/sigcomm-supplementary in your project.
What does Sigcomm Supplementary need to run?
SKILL.md names no scripts, command-line tools or credentials: Sigcomm Supplementary is instructions for the agent only.
Does Sigcomm Supplementary 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 Supplementary 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 Supplementary use?
Sigcomm Supplementary 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 Supplementary use?
About 950 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sigcomm Supplementary?
Skills that share tags, products or a category with Sigcomm Supplementary: 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 Supplementary?
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.