Literature Review
K-Dense-AI/scientific-agent-skills
Runs systematic, scoping or narrative literature reviews across PubMed, arXiv, bioRxiv and Semantic Scholar, with citation checks and Markdown or PDF output.
A skill your agent uses to make an ITCS paper's mathematics independently checkable — complete proofs of every central claim, self-contained definitions, pinned dependencies on prior results, and a…
Install Itcs Reproducibility
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-reproducibility -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-reproducibility .claude/skills/itcs-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 "itcs-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-reproducibility into .claude/skills/itcs-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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/ITCS-Skills/skills/itcs-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 itcs-reproducibility -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-reproducibility .agents/skills/itcs-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 "itcs-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-reproducibility into .agents/skills/itcs-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 itcs-reproducibility -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-reproducibility .cursor/skills/itcs-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 "itcs-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-reproducibility into .cursor/skills/itcs-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 ITCS-Skills/skills/itcs-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 itcs-reproducibility -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-reproducibility .gemini/skills/itcs-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 "itcs-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-reproducibility into .gemini/skills/itcs-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 itcs-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 itcs-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/ITCS-Skills/skills/itcs-reproducibility .github/skills/itcs-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 "itcs-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-reproducibility into .github/skills/itcs-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 itcs-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 itcs-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/ITCS-Skills/skills/itcs-reproducibility .opencode/skills/itcs-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 "itcs-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-reproducibility into .opencode/skills/itcs-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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
itcs-reproducibility- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 633 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses to make an ITCS paper's mathematics independently checkable — complete proofs of every central claim, self-contained definitions, pinned dependencies on prior results, and a…
- Make an ITCS papers mathematics independently checkable — complete proofs of every central claim
- SKILL.md covers Completeness: every central…, Self-containment: definitions…, Dependency provenance: pin… and The full version as the…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Self-contained definitions
What it does
Itcs Reproducibility is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to make an ITCS paper's mathematics independently checkable — complete proofs of every central claim, self-contained definitions, pinned dependencies on prior results, and a matching full version on arXiv/ECCC/ePrint — the pure-theory analogue of a reproducibility package.
Its SKILL.md is about 1.4k 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 and Academic paper search. It works with arXiv. 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
- Make an ITCS papers mathematics independently checkable — complete proofs of every central claim
- Self-contained definitions
- Pinned dependencies on prior results
- A matching full version on arXiv/ECCC/ePrint — the pure-theory analogue of a reproducibility package
Example prompts
- “/itcs-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
Itcs Reproducibility loads about 1.4k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 633 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). 633 words, ~1,426 tokens.
Download SKILL.mdSave it as
.claude/skills/itcs-reproducibility/SKILL.md (or your agent's skills folder).- name
- itcs-reproducibility
- description
- Use to make an ITCS paper's mathematics independently checkable — complete proofs of every central claim, self-contained definitions, pinned dependencies on prior results, and a matching full version on arXiv/ECCC/ePrint — the pure-theory analogue of a reproducibility package.
ITCS Reproducibility
"Reproducibility" at a pure-theory venue means one thing: a competent, skeptical reader can verify every central claim from the paper alone. There is no code to rerun and no dataset to re-mine — the analogue of a reproducibility package is a complete, self-contained, correctly attributed proof. ITCS makes this concrete in its call: submissions must include complete proofs of all central claims (in an appendix if needed). This skill is the discipline that makes the mathematics checkable, which — since ITCS has no rebuttal — is also your only defense against a reviewer who gets stuck.
Completeness: every central claim is fully proved
- No "proof omitted," no "proof is standard," no "see the full version" for anything a reviewer must check to believe the result. Deferring a routine calculation to an appendix is fine; deferring the load-bearing lemma is a reproducibility failure and, at ITCS, a likely reject.
- Distinguish proved from assumed. Every step is either proved here or cited to a precise prior result. A theorem that quietly relies on an unproved claim is the theory analogue of a package that silently calls a missing dependency.
- Prove the anchoring result in full. For a new-model paper, the separation/possibility result that shows the model is alive is exactly what a reviewer will try hardest to break — give it the most complete treatment in the paper.
Self-containment: definitions and notation
- Define every symbol and model parameter before use. A reviewer should verify a theorem
statement without opening your prior papers — which lightweight double-blind would expose
anyway (see
itcs-related-work). - State the exact model, not "the usual one." Small variations in a definition (adaptive vs. non-adaptive, worst-case vs. average, the quantifier order) change what is true; pin them down.
- Restate borrowed results you rely on. Quote the precise statement (and its hypotheses) of an external theorem you invoke, so a reviewer sees exactly what you assume and can check the fit.
Dependency provenance: pin what you borrow
The theory analogue of "pinning versions" is precise citation of the results you build on:
- Cite each borrowed theorem to a specific venue, year, and statement number — not a vague "it is known that."
- Flag any dependency on a recent, unrefereed, or conditional result (an arXiv/ECCC preprint, a conjecture, an unpublished personal communication). A result standing on an unverified preprint should say so; its correctness is then explicitly conditional.
- Separate assumptions (P != NP, a hardness assumption, a conjecture) from theorems, and make every conditional result's hypothesis unmissable in its statement.
Show full SKILL.md (220 more words)Show less
The full version as the durable record
Under lightweight double-blind, authors are encouraged to post the full version to arXiv, ECCC, or the IACR ePrint Archive. Treat it as the permanent, complete record:
- The full version and the submission must agree. Divergent theorem statements or proofs between the two invite a reviewer to trust the wrong one. Keep them in sync, and say in the submission that a full version exists.
- Put genuinely long proofs in the full version and an appendix the PC can read — a proof a
reviewer must consult to judge the paper cannot live only in an external preprint they are not
obligated to open (see
itcs-supplementary). - Keep the preprint's identity handling consistent with your strategy — posting is allowed and common, but the submitted PDF still omits author names.
The checkability passes (run before upload)
[Completeness] every central claim has a full proof present (appendix ok)? no "omitted"/"standard"?
[Self-contain] every symbol/model/parameter defined before use? theorem statements parseable alone?
[Dependencies] each borrowed result cited to venue+year+statement number? unrefereed deps flagged?
[Assumptions] every conditional theorem states its hypothesis in the statement?
[Consistency] abstract bound = theorem bound = proof bound; quantifier order uniform?
[Full version] submission and arXiv/ECCC/ePrint version agree? existence noted?Common failure modes
| Symptom | Why it fails at ITCS | Fix |
|---|---|---|
| Central lemma "proof omitted" | Violates the complete-proofs requirement | Include the full proof (appendix) |
| Theorem parseable only with your prior paper | Not self-contained; anonymity risk too | Define everything in-paper |
| "It is known that ..." with no cite | Dependency unpinned; reviewer cannot check | Cite venue/year/statement |
| Relies on a preprint silently | Correctness is conditional but hidden | State the conditional dependency |
| Preprint proof differs from submission | Reviewer trusts the wrong version | Sync the two |
Output format
[ITCS checkability status] verifiable / gaps
[Completeness] central claims fully proved (list any "omitted")
[Self-containment] definitions complete? statements parseable alone? yes/no
[Dependencies] borrowed results pinned? unrefereed/conditional ones flagged? yes/no
[Full version] posted and consistent with submission? yes/no
[Fix queue] <ordered, load-bearing gaps first>© 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 ITCS-Skills/skills/itcs-reproducibility of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Itcs 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 |
|---|---|---|---|---|---|---|
| Itcs Reproducibility this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Literature ReviewK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Literature Search Methodologyaiming-lab/AutoResearchClaw | 15k | — | ~709 | Automated safety check: Pass | MIT | |
| Paper LensYSQ-boop/paper-lens | 101 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Read arXiv Paperkarpathy/nanochat | 59k | 1 repos | ~494 | Automated safety check: Pass | MIT | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
Literature Search Methodology
aiming-lab/AutoResearchClaw
Lays out a systematic literature review method: PICO-based search strategy, inclusion criteria, PRISMA screening, quality assessment tools and synthesis approaches.
Paper Lens
YSQ-boop/paper-lens
Read and critically analyze one academic paper from an arXiv URL/ID or a local PDF, producing a source-grounded Markdown report that can grow from a quick read into a reviewer-level deep review.
Read arXiv Paper
karpathy/nanochat
Fetches the TeX source of an arXiv paper from its URL, reads it and writes a markdown summary tied to the nanochat project.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Openalex Database
neflibata-feng/MyArxiv-Agent
Query and analyze scholarly literature using the OpenAlex database.
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
Works with
Categories
Questions about Itcs Reproducibility
What does Itcs Reproducibility do?
A skill your agent uses to make an ITCS paper's mathematics independently checkable — complete proofs of every central claim, self-contained definitions, pinned dependencies on prior results, and a…. Itcs Reproducibility is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to make an ITCS paper's mathematics independently checkable — complete proofs of every central claim, self-contained definitions, pinned dependencies on prior results, and a matching full version on arXiv/ECCC/ePrint — the pure-theory analogue of a reproducibility package.
When should I use Itcs Reproducibility?
Itcs Reproducibility fits situations like: make an ITCS papers mathematics independently checkable — complete proofs of every central claim; self-contained definitions; pinned dependencies on prior results; A matching full version on arXiv/ECCC/ePrint — the pure-theory analogue of a reproducibility package.
How do I install Itcs Reproducibility in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-reproducibility -a claude-code`. Or copy the skill folder (ITCS-Skills/skills/itcs-reproducibility in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/itcs-reproducibility in your project. Claude Code loads it when a task matches its description.
How do I install Itcs Reproducibility in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-reproducibility -a codex`. Or copy the skill folder (ITCS-Skills/skills/itcs-reproducibility in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/itcs-reproducibility in your project. Codex loads it when a task matches its description.
Can I use Itcs 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 itcs-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/itcs-reproducibility, .gemini/skills/itcs-reproducibility, .github/skills/itcs-reproducibility and .opencode/skills/itcs-reproducibility in your project.
What does Itcs Reproducibility need to run?
SKILL.md names no scripts, command-line tools or credentials: Itcs Reproducibility is instructions for the agent only.
Does Itcs 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 Itcs 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 Itcs Reproducibility use?
Itcs 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 Itcs Reproducibility use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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 Itcs Reproducibility?
Skills that share tags, products or a category with Itcs Reproducibility: Literature Review (K-Dense-AI/scientific-agent-skills, 48k stars), Literature Search Methodology (aiming-lab/AutoResearchClaw, 15k stars), Paper Lens (YSQ-boop/paper-lens, 101 stars) and Read arXiv Paper (karpathy/nanochat, 59k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Itcs Reproducibility?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.