Ieee Paper Reader
CloudWave818/ieee-skills
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.
A skill your agent uses when writing the related-work and positioning of an ASE (IEEE/ACM Automated Software Engineering) paper, covering the automated-SE literature lanes, delta-first positioning…
Install Ase Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ase-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/ASE-Skills/skills/ase-related-work .claude/skills/ase-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 "ase-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASE-Skills/skills/ase-related-work into .claude/skills/ase-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ase-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/ASE-Skills/skills/ase-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 ase-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ase-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/ASE-Skills/skills/ase-related-work .agents/skills/ase-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 "ase-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASE-Skills/skills/ase-related-work into .agents/skills/ase-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ase-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 ase-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ase-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/ASE-Skills/skills/ase-related-work .cursor/skills/ase-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 "ase-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASE-Skills/skills/ase-related-work into .cursor/skills/ase-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ase-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 ASE-Skills/skills/ase-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 ase-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ase-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/ASE-Skills/skills/ase-related-work .gemini/skills/ase-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 "ase-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASE-Skills/skills/ase-related-work into .gemini/skills/ase-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ase-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 ase-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 ase-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/ASE-Skills/skills/ase-related-work .github/skills/ase-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 "ase-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASE-Skills/skills/ase-related-work into .github/skills/ase-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ase-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 ase-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 ase-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/ASE-Skills/skills/ase-related-work .opencode/skills/ase-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 "ase-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASE-Skills/skills/ase-related-work into .opencode/skills/ase-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ase-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
ase-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 411 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing the related-work and positioning of an ASE (IEEE/ACM Automated Software Engineering) paper, covering the automated-SE literature lanes, delta-first positioning…
- Writing the related-work and positioning of an ASE (IEEE/ACM Automated Software Engineering) paper
- SKILL.md covers Cover the ASE literature lanes, Delta-first positioning, Fair head-to-head framing (the… and Distinguish ASE from…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the automated-SE literature lanes
What it does
Ase Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing the related-work and positioning of an ASE (IEEE/ACM Automated Software Engineering) paper, covering the automated-SE literature lanes, delta-first positioning against prior tools/techniques, fair head-to-head framing, and double-anonymous self-citation.
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, Positioning and messaging 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
- Writing the related-work and positioning of an ASE (IEEE/ACM Automated Software Engineering) paper
- Covering the automated-SE literature lanes
- Delta-first positioning against prior tools/techniques
- Fair head-to-head framing
Example prompts
- “/ase-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
Ase Related Work loads about 1.1k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 411 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). 411 words, ~1,117 tokens.
Download SKILL.mdSave it as
.claude/skills/ase-related-work/SKILL.md (or your agent's skills folder).- name
- ase-related-work
- description
- Use when writing the related-work and positioning of an ASE (IEEE/ACM Automated Software Engineering) paper, covering the automated-SE literature lanes, delta-first positioning against prior tools/techniques, fair head-to-head framing, and double-anonymous self-citation.
ASE Related Work
Position the paper against prior automation, not against a topic. At ASE the question a reviewer holds is "what does this tool/technique do that the existing automated approaches do not?" — so related work is a delta argument, and the strongest deltas are stated against named, runnable prior tools you can (and often must) compare against empirically.
Cover the ASE literature lanes
An automated-SE paper usually sits at the intersection of several lanes; name your position in each that applies:
- Program analysis — static/dynamic analysis, symbolic/concolic execution, abstract interpretation, invariant inference.
- Test generation and testing — search-based, specification-based, fuzzing, regression and flaky-test handling.
- Fault localization, debugging, and repair — spectrum-based localization, automated program repair, patch synthesis.
- Synthesis and recommendation — program/code synthesis, API recommendation, refactoring automation.
- Comprehension and documentation — summarization, code search, clone and change analysis.
- Learning-based / AI4SE — learned code representations, models applied to SE tasks, LLM-based automation — and SE4AI, applying SE automation to ML systems.
Delta-first positioning
Write each related-work cluster as: prior automation X does A; it cannot do B because C; we do B. Then, where B is comparable, compare against X empirically — ASE reviewers expect a head-to-head against the closest runnable baseline, not just a prose distinction.
[Cluster] spectrum-based fault localization
Prior: ranks statements by suspiciousness from pass/fail spectra.
Gap: assumes a fixed test suite; degrades when tests are flaky.
Delta: our technique estimates and corrects for flakiness before ranking.
Evidence of delta: head-to-head on the same faulty subjects, §5.2, Table 3.Fair head-to-head framing (the ASE credibility test)
- Compare against the strongest, most recent automated baseline you can run, at an equal, documented budget (time, iterations, tuning). An under-configured baseline is the classic soundness objection and a Revision criterion waiting to happen.
- If a baseline tool cannot run on your subjects, say why explicitly and choose the nearest viable alternative — do not quietly omit the obvious competitor.
- Distinguish reimplementation from the original tool, and note version/commit — reviewers who built the baseline will check.
Show full SKILL.md (130 more words)Show less
Distinguish ASE from sibling-venue prior work
Because automated-SE ideas appear across venues, position precisely: a testing-theory result may live at ISSTA, a broad empirical study at FSE, a language mechanism at a PL venue. When you cite across venues, make the ASE delta — the automation you add — explicit, so a reviewer does not read your contribution as a reheated sibling-venue result.
Double-anonymous self-citation
- Cite your own prior tools and papers in the third person ("Prior work by [Anonymous] proposed ...", or neutrally "The X tool [12] ...") so the citation does not deanonymize you.
- Do not write "our earlier tool" or link to a repository whose owner is you.
- Keep the count of self-citations honest; a cluster of third-person citations to one hidden group is itself a leak.
Coverage checks
[Recency] at least the last 2-3 years of ASE/ICSE/FSE/ISSTA automation in your subarea cited?
[Closest baseline] is the single most similar runnable tool named AND compared, not just cited?
[Cross-venue] PL/ML/testing neighbors positioned so your automation delta is explicit?
[Anonymity] every self-citation in the third person; no repository ownership revealed?
[Honesty] any obvious competitor conspicuously missing? (a reviewer will notice)Output format
[Lanes] which automated-SE lanes the paper touches
[Delta table] prior tool -> what it does -> gap -> your delta -> where the head-to-head lives
[Baseline fairness] closest runnable baseline named, version pinned, equal budget?
[Anonymity check] self-citations third-person, no repo owner revealed© 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 ASE-Skills/skills/ase-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ase 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 |
|---|---|---|---|---|---|---|
| Ase Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | 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 Ase Related Work
What does Ase Related Work do?
A skill your agent uses when writing the related-work and positioning of an ASE (IEEE/ACM Automated Software Engineering) paper, covering the automated-SE literature lanes, delta-first positioning…. Ase Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing the related-work and positioning of an ASE (IEEE/ACM Automated Software Engineering) paper, covering the automated-SE literature lanes, delta-first positioning against prior tools/techniques, fair head-to-head framing, and double-anonymous self-citation.
When should I use Ase Related Work?
Ase Related Work fits situations like: writing the related-work and positioning of an ASE (IEEE/ACM Automated Software Engineering) paper; covering the automated-SE literature lanes; delta-first positioning against prior tools/techniques; fair head-to-head framing.
How do I install Ase Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-related-work -a claude-code`. Or copy the skill folder (ASE-Skills/skills/ase-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ase-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Ase Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ase-related-work -a codex`. Or copy the skill folder (ASE-Skills/skills/ase-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ase-related-work in your project. Codex loads it when a task matches its description.
Can I use Ase 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 ase-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/ase-related-work, .gemini/skills/ase-related-work, .github/skills/ase-related-work and .opencode/skills/ase-related-work in your project.
What does Ase Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Ase Related Work is instructions for the agent only.
Does Ase 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 Ase 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 Ase Related Work use?
Ase 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 Ase Related Work use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 Ase Related Work?
Skills that share tags, products or a category with Ase 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 Ase 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.