Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
A skill your agent uses when positioning an ESEC/FSE submission against the software-engineering literature across ICSE, FSE, ASE, ISSTA, MSR, and the SE journals (EMSE, TSE, TOSEM), writing…
Install Fse Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-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/FSE-Skills/skills/fse-related-work .claude/skills/fse-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 "fse-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-related-work into .claude/skills/fse-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-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/FSE-Skills/skills/fse-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 fse-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-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/FSE-Skills/skills/fse-related-work .agents/skills/fse-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 "fse-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-related-work into .agents/skills/fse-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-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 fse-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-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/FSE-Skills/skills/fse-related-work .cursor/skills/fse-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 "fse-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-related-work into .cursor/skills/fse-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-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 FSE-Skills/skills/fse-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 fse-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fse-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/FSE-Skills/skills/fse-related-work .gemini/skills/fse-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 "fse-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-related-work into .gemini/skills/fse-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-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 fse-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 fse-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/FSE-Skills/skills/fse-related-work .github/skills/fse-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 "fse-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-related-work into .github/skills/fse-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-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 fse-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 fse-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/FSE-Skills/skills/fse-related-work .opencode/skills/fse-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 "fse-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FSE-Skills/skills/fse-related-work into .opencode/skills/fse-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fse-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
fse-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 419 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 ESEC/FSE submission against the software-engineering literature across ICSE, FSE, ASE, ISSTA, MSR, and the SE journals (EMSE, TSE, TOSEM), writing…
- Positioning an ESEC/FSE submission against the software-engineering literature across ICSE
- SKILL.md covers Positioning checks, SE literature lanes, Delta-first positioning vignette and Concurrent and prior-version…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The SE journals (EMSE
What it does
Fse Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an ESEC/FSE submission against the software-engineering literature across ICSE, FSE, ASE, ISSTA, MSR, and the SE journals (EMSE, TSE, TOSEM), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling concurrent, preprint, and prior-version overlap.
Its SKILL.md is about 1.1k 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 Academic paper search. 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 ESEC/FSE submission against the software-engineering literature across ICSE
- The SE journals (EMSE
- Writing delta-first contrast rather than a citation catalog
- Keeping self-citations double-anonymous
Example prompts
- “/fse-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
Fse Related Work loads about 1.1k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 419 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). 419 words, ~1,076 tokens.
Download SKILL.mdSave it as
.claude/skills/fse-related-work/SKILL.md (or your agent's skills folder).- name
- fse-related-work
- description
- Use when positioning an ESEC/FSE submission against the software-engineering literature across ICSE, FSE, ASE, ISSTA, MSR, and the SE journals (EMSE, TSE, TOSEM), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling concurrent, preprint, and prior-version overlap.
FSE Related Work
Use this to audit novelty and eligibility. FSE reviewers are close to the SE literature and expect to see where your paper sits relative to the nearest prior work — stated as a delta, not a list. Reopen the current call for dual-submission, anonymity, and prior-publication rules before advising authors.
Positioning checks
- Separate the software-engineering novelty from the engineering effort. What is new: a technique, an empirical finding, a validated measurement, a design, or an evidence regime nobody had covered?
- Cover the SE lanes. FSE reviewers expect the flagship venues and the journals, not just the papers nearest your method (see the table). A bibliography missing the obvious sibling work reads as unaware.
- Write delta-first. Each closely related paper gets one sentence naming what it did and one naming what you do differently — not a summary. Position, don't catalog.
- Preserve heavy double-anonymity. Cite your own prior work in the third person and never link reviewers to an identity-revealing preprint, repository, or homepage.
- Declare overlap with any prior conference/workshop version or concurrent submission; do not re-submit archival work as new.
SE literature lanes
| Lane | Typical venues | What FSE reviewers check |
|---|---|---|
| General-SE flagships | ICSE, ESEC/FSE | Whether the nearest broad-SE technique/study is compared or distinguished |
| Automation & analysis | ASE, ISSTA | Whether tool-centric or testing/analysis predecessors are credited |
| Mining & evolution | MSR, ICSME | Whether prior empirical/mining work on your data is acknowledged |
| SE journals | EMSE, TSE, TOSEM | Whether deeper journal-length studies on the topic are engaged |
| Adjacent fields (when relevant) | PL, HCI, ML venues | Whether borrowed methods are cited to their real origin |
A bibliography that cites only your own subarea tells a reviewer the delta may be smaller than claimed; one that reaches the sibling flagships and journals signals command of the field.
Show full SKILL.md (129 more words)Show less
Delta-first positioning vignette
Suppose the paper proposes a flaky-test classifier and an accompanying study. Its nearest neighbors: the foundational flaky-tests empirical study (characterization, no predictor), an ASE tool that reruns tests to detect flakiness (dynamic, expensive), and a journal study on flaky-test prevalence (scope, no method). The novelty sentence should name all three contrasts — prediction where the study offered only characterization, a static filter where the tool required reruns, and a technique where the journal offered only prevalence.
Concurrent and prior-version judgment calls
[Concurrent arXiv work] cite neutrally, state the technical difference, avoid unverifiable
priority claims; keep the citation double-anonymous
[Your workshop version] usually non-archival and citable, but confirm against the current CFP
wording and phrase so anonymity survives
[Prior short/NIER version] declare the overlap and state what the full paper adds beyond it
[Archival status unclear] declare the overlap in the submission form rather than guessing a
chair's interpretationEligibility red flags
- Substantial text overlap with a published paper by the same authors (self-plagiarism risk).
- A "new" study that re-reports a prior dataset's numbers without a new question.
- Citations exclusively to non-SE venues, signaling the paper may be a visitor rerouted without reframing.
Output format
[Eligibility] clear / needs declaration / risky
[Lanes covered] <flagships / automation-analysis / mining-evolution / journals / adjacent>
[Nearest 3 works] <work -> one-line delta>
[Archival-overlap risk] <none / declare: what>
[Novelty sentence] <FSE-ready contribution contrast against the nearest prior work>© 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 FSE-Skills/skills/fse-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Fse 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 |
|---|---|---|---|---|---|---|
| Fse Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| 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 | |
| Systematic Literature Review Builderbytedance/deer-flow | 84k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Paper Research on arXivXiaomiMiMo/MiMo-Code | 14k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Literature Review AgentAr9av/PaperOrchestra | 679 | 1 repos | ~5.2k | Automated safety check: Pass | Custom licence |
Similar skills
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.
Systematic Literature Review Builder
bytedance/deer-flow
Searches arXiv across many papers on one topic, extracts each paper's methodology and findings in parallel, and synthesizes a cited literature review.
Paper Research on arXiv
XiaomiMiMo/MiMo-Code
Searches arXiv, fetches metadata, generates BibTeX, downloads PDFs and finds citations and related papers using a bundled Python script.
Literature Review Agent
Ar9av/PaperOrchestra
Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). An agent skill from Ar9av/PaperOrchestra.
Autonomous Research
federicodeponte/opendraft
An 18-agent pipeline that turns one topic line into a drafted research paper, literature review, or thesis chapter.
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 Fse Related Work
What does Fse Related Work do?
A skill your agent uses when positioning an ESEC/FSE submission against the software-engineering literature across ICSE, FSE, ASE, ISSTA, MSR, and the SE journals (EMSE, TSE, TOSEM), writing…. Fse Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an ESEC/FSE submission against the software-engineering literature across ICSE, FSE, ASE, ISSTA, MSR, and the SE journals (EMSE, TSE, TOSEM), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling concurrent, preprint, and prior-version overlap.
When should I use Fse Related Work?
Fse Related Work fits situations like: positioning an ESEC/FSE submission against the software-engineering literature across ICSE; the SE journals (EMSE; writing delta-first contrast rather than a citation catalog; keeping self-citations double-anonymous.
How do I install Fse Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-related-work -a claude-code`. Or copy the skill folder (FSE-Skills/skills/fse-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/fse-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Fse Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fse-related-work -a codex`. Or copy the skill folder (FSE-Skills/skills/fse-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/fse-related-work in your project. Codex loads it when a task matches its description.
Can I use Fse 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 fse-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/fse-related-work, .gemini/skills/fse-related-work, .github/skills/fse-related-work and .opencode/skills/fse-related-work in your project.
What does Fse Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Fse Related Work is instructions for the agent only.
Does Fse 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 Fse 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 Fse Related Work use?
Fse 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 Fse Related Work use?
About 1.1k tokens (SKILL.md is roughly 4.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 Fse Related Work?
Skills that share tags, products or a category with Fse Related Work: Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Preprint Search on bioRxiv (LigphiDonk/Oh-my--paper, 739 stars), Systematic Literature Review Builder (bytedance/deer-flow, 84k stars) and Paper Research on arXiv (XiaomiMiMo/MiMo-Code, 14k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fse 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.