Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
Agent skill
Infocom Reproducibility
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when strengthening IEEE INFOCOM reproducibility even though the venue runs no formal artifact-evaluation track, covering pinned simulator setups, released code and datasets…
Install Infocom Reproducibility
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-reproducibility -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-reproducibility --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/INFOCOM-Skills/skills/infocom-reproducibility .claude/skills/infocom-reproducibility && 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 "infocom-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-reproducibility into .claude/skills/infocom-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-reproducibility", 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/INFOCOM-Skills/skills/infocom-reproducibilityType 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 infocom-reproducibility -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-reproducibility --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/INFOCOM-Skills/skills/infocom-reproducibility .agents/skills/infocom-reproducibility && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "infocom-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-reproducibility into .agents/skills/infocom-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-reproducibility", 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 infocom-reproducibility -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-reproducibility --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/INFOCOM-Skills/skills/infocom-reproducibility .cursor/skills/infocom-reproducibility && 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 "infocom-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-reproducibility into .cursor/skills/infocom-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-reproducibility", 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 INFOCOM-Skills/skills/infocom-reproducibility--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 infocom-reproducibility -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-reproducibility --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/INFOCOM-Skills/skills/infocom-reproducibility .gemini/skills/infocom-reproducibility && 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 "infocom-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-reproducibility into .gemini/skills/infocom-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-reproducibility", 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 infocom-reproducibilityInstalls 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 infocom-reproducibility -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/INFOCOM-Skills/skills/infocom-reproducibility .github/skills/infocom-reproducibility && 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 "infocom-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-reproducibility into .github/skills/infocom-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-reproducibility", 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 infocom-reproducibility -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 infocom-reproducibility --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/INFOCOM-Skills/skills/infocom-reproducibility .opencode/skills/infocom-reproducibility && 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 "infocom-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-reproducibility into .opencode/skills/infocom-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-reproducibility", 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
infocom-reproducibility- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 563 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when strengthening IEEE INFOCOM reproducibility even though the venue runs no formal artifact-evaluation track, covering pinned simulator setups, released code and datasets…
- Strengthening IEEE INFOCOM reproducibility even though the venue runs no formal artifact-evaluation track
- SKILL.md covers Evidence map, What "reproducible" means…, Provenance and setup pinning and IEEE reproducibility options…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering pinned simulator setups
What it does
Infocom Reproducibility is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when strengthening IEEE INFOCOM reproducibility even though the venue runs no formal artifact-evaluation track, covering pinned simulator setups, released code and datasets where possible, complete proofs and parameters within the page budget, IEEE reproducibility-badge options, and consistency between what the paper claims and what a reader could rebuild.
Its SKILL.md is about 1.3k 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, covering Reproducible research. 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
- Strengthening IEEE INFOCOM reproducibility even though the venue runs no formal artifact-evaluation track
- Covering pinned simulator setups
- Released code and datasets where possible
- Complete proofs and parameters within the page budget
Example prompts
- “/infocom-reproducibility”
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
Infocom Reproducibility loads about 1.3k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 563 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). 563 words, ~1,330 tokens.
Download SKILL.mdSave it as
.claude/skills/infocom-reproducibility/SKILL.md (or your agent's skills folder).- name
- infocom-reproducibility
- description
- Use when strengthening IEEE INFOCOM reproducibility even though the venue runs no formal artifact-evaluation track, covering pinned simulator setups, released code and datasets where possible, complete proofs and parameters within the page budget, IEEE reproducibility-badge options, and consistency between what the paper claims and what a reader could rebuild.
INFOCOM Reproducibility
Use this before submission and again before camera-ready. INFOCOM has no formal artifact-evaluation track (as of 2026-07-09; 待核实 whether a cycle adds one), so reproducibility is a matter of credibility, not a badge you are forced to earn. The goal is that a competent networking reader could rebuild your evidence and reach your conclusions from the paper plus any material you choose to release — which, at a large venue with no rebuttal, is how you convert a skeptical reviewer.
Evidence map
- Map each theorem, algorithm, and reported number to a verifiable location — a proof (in the body or a tight in-budget appendix), a simulator configuration, or a released script/dataset.
- For analytical results, give enough of the assumptions, derivation, and parameters that a reader could re-derive or check the bound. A theorem whose proof is "omitted for space" with no pointer is a weakness a reviewer cannot rebut for you.
- For simulation/measurement, report the simulator and version, topology and traffic model, seeds, number of runs, and the parameters — enough to re-run.
- Releasing code/data is optional but persuasive. Where you can, deposit the simulator scripts, the trace, and the plotting code in a public archive; where you cannot (proprietary traces, privacy), say so and why.
- Keep the paper and any released material consistent: a number in the PDF that no released script or stated configuration produces reads as carelessness.
What "reproducible" means without a badge track
| Claim in the paper | Weak reproducibility answer | INFOCOM-persuasive answer |
|---|---|---|
| "We prove Theorem 1" | "Proof omitted for space" (no pointer) | Proof sketch in body + full proof in the in-budget appendix or a stated report |
| "We simulate at scale" | "ns-3 simulation" (no setup) | Named simulator + version, topology/traffic, seeds, runs, CIs; scripts if releasable |
| "On a real trace" | "a real dataset" (unnamed) | The trace's source and access, preprocessing, and inclusion criteria |
| "Our policy beats X" | Point estimates only | Seeded runs with CIs; released config so the comparison can be re-run |
Because there is no artifact evaluator and (traditionally) no rebuttal, "trust us" does not scale — convert every hand-wave into a stated configuration or a released file.
Show full SKILL.md (214 more words)Show less
Provenance and setup pinning
[Analysis] list assumptions; give full proofs (in-budget appendix or a cited technical report);
state all parameters used in the theorems
[Simulation] name and version the simulator; pin topology, traffic model, seeds, run count;
archive the scripts and configs if releasable
[Measurement] record the trace source and dates; document preprocessing, filtering, and confounds
[Compute] state hardware and runtime so a reader can size a reproduction
[Randomness] log seeds for stochastic steps; say what is and is not deterministicIEEE reproducibility options (optional, post-decision)
- IEEE offers reproducibility avenues (e.g., IEEE DataPort for datasets, and code/data badges on some IEEE venues) that authors may use to deposit artifacts with a DOI. INFOCOM does not mandate them; treat them as a way to strengthen a released package, and confirm the current cycle's specifics (待核实).
- A public repository with an OSI-approved license and a one-screen README makes a released simulator far more credible than a bare tarball.
Degrees of reproducibility (state the one you achieved)
- Turnkey: one documented command re-runs the simulation and regenerates the key figures.
- Scripted: scripts exist but need documented manual steps or external trace access.
- Descriptive: the paper states assumptions, setup, and parameters precisely enough to rebuild.
For an analytical INFOCOM paper, descriptive plus a full proof is often the honest bar; for a simulation-heavy paper, aim scripted or turnkey so a reviewer's doubt about a number has a public answer.
Consistency and camera-ready pass
- Before submission: every scored number traces to a proof, a stated configuration, or a releasable script; released material (if any) is double-blind (no owner strings or identifying repo).
- Before camera-ready: if you release code/data, swap any anonymized link for a permanent, licensed, DOI-issuing archive, and make the paper's statements match it.
Output format
[Claim inventory] <claim -> proof | configuration | released script>
[Proof completeness] full / sketched-with-pointer / omitted-no-pointer
[Simulation provenance] <simulator+version / topology / seeds / runs / CIs present?>
[Release plan] none / code / data / both, with license and archive
[Reproducibility level] turnkey / scripted / descriptive, stated honestly
[Fixes] <paper additions + release additions before the deadline>© 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 INFOCOM-Skills/skills/infocom-reproducibility of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Infocom Reproducibility 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 |
|---|---|---|---|---|---|---|
| Infocom Reproducibility this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT | |
| CHARLS Paper Reproduction Guidexjtulyc/MedgeClaw | 617 | 1 repos | ~1.8k | Automated safety check: Pass | None | |
| Compute Environment Setupaipoch/open-science | 5.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Figure Styleaipoch/open-science | 5.5k | — | ~5.1k | Automated safety check: Pass | Apache-2.0 | |
| Add Bactopia Toolbactopia/bactopia | 522 | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
CHARLS Paper Reproduction Guide
xjtulyc/MedgeClaw
Guides an agent through reproducing papers built on the CHARLS health and retirement survey, from variable mapping to cognition, depression and isolation scores.
Compute Environment Setup
aipoch/open-science
Prepares setup instructions and a named activation file for a user-managed software environment on an Open-Science SSH or Slurm compute host.
Figure Style
aipoch/open-science
Publication-grade correctness and legibility rules for final-deliverable scientific figures, not exploratory plots.
Add Bactopia Tool
bactopia/bactopia
Scaffold a complete Bactopia Tool across all three tiers -- module, subworkflow, and workflow entry point under workflows/bactopia-tools/.
Modeling Code and Result Contracts
yushui2022/MathModel-Skill
Generates result-evidence contracts, tables and runnable q1 to q3 modeling code scaffolds for a math modeling paper from a model route, a data plan and cleaned data.
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 Infocom Reproducibility
What does Infocom Reproducibility do?
A skill your agent uses when strengthening IEEE INFOCOM reproducibility even though the venue runs no formal artifact-evaluation track, covering pinned simulator setups, released code and datasets…. Infocom Reproducibility is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when strengthening IEEE INFOCOM reproducibility even though the venue runs no formal artifact-evaluation track, covering pinned simulator setups, released code and datasets where possible, complete proofs and parameters within the page budget, IEEE reproducibility-badge options, and consistency between what the paper claims and what a reader could rebuild.
When should I use Infocom Reproducibility?
Infocom Reproducibility fits situations like: strengthening IEEE INFOCOM reproducibility even though the venue runs no formal artifact-evaluation track; covering pinned simulator setups; released code and datasets where possible; complete proofs and parameters within the page budget.
How do I install Infocom Reproducibility in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-reproducibility -a claude-code`. Or copy the skill folder (INFOCOM-Skills/skills/infocom-reproducibility in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/infocom-reproducibility in your project. Claude Code loads it when a task matches its description.
How do I install Infocom Reproducibility in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-reproducibility -a codex`. Or copy the skill folder (INFOCOM-Skills/skills/infocom-reproducibility in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/infocom-reproducibility in your project. Codex loads it when a task matches its description.
Can I use Infocom Reproducibility 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 infocom-reproducibility -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/infocom-reproducibility, .gemini/skills/infocom-reproducibility, .github/skills/infocom-reproducibility and .opencode/skills/infocom-reproducibility in your project.
What does Infocom Reproducibility need to run?
SKILL.md names no scripts, command-line tools or credentials: Infocom Reproducibility is instructions for the agent only.
Does Infocom Reproducibility 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 Infocom Reproducibility 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 Infocom Reproducibility use?
Infocom Reproducibility 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 Infocom Reproducibility use?
About 1.3k tokens (SKILL.md is roughly 5.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 Infocom Reproducibility?
Skills that share tags, products or a category with Infocom Reproducibility: Peer Review (K-Dense-AI/claude-scientific-writer, 2.4k stars), CHARLS Paper Reproduction Guide (xjtulyc/MedgeClaw, 617 stars), Compute Environment Setup (aipoch/open-science, 5.5k stars) and Figure Style (aipoch/open-science, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Infocom Reproducibility?
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.