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 an HPCA related-work section: sweeping the HPCA/ISCA/MICRO/ASPLOS record on dblp and IEEE Xplore, writing lineage paragraphs with structural deltas, blinding…
Install Hpca Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hpca-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/HPCA-Skills/skills/hpca-related-work .claude/skills/hpca-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 "hpca-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-related-work into .claude/skills/hpca-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-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/HPCA-Skills/skills/hpca-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 hpca-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hpca-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/HPCA-Skills/skills/hpca-related-work .agents/skills/hpca-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 "hpca-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-related-work into .agents/skills/hpca-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-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 hpca-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hpca-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/HPCA-Skills/skills/hpca-related-work .cursor/skills/hpca-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 "hpca-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-related-work into .cursor/skills/hpca-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-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 HPCA-Skills/skills/hpca-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 hpca-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hpca-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/HPCA-Skills/skills/hpca-related-work .gemini/skills/hpca-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 "hpca-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-related-work into .gemini/skills/hpca-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-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 hpca-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 hpca-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/HPCA-Skills/skills/hpca-related-work .github/skills/hpca-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 "hpca-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-related-work into .github/skills/hpca-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-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 hpca-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 hpca-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/HPCA-Skills/skills/hpca-related-work .opencode/skills/hpca-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 "hpca-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-related-work into .opencode/skills/hpca-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-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
hpca-related-work- GitHub stars
- 1.2k
- Token cost
- ~941 tokens
- SKILL.md length
- 410 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when building an HPCA related-work section: sweeping the HPCA/ISCA/MICRO/ASPLOS record on dblp and IEEE Xplore, writing lineage paragraphs with structural deltas, blinding…
- Building an HPCA related-work section: sweeping the HPCA/ISCA/MICRO/ASPLOS record on dblp and IEEE Xplore
- SKILL.md covers Sweep the whole architecture…, Write lineage, not a pile, Blind the voice, never the… and The concurrency and preprint…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Writing lineage paragraphs with structural deltas
What it does
Hpca Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when building an HPCA related-work section: sweeping the HPCA/ISCA/MICRO/ASPLOS record on dblp and IEEE Xplore, writing lineage paragraphs with structural deltas, blinding self-citations without touching the bibliography, and honoring the rule that every reference lists all its authors.
Its SKILL.md is about 940 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 Citation management and Literature review. 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 an HPCA related-work section: sweeping the HPCA/ISCA/MICRO/ASPLOS record on dblp and IEEE Xplore
- Writing lineage paragraphs with structural deltas
- Blinding self-citations without touching the bibliography
- Honoring the rule that every reference lists all its authors
Example prompts
- “/hpca-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
Hpca Related Work loads about 941 tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 410 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). 410 words, ~941 tokens.
Download SKILL.mdSave it as
.claude/skills/hpca-related-work/SKILL.md (or your agent's skills folder).- name
- hpca-related-work
- description
- Use when building an HPCA related-work section: sweeping the HPCA/ISCA/MICRO/ASPLOS record on dblp and IEEE Xplore, writing lineage paragraphs with structural deltas, blinding self-citations without touching the bibliography, and honoring the rule that every reference lists all its authors.
HPCA Related Work
Use this to position an HPCA paper against decades of computer-architecture literature. The bar is a related-work section that reads as a lineage with structural deltas, not a citation pile — and one that respects HPCA's two bibliography rules: references are never blinded, and every reference lists all of its authors.
Sweep the whole architecture record
Architecture ideas recur across four venues and forty years. Search the publisher-neutral spine (dblp) plus IEEE Xplore, not a single library:
- dblp HPCA series (
dblp.org/db/conf/hpca/) for the venue's own line, and the ISCA/MICRO/ASPLOS series for cross-venue lineage. - IEEE Xplore for HPCA's published volumes; ACM DL for the ACM-published siblings.
- The HPCA Test of Time Award list for the load-bearing ancestors of your subfield.
A mechanism you think is new often has a named ancestor at HPCA 2003 or ISCA 2006; find it before a reviewer does.
Write lineage, not a pile
Each related-work paragraph should name a prior line, then state the structural delta your paper adds — what changes in the machine or the mechanism, not just that you are "different." Group by mechanism family, not chronologically.
| Weak related-work move | Stronger HPCA move |
|---|---|
| "Many prefetchers exist [3,7,9,12]." | "History prefetchers [X] cover irregular patterns but issue regardless of bandwidth; we gate on measured utilization." |
| Listing venues and years | Naming the mechanism each prior work uses and where it breaks |
| Omitting a famous ancestor | Citing it and stating the concrete delta |
| Blinding your own prior work out | Citing it in the third person, un-blinded |
Show full SKILL.md (160 more words)Show less
Blind the voice, never the bibliography
Double-blind means the prose must not reveal you, but the references must stay intact:
- Cite your own prior work in the third person ("Prior work [12] proposed …"), never remove it.
- Do not anonymize, omit, or "et al."-abbreviate any reference — HPCA requires each reference to list all its authors, and a missing citation reads as either a gap or a blinding hack.
- Keep acknowledgments and funding out of the submitted version; they return at camera-ready.
The concurrency and preprint question
Recent HPCA guidance asks PC members not to hold arXiv or CAL preprints against a submission. Position honestly against concurrent work you know of, but do not use a preprint to claim priority in a way that de-anonymizes you. When a truly concurrent result exists, name the difference in scope rather than ignoring it.
Build sequence
1. dblp + IEEE Xplore sweep across HPCA/ISCA/MICRO/ASPLOS for the mechanism family
2. Pull the Test-of-Time ancestors of the subfield
3. Draft one paragraph per mechanism line, each ending in a structural delta
4. Blind self-citations to third person; confirm none were dropped
5. Verify every reference lists all authors (HPCA reject trigger otherwise)Output format
[Coverage] mechanism families cited / families that exist
[Lineage quality] deltas stated / paragraphs
[Missing ancestor risk] <named prior work not yet cited, or none>
[Blinding] self-cites third-person? bibliography intact? (Y/N)
[Author-list check] every reference lists all authors? (Y/N)
[Top gaps] <ordered>Reopen the current CFP for the preprint policy and the all-authors rule before finalizing — both are per-edition.
© 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 HPCA-Skills/skills/hpca-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Hpca 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 |
|---|---|---|---|---|---|---|
| Hpca Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~941 | 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 Hpca Related Work
What does Hpca Related Work do?
A skill your agent uses when building an HPCA related-work section: sweeping the HPCA/ISCA/MICRO/ASPLOS record on dblp and IEEE Xplore, writing lineage paragraphs with structural deltas, blinding…. Hpca Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when building an HPCA related-work section: sweeping the HPCA/ISCA/MICRO/ASPLOS record on dblp and IEEE Xplore, writing lineage paragraphs with structural deltas, blinding self-citations without touching the bibliography, and honoring the rule that every reference lists all its authors.
When should I use Hpca Related Work?
Hpca Related Work fits situations like: building an HPCA related-work section: sweeping the HPCA/ISCA/MICRO/ASPLOS record on dblp and IEEE Xplore; writing lineage paragraphs with structural deltas; blinding self-citations without touching the bibliography; honoring the rule that every reference lists all its authors.
How do I install Hpca Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-related-work -a claude-code`. Or copy the skill folder (HPCA-Skills/skills/hpca-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/hpca-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Hpca Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-related-work -a codex`. Or copy the skill folder (HPCA-Skills/skills/hpca-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/hpca-related-work in your project. Codex loads it when a task matches its description.
Can I use Hpca 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 hpca-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/hpca-related-work, .gemini/skills/hpca-related-work, .github/skills/hpca-related-work and .opencode/skills/hpca-related-work in your project.
What does Hpca Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Hpca Related Work is instructions for the agent only.
Does Hpca 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 Hpca 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 Hpca Related Work use?
Hpca 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 Hpca Related Work use?
About 941 tokens (SKILL.md is roughly 3.8k 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 Hpca Related Work?
Skills that share tags, products or a category with Hpca 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 Hpca 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.