Ieee Paper Reader
CloudWave818/ieee-skills
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.
A skill your agent uses when positioning an ITCS paper against the theory literature — writing the delta that proves the model/question is genuinely new, covering the right STOC/FOCS/SODA/CCC/TCC…
Install Itcs Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-related-work --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-related-work .claude/skills/itcs-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-related-work into .claude/skills/itcs-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-related-work", 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-related-workType 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-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-related-work --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-related-work .agents/skills/itcs-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-related-work into .agents/skills/itcs-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-related-work", 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-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-related-work --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-related-work .cursor/skills/itcs-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-related-work into .cursor/skills/itcs-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-related-work", 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-related-work--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-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-related-work --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-related-work .gemini/skills/itcs-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-related-work into .gemini/skills/itcs-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-related-work", 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-related-workInstalls 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-related-work -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-related-work .github/skills/itcs-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-related-work into .github/skills/itcs-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-related-work", 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-related-work -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-related-work --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-related-work .opencode/skills/itcs-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-related-work into .opencode/skills/itcs-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-related-work", 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-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 720 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when positioning an ITCS paper against the theory literature — writing the delta that proves the model/question is genuinely new, covering the right STOC/FOCS/SODA/CCC/TCC…
- Positioning an ITCS paper against the theory literature — writing the delta that proves the model/question is genuinely new
- SKILL.md covers Delta-first positioning, Cover the right lanes, Honesty under lightweight… and Positioning the novelty claim…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the right STOC/FOCS/SODA/CCC/TCC lanes
What it does
Itcs Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an ITCS paper against the theory literature — writing the delta that proves the model/question is genuinely new, covering the right STOC/FOCS/SODA/CCC/TCC lanes, and staying honest under lightweight double-blind where the reference list is not anonymized.
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 Literature review, Citation management and Positioning and messaging. 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
- Positioning an ITCS paper against the theory literature — writing the delta that proves the model/question is genuinely new
- Covering the right STOC/FOCS/SODA/CCC/TCC lanes
- Staying honest under lightweight double-blind where the reference list is not anonymized
Example prompts
- “/itcs-related-work”
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 Related Work loads about 1.4k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 720 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). 720 words, ~1,414 tokens.
Download SKILL.mdSave it as
.claude/skills/itcs-related-work/SKILL.md (or your agent's skills folder).- name
- itcs-related-work
- description
- Use when positioning an ITCS paper against the theory literature — writing the delta that proves the model/question is genuinely new, covering the right STOC/FOCS/SODA/CCC/TCC lanes, and staying honest under lightweight double-blind where the reference list is not anonymized.
ITCS Related Work
At ITCS, related work carries a heavier burden than at a depth venue: since conceptual novelty is the selection criterion, your positioning must prove the contribution is genuinely new, not merely stronger. A reviewer's most damaging finding is not "someone proved a better bound" — it is "someone already asked this question" or "this is a known model under a new name." The related-work discussion is where you win or lose the novelty claim, so it is a load-bearing part of an ITCS paper, not an obligatory appendix.
Delta-first positioning
Lead each comparison with the delta, not the citation:
- Name the closest prior model or question, state what it did, and then state precisely what it did not ask that you do. "Prior work bounds the prover's computation; none bounds its memory of the interaction" is a delta. "Many works study interactive proofs [3-19]" is a dump.
- Distinguish new question from new answer. If the question existed and you answer it
better, say so honestly — and reconsider whether ITCS is the right venue (see
itcs-topic-selection); if the question is new, make that the headline of the paragraph. - Address independent and concurrent work plainly. In a small community with heavy arXiv/ECCC posting, a near-simultaneous related idea is common; acknowledging it and drawing the distinction reads as strength, not weakness.
Cover the right lanes
An ITCS paper usually sits at a seam between areas, so its related work must reach across lanes a single-area reader might miss:
| Lane | Typical venues to survey | Why it matters at ITCS |
|---|---|---|
| Your core area's depth work | STOC, FOCS, the specialist venue (CCC/SODA/TCC) | Shows you know the hard results your idea sits near |
| The other area you connect to | wherever that field publishes | An ITCS bridge is only novel if both banks are cited |
| Prior models/definitions near yours | ITCS/ICS back-catalog, journals | This is where "already asked" hides — search it hardest |
| Folklore and surveys | monographs, lecture notes, Dagstuhl reports | New questions are often "known folklore"; pre-empt that charge |
Scan the ITCS/ICS back-catalog (dblp conf/innovations, LIPIcs volumes) specifically: because
ITCS is where new models are introduced, the venue most likely to already contain your idea is
ITCS itself.
Show full SKILL.md (359 more words)Show less
Honesty under lightweight double-blind
ITCS review is lightweight double-blind: the PDF hides author names, affiliations, and emails, but the reference list is NOT anonymized, and authors are encouraged to post a non-anonymous full version to arXiv/ECCC/ePrint. Practical consequences for related work:
- Cite your own prior work normally in the third person. Do not anonymize references or write "[removed for anonymity]." Refer to your own earlier papers as "[Author, YEAR] shows..." the way you would cite anyone — the reference stays in the list, the prose stays neutral.
- Do not write "in our previous work [12] we..." — that first-person self-reference is the
classic leak the anonymity sweep must catch (see
itcs-submission). - Do not sabotage coverage to hide identity. Omitting the obviously-relevant paper by your own group to avoid a tell is worse than the tell: reviewers notice the gap, and it damages the novelty case. Cite it neutrally.
Positioning the novelty claim itself
Make the newness checkable, the way the rest of the paper makes theorems checkable:
- State the novelty claim explicitly ("to our knowledge, no prior work models X as Y") rather than implying it — an explicit claim is one a reviewer can confirm or refute, which is the honest posture.
- Bound the claim. "New, to our knowledge, in the unconditional setting" is safer and more credible than a blanket "first ever."
- Credit the lineage. Showing your idea descends from a recognizable line ("this extends the non-malleability philosophy to ...") makes it legible and generous without weakening the delta.
Common failure modes
| Symptom | Why it fails at ITCS | Fix |
|---|---|---|
| Citation dump with no deltas | Does not prove novelty, the selection axis | Lead each comparison with what prior work did not ask |
| Missed the closest prior model | "Already asked" — fatal to a novelty paper | Search the ITCS/ICS back-catalog hardest |
| Anonymized/removed references | Violates the not-anonymized reference rule | Cite normally in the third person |
| "In our prior work [12] we..." | Anonymity leak under lightweight double-blind | Rewrite as a neutral third-person citation |
| Blanket "first ever" claim | One counterexample sinks it | Bound the claim to a precise setting |
| Only your own area cited | An ITCS bridge needs both banks | Survey the connected area too |
Output format
[ITCS positioning status] novelty-proven / at-risk / unclear
[Closest prior model] <named> ; delta: <what they did NOT ask that you do>
[Back-catalog check] searched ITCS/ICS + connected area for a prior version? yes/no
[Novelty claim] stated explicitly and bounded to a setting? yes/no
[Anonymity] references un-anonymized; no first-person self-cites? yes/no
[Fix queue] <ordered edits>© 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-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Itcs Related Work 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 Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Ieee Paper ReaderCloudWave818/ieee-skills | 359 | — | ~591 | Automated safety check: Pass | MIT | |
| Gec Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~855 | Automated safety check: Pass | None | |
| Jpe Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
Gec Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when positioning a Global Environmental Change (GEC) manuscript against the relevant literatures.
Jpe Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when writing or repairing the introduction and related-work framing for a Journal of Political Economy (JPE) manuscript — situating the contribution in the economics…
Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
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 Itcs Related Work
What does Itcs Related Work do?
A skill your agent uses when positioning an ITCS paper against the theory literature — writing the delta that proves the model/question is genuinely new, covering the right STOC/FOCS/SODA/CCC/TCC…. Itcs Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an ITCS paper against the theory literature — writing the delta that proves the model/question is genuinely new, covering the right STOC/FOCS/SODA/CCC/TCC lanes, and staying honest under lightweight double-blind where the reference list is not anonymized.
When should I use Itcs Related Work?
Itcs Related Work fits situations like: positioning an ITCS paper against the theory literature — writing the delta that proves the model/question is genuinely new; covering the right STOC/FOCS/SODA/CCC/TCC lanes; staying honest under lightweight double-blind where the reference list is not anonymized.
How do I install Itcs Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-related-work -a claude-code`. Or copy the skill folder (ITCS-Skills/skills/itcs-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/itcs-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Itcs Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-related-work -a codex`. Or copy the skill folder (ITCS-Skills/skills/itcs-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/itcs-related-work in your project. Codex loads it when a task matches its description.
Can I use Itcs Related Work 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-related-work -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-related-work, .gemini/skills/itcs-related-work, .github/skills/itcs-related-work and .opencode/skills/itcs-related-work in your project.
What does Itcs Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Itcs Related Work is instructions for the agent only.
Does Itcs Related Work 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 Related Work 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 Related Work use?
Itcs Related Work 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 Related Work 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 Related Work?
Skills that share tags, products or a category with Itcs Related Work: Ieee Paper Reader (CloudWave818/ieee-skills, 359 stars), Gec Literature Positioning (franklee16/academic-research-skills, 223 stars), Jpe Literature Positioning (franklee16/academic-research-skills, 223 stars) and Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Itcs Related Work?
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.