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 IEEE ICSME submission against the software-maintenance and evolution literature across ICSME, SANER, MSR, ICPC, SCAM, ICSE/FSE, and the SE journals (TSE…
Install Icsme Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-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/ICSME-Skills/skills/icsme-related-work .claude/skills/icsme-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 "icsme-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-related-work into .claude/skills/icsme-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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/ICSME-Skills/skills/icsme-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 icsme-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-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/ICSME-Skills/skills/icsme-related-work .agents/skills/icsme-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 "icsme-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-related-work into .agents/skills/icsme-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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 icsme-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-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/ICSME-Skills/skills/icsme-related-work .cursor/skills/icsme-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 "icsme-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-related-work into .cursor/skills/icsme-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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 ICSME-Skills/skills/icsme-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 icsme-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-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/ICSME-Skills/skills/icsme-related-work .gemini/skills/icsme-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 "icsme-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-related-work into .gemini/skills/icsme-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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 icsme-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 icsme-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/ICSME-Skills/skills/icsme-related-work .github/skills/icsme-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 "icsme-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-related-work into .github/skills/icsme-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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 icsme-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 icsme-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/ICSME-Skills/skills/icsme-related-work .opencode/skills/icsme-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 "icsme-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-related-work into .opencode/skills/icsme-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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
icsme-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 467 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 IEEE ICSME submission against the software-maintenance and evolution literature across ICSME, SANER, MSR, ICPC, SCAM, ICSE/FSE, and the SE journals (TSE…
- Positioning an IEEE ICSME submission against the software-maintenance and evolution literature across ICSME
- SKILL.md covers Positioning checks, Maintenance literature lanes, Delta-first positioning vignette and Replication and prior-version…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The SE journals (TSE
What it does
Icsme Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an IEEE ICSME submission against the software-maintenance and evolution literature across ICSME, SANER, MSR, ICPC, SCAM, ICSE/FSE, and the SE journals (TSE, EMSE), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling replication overlap and prior-version eligibility.
Its SKILL.md is about 1.2k 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 IEEE ICSME submission against the software-maintenance and evolution literature across ICSME
- The SE journals (TSE
- Writing delta-first contrast rather than a citation catalog
- Keeping self-citations double-anonymous
Example prompts
- “/icsme-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
Icsme Related Work loads about 1.2k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 467 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). 467 words, ~1,235 tokens.
Download SKILL.mdSave it as
.claude/skills/icsme-related-work/SKILL.md (or your agent's skills folder).- name
- icsme-related-work
- description
- Use when positioning an IEEE ICSME submission against the software-maintenance and evolution literature across ICSME, SANER, MSR, ICPC, SCAM, ICSE/FSE, and the SE journals (TSE, EMSE), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling replication overlap and prior-version eligibility.
ICSME Related Work
Use this to audit novelty and eligibility. ICSME reviewers are close to the maintenance/evolution literature and expect to see where your paper sits relative to the nearest prior work — stated as a delta, not a list. Because the venue values replication (the RENE track) and rewards honest re-examination, "we redo prior work" is a legitimate contribution when framed as one — but it must engage the original explicitly. Reopen the current call for dual-submission, anonymity, and prior-publication rules before advising.
Positioning checks
- Separate the maintenance/evolution novelty from the engineering effort. What is new: a technique, an empirical finding about how software ages, a validated measurement of debt or comprehension, a recovered model, or an evidence regime nobody had covered?
- Cover the maintenance lanes. ICSME reviewers expect the evolution venues and journals, not just the papers nearest your method (see the table). A bibliography missing the obvious sibling work reads as unaware of the community.
- 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 double-anonymity. Cite your own prior maintenance studies in the third person and never link reviewers to an identity-revealing preprint, repository, or homepage.
- Declare overlap with any prior workshop/short version or a replicated original; for a RENE submission, name the exact study you reproduce.
Maintenance literature lanes
| Lane | Typical venues | What ICSME reviewers check |
|---|---|---|
| Maintenance & evolution core | ICSME, SANER, ICSM (historical) | Whether the nearest evolution technique/study is compared or distinguished |
| Mining software repositories | MSR | Whether prior mining work on your data/phenomenon is acknowledged |
| Comprehension & source analysis | ICPC, SCAM | Whether comprehension or analysis predecessors are credited |
| General-SE flagships | ICSE, ESEC/FSE | Whether the broad-SE technique/study you build on is engaged |
| SE journals | TSE, EMSE | Whether deeper journal-length maintenance studies are engaged |
A bibliography that cites only your own subarea tells a reviewer the delta may be smaller than claimed; one that reaches the evolution siblings and journals signals command of the field.
Show full SKILL.md (135 more words)Show less
Delta-first positioning vignette
Suppose the paper proposes a predictor of technical-debt hotspots plus a study. Its nearest neighbors: a foundational empirical study characterizing debt accumulation (no predictor), an MSR tool that mines debt-related commits (detection, not prediction), and a TSE study on debt repayment economics (scope, no method). The novelty sentence should name all three contrasts — prediction where the study offered characterization, forward-looking where the tool was retrospective, and a technique where the journal offered only economics.
Replication and prior-version judgment calls
[RENE replication] name the exact original study; state what you kept identical and what you
extended (new datasets, new systems); frame reproducibility as the contribution
[Concurrent arXiv work] cite neutrally, state the technical difference, avoid priority claims;
keep the citation double-anonymous
[Your workshop/SANER version] usually citable, but confirm against the current CFP and phrase so
anonymity survives; state what the full paper adds
[Prior short/NIER version] declare the overlap and state what the full study adds beyond it
[Archival status unclear] declare the overlap in the submission form rather than guessingEligibility red flags
- Substantial text overlap with a published paper by the same authors (self-plagiarism risk).
- A "new" study that re-reports a prior corpus's numbers without a new maintenance question — unless submitted to RENE and framed honestly as replication.
- Citations exclusively to non-maintenance venues, signaling a paper rerouted here without reframing.
Output format
[Eligibility] clear / needs declaration / risky
[Lanes covered] <maintenance-core / mining / comprehension-analysis / flagships / journals>
[Nearest 3 works] <work -> one-line delta>
[Replication framing] <n/a | RENE: original study named + what was extended>
[Novelty sentence] <ICSME-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 ICSME-Skills/skills/icsme-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icsme 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 |
|---|---|---|---|---|---|---|
| Icsme Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | 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 | |
| Jape Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~572 | Automated safety check: Pass | None | |
| Review PaperAperivue/medsci-skills | 333 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Joe Replication And Data Policyfranklee16/academic-research-skills | 223 | 1 repos | ~986 | Automated safety check: Pass | None |
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.
Jape Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when positioning a Journal of Applied Econometrics (JAE) manuscript against prior work — applied-econometrics precedent, the methods you apply, and JAE's own corpus and Data…
Review Paper
Aperivue/medsci-skills
A skill your agent uses when writing a literature review article (narrative, scoping PRISMA-ScR or systematic).
Joe Replication And Data Policy
franklee16/academic-research-skills
A skill your agent uses to prepare code and data materials for a Journal of Econometrics (JoE) submission under Elsevier's data-citation and availability norms, including reproducible Monte Carlo…
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…
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 Icsme Related Work
What does Icsme Related Work do?
A skill your agent uses when positioning an IEEE ICSME submission against the software-maintenance and evolution literature across ICSME, SANER, MSR, ICPC, SCAM, ICSE/FSE, and the SE journals (TSE…. Icsme Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an IEEE ICSME submission against the software-maintenance and evolution literature across ICSME, SANER, MSR, ICPC, SCAM, ICSE/FSE, and the SE journals (TSE, EMSE), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling replication overlap and prior-version eligibility.
When should I use Icsme Related Work?
Icsme Related Work fits situations like: positioning an IEEE ICSME submission against the software-maintenance and evolution literature across ICSME; the SE journals (TSE; writing delta-first contrast rather than a citation catalog; keeping self-citations double-anonymous.
How do I install Icsme Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-related-work -a claude-code`. Or copy the skill folder (ICSME-Skills/skills/icsme-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icsme-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Icsme Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-related-work -a codex`. Or copy the skill folder (ICSME-Skills/skills/icsme-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icsme-related-work in your project. Codex loads it when a task matches its description.
Can I use Icsme 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 icsme-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/icsme-related-work, .gemini/skills/icsme-related-work, .github/skills/icsme-related-work and .opencode/skills/icsme-related-work in your project.
What does Icsme Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Icsme Related Work is instructions for the agent only.
Does Icsme 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 Icsme 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 Icsme Related Work use?
Icsme 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 Icsme Related Work use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Icsme Related Work?
Skills that share tags, products or a category with Icsme Related Work: Ieee Paper Reader (CloudWave818/ieee-skills, 359 stars), Gec Literature Positioning (franklee16/academic-research-skills, 223 stars), Jape Literature Positioning (franklee16/academic-research-skills, 223 stars) and Review Paper (Aperivue/medsci-skills, 333 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icsme 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.