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.
A skill your agent uses when building the related-work and positioning sections of an ICSE research-track paper, covering the literature lanes SE reviewers check, searching ACM DL, IEEE Xplore and…
Install Icse Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-related-work .claude/skills/icse-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 "icse-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-related-work into .claude/skills/icse-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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/ICSE-Skills/skills/icse-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 icse-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-related-work .agents/skills/icse-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 "icse-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-related-work into .agents/skills/icse-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-related-work .cursor/skills/icse-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 "icse-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-related-work into .cursor/skills/icse-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 ICSE-Skills/skills/icse-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 icse-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-related-work .gemini/skills/icse-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 "icse-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-related-work into .gemini/skills/icse-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-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 icse-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/ICSE-Skills/skills/icse-related-work .github/skills/icse-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 "icse-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-related-work into .github/skills/icse-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-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 icse-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/ICSE-Skills/skills/icse-related-work .opencode/skills/icse-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 "icse-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-related-work into .opencode/skills/icse-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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
icse-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 616 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when building the related-work and positioning sections of an ICSE research-track paper, covering the literature lanes SE reviewers check, searching ACM DL, IEEE Xplore and…
- Building the related-work and positioning sections of an ICSE research-track paper
- SKILL.md covers The five lanes an SE reviewer…, Currency in fast lanes, Writing the section as an… and Double-anonymous self-citation, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the literature lanes SE reviewers check
What it does
Icse Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when building the related-work and positioning sections of an ICSE research-track paper, covering the literature lanes SE reviewers check, searching ACM DL, IEEE Xplore and dblp across the flagship venues, staying current in fast-moving areas like LLM4SE, and keeping self-citations double-anonymous.
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 and Citation management. 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
- Building the related-work and positioning sections of an ICSE research-track paper
- Covering the literature lanes SE reviewers check
- Searching ACM DL
- IEEE Xplore and dblp across the flagship venues
Example prompts
- “/icse-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 (its code samples are markdown).
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
Icse Related Work loads about 1.4k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 616 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). 616 words, ~1,388 tokens.
Download SKILL.mdSave it as
.claude/skills/icse-related-work/SKILL.md (or your agent's skills folder).- name
- icse-related-work
- description
- Use when building the related-work and positioning sections of an ICSE research-track paper, covering the literature lanes SE reviewers check, searching ACM DL, IEEE Xplore and dblp across the flagship venues, staying current in fast-moving areas like LLM4SE, and keeping self-citations double-anonymous.
ICSE Related Work
Positioning at ICSE is scored twice: once under novelty ("sufficiently original with respect to the state-of-the-art", per the 2027 criteria read 2026-07-08) and once implicitly when the assigned reviewers — likely authors of the nearest prior work — check whether they and their neighbors are represented fairly. Cover the lanes below before writing a word of the section.
The five lanes an SE reviewer sweeps
| Lane | Where it lives | What missing it costs you |
|---|---|---|
| Flagship conference line | ICSE, FSE, ASE, ISSTA proceedings (ACM DL / IEEE Xplore) | The direct-competitor omission — often the reviewer's own paper |
| Journal line | TSE, TOSEM, EMSE | Mature versions of "your" idea; journals often published it first |
| Specialized venue line | MSR, ICSME, ICPC, SANER, RE, SPLC, ESEM per subfield | Reviewers from that subcommunity notice instantly |
| Preprint line | arXiv cs.SE (critical in LLM4SE, AI-for-SE) | Staleness: in fast lanes, six months of preprints can contain your contribution |
| Adjacent-field line | PL (PLDI/OOPSLA), systems, ML, HCI as relevant | Reinvention accusations from cross-listed reviewers |
Search all three indexes — ACM Digital Library, IEEE Xplore, and dblp — because ICSE's own proceedings historically alternate between publishers and no single index has everything; dblp is the neutral spine for coverage checking, the DLs for full text.
Currency in fast lanes
LLM4SE and AI-for-SE turn over in months. For a June 30 submission, run a final sweep in the last two weeks: new arXiv postings, the just-published ICSE/FSE proceedings, and the accepted-papers lists that venues post before official publication. Concurrent work (public after your study was designed) deserves acknowledgment, not competition: cite it, mark it concurrent, and do not contort your evaluation to beat a paper that appeared last month — reviewers understand timelines and respect the candor.
Writing the section as an argument
The section's job is a delta statement, not a bibliography. Organize by the dimensions on which you differ, then place each cluster:
## Related Work (delta-first pattern)
**Test-suite-based repair.** [Cluster: GenProg lineage, semantics-based
repair.] These validate candidate patches against the failing suite; all
inherit test-suite overfitting. *We differ:* our oracle is X, so overfitting
of type Y cannot occur by construction (§4).
**LLM-based patch generation.** [Cluster: 2023–2026 line, incl. concurrent
work.] These generate candidates but keep suite-based validation. *We
differ:* evaluation on post-training-cutoff bugs (§5.2) removes the
contamination confound these papers share.
**Empirical studies of overfitting.** [Studies motivating the problem.]
We *build on* their measurement protocol and extend it to Z.Every cluster paragraph ends with the difference stated in your paper's own technical terms, with a section pointer. If a cluster ends with "...has also studied this area", it is filler.
Show full SKILL.md (277 more words)Show less
Double-anonymous self-citation
ICSE reviews double-anonymously, and prior-work references must be third person: "Prior work introduced FOO [12]" rather than "In our earlier paper [12]". The subtle leaks: citing an unpublished technical report only your group could know, an artifact URL from your prior paper's repository, and a tool name unique to your lab used without citation. If the current paper extends your own published tool, cite it in third person and phrase the relationship symmetrically ("extends FOO [12] by...") — reviewers may guess, but the text must not confirm.
The nearest-neighbor rehearsal
Before freezing the section, run one simulation: pick the three papers a PC chair would most plausibly assign as reviewer expertise matches — usually the three you compare against in the evaluation — and reread your section as each of those authors. For each, answer: is my paper described accurately (not straw-manned)? is the difference stated in terms I would accept? is my most recent relevant paper present, or only my old one? A misdescribed neighbor produces the angriest review in the packet, and it is entirely preventable at the cost of an hour.
Verification discipline for the bibliography
- Every citation checked against dblp or the DL record — titles, venues, years drift when copied from other papers' bibliographies or generated by models; a hallucinated reference discovered by a reviewer poisons trust in everything else.
- Cite the archival version over the preprint when both exist; keep arXiv IDs for preprint-only work.
- Distinguish venue tiers honestly: a workshop paper and an ICSE paper by the same authors are different maturity claims.
- Normalize venue naming (e.g., ESEC/FSE vs FSE across years) so reviewers recognize the venues at a glance.
Output format
[Lane coverage] five lanes -> swept on <date> / gap
[Delta table] nearest neighbors -> difference in our terms -> section pointer
[Currency] last sweep date; concurrent-work items flagged
[Anonymity] self-citation phrasing audit: violations found/fixed
[Bibliography hygiene] unverified entries remaining (must be zero)© 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 ICSE-Skills/skills/icse-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icse 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 |
|---|---|---|---|---|---|---|
| Icse Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| 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 | |
| Preprint Search on bioRxivLigphiDonk/Oh-my--paper | 739 | 12 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Deep Research WorkflowTokenRhythm/opensquilla | 7.1k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
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.
Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Deep Research Workflow
TokenRhythm/opensquilla
Runs multi-round research in three stages with a persisted state file, evidence tracking and a long-form report with per-claim citations.
Academic Research Suite for Codex
Imbad0202/academic-research-skills-codex
A router skill that sends academic work such as literature reviews, drafting, citation checks, peer review and revision to the right workflow in the ARS suite.
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 Icse Related Work
What does Icse Related Work do?
A skill your agent uses when building the related-work and positioning sections of an ICSE research-track paper, covering the literature lanes SE reviewers check, searching ACM DL, IEEE Xplore and…. Icse Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when building the related-work and positioning sections of an ICSE research-track paper, covering the literature lanes SE reviewers check, searching ACM DL, IEEE Xplore and dblp across the flagship venues, staying current in fast-moving areas like LLM4SE, and keeping self-citations double-anonymous.
When should I use Icse Related Work?
Icse Related Work fits situations like: building the related-work and positioning sections of an ICSE research-track paper; covering the literature lanes SE reviewers check; searching ACM DL; IEEE Xplore and dblp across the flagship venues.
How do I install Icse Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-related-work -a claude-code`. Or copy the skill folder (ICSE-Skills/skills/icse-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icse-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Icse Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-related-work -a codex`. Or copy the skill folder (ICSE-Skills/skills/icse-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icse-related-work in your project. Codex loads it when a task matches its description.
Can I use Icse 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 icse-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/icse-related-work, .gemini/skills/icse-related-work, .github/skills/icse-related-work and .opencode/skills/icse-related-work in your project.
What does Icse Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Icse Related Work is instructions for the agent only.
Does Icse 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 Icse 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 Icse Related Work use?
Icse 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 Icse Related Work use?
About 1.4k tokens (SKILL.md is roughly 5.6k 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 Icse Related Work?
Skills that share tags, products or a category with Icse Related Work: Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars), Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Preprint Search on bioRxiv (LigphiDonk/Oh-my--paper, 739 stars) and Academic Paper Writing Pipeline (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 Icse 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.