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 a MICRO paper's related-work coverage and positioning — sweeping the four-venue architecture literature plus journals and industry disclosures, differentiating…
Install Micro Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-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/MICRO-Skills/skills/micro-related-work .claude/skills/micro-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 "micro-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-related-work into .claude/skills/micro-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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/MICRO-Skills/skills/micro-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 micro-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-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/MICRO-Skills/skills/micro-related-work .agents/skills/micro-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 "micro-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-related-work into .agents/skills/micro-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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 micro-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-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/MICRO-Skills/skills/micro-related-work .cursor/skills/micro-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 "micro-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-related-work into .cursor/skills/micro-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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 MICRO-Skills/skills/micro-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 micro-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills micro-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/MICRO-Skills/skills/micro-related-work .gemini/skills/micro-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 "micro-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-related-work into .gemini/skills/micro-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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 micro-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 micro-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/MICRO-Skills/skills/micro-related-work .github/skills/micro-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 "micro-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-related-work into .github/skills/micro-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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 micro-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 micro-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/MICRO-Skills/skills/micro-related-work .opencode/skills/micro-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 "micro-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MICRO-Skills/skills/micro-related-work into .opencode/skills/micro-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "micro-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
micro-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 815 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when building a MICRO paper's related-work coverage and positioning — sweeping the four-venue architecture literature plus journals and industry disclosures, differentiating…
- Works in 4 steps: Open with a two-sentence taxonomy of the… → Spend one structural-difference sentence… → Group the rest by lane with clustered… → …
- Differentiating by mechanism structure and cost rather than by numbers
- SKILL.md covers The five lanes to sweep, Differentiate on structure and…, Venue attribution: verify… and Handling your own preprints…, plus 4 more sections
- Calls curl and python3; reaches dblp.org
What it does
Micro Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when building a MICRO paper's related-work coverage and positioning — sweeping the four-venue architecture literature plus journals and industry disclosures, differentiating by mechanism structure and cost rather than by numbers, obeying MICRO's all-author citation format, and verifying venue attribution via dblp before citing.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Literature review and Citation management. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Differentiating by mechanism structure and cost rather than by numbers
- Obeying MICROs all-author citation format
- Verifying venue attribution via dblp before citing
Example prompts
- “/micro-related-work”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Open with a two-sentence taxonomy of the mechanism space (the axes along which
- Spend one structural-difference sentence on each of the 3–5 nearest neighbors.
- Group the rest by lane with clustered citations — ten grouped citations cost
- Close by naming which neighbors appear in the evaluation and why the others
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
Shell commands in SKILL.md call:
curlpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
dblp.org
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
Micro Related Work loads about 1.8k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 815 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). 815 words, ~1,757 tokens.
Download SKILL.mdSave it as
.claude/skills/micro-related-work/SKILL.md (or your agent's skills folder).- name
- micro-related-work
- description
- Use when building a MICRO paper's related-work coverage and positioning — sweeping the four-venue architecture literature plus journals and industry disclosures, differentiating by mechanism structure and cost rather than by numbers, obeying MICRO's all-author citation format, and verifying venue attribution via dblp before citing.
MICRO Related Work
At MICRO the related-work section is a mechanism taxonomy, not a bibliography tour. Reviewers — who probably wrote some of the cited papers — check three things: did you find the nearest mechanisms, do you know how yours differs structurally, and did you compare against the right one in the evaluation.
The five lanes to sweep
| Lane | Where it lives | What reviewers check |
|---|---|---|
| Direct ancestors of your mechanism | MICRO/ISCA/HPCA/ASPLOS, last ~5 years first, then classics | The named predecessor is in your evaluation, reimplemented (micro-experiments) |
| Same problem, different layer | ASPLOS, OSDI/SOSP, PLDI (software attacks on your bottleneck) | You explain why hardware is still warranted |
| Modeling & methodology you rely on | MICRO/ISCA tool papers (e.g., CACTI @ MICRO 2007, McPAT @ MICRO 2009), TACO/CAL journals | Versions cited match versions used |
| Industry disclosures | Hot Chips talks, ISSCC papers, patents, vendor optimization manuals | A shipped equivalent of your idea would be fatal to novelty — find it before reviewers do |
| Workload/characterization studies | IISWC, SIGMETRICS, arch venues | Your motivating characterization is consistent with published behavior |
The industry lane is MICRO-distinctive: commercial cores have shipped sophisticated predictors and prefetchers for decades, often documented only in patents and manuals. "Novel versus academia, present in Zen/M-series silicon" is a real review outcome; a sentence acknowledging and differentiating from disclosed industrial practice inoculates against it.
Differentiate on structure and cost, not adjectives
Weak: "Unlike prior work, our approach is more efficient and scalable." Strong, MICRO-shaped: "Both X [12] and our design track reuse at cache-line grain; X spends 68KB on per-core tables and trains on evictions, while we piggyback on existing replacement metadata (3.2KB) and train on fills, which is why we survive the shared-LLC configs where X thrashes (Fig. 8)."
The pattern: shared premise → structural difference → cost difference → consequence shown in your own evaluation. Every "nearest neighbor" paper deserves one such sentence; the merely-adjacent get grouped citations.
Venue attribution: verify before you cite
Architecture's four venues publish look-alike work; misattributing a classic is a credibility wound with expert reviewers. Verify on dblp (or the ACM DL / IEEE Xplore record) — MICRO's proceedings are split across both libraries, which makes guessing extra unreliable:
# dblp API: confirm venue + year + pages before the entry goes in the .bib
curl -s "https://dblp.org/search/publ/api?q=utility-based+cache+partitioning&format=json" \
| python3 -c "import json,sys; hits=json.load(sys.stdin)['result']['hits']['hit']; \
[print(h['info'].get('venue'), h['info'].get('year'), h['info'].get('title')) for h in hits]"
# expect: MICRO 2006 — not ISCA, not HPCAClassics that live at MICRO (dblp/ACM-DL verified 2026-07-08, see
resources/exemplars/library.md): two-level branch prediction (MICRO 1991),
utility-based cache partitioning (MICRO 2006), CACTI 6.0 (MICRO 2007), McPAT
(MICRO 2009), DaDianNao (MICRO 2014). Rowhammer and Wattch, by contrast, are ISCA
papers — the standard misattribution traps in this space.
Handling your own preprints and prior papers
- Your published prior mechanism is cited in third person and, if it is the nearest neighbor, compared in the evaluation like anyone else's — reviewers notice a suspicious gap where the obvious predecessor comparison should be.
- Your own arXiv preprint of this submission: current-cycle policy on preprint coexistence with double-blind review is 待核实 on the live guidelines; do not cite it, and do not structure the paper so that finding it is necessary to evaluate the work.
- Extended-abstract or workshop versions (e.g., an IISWC characterization that seeded this mechanism): cite in third person, and be prepared to explain the delta in rebuttal if a reviewer connects them.
Show full SKILL.md (307 more words)Show less
Format and anonymity constraints on the section
- MICRO's reference format requires every author named in every entry — no "et al." — and reference pages are unlimited, so breadth costs no content space. There is no page-pressure excuse for a thin section.
- Double-blind: cite your own prior mechanisms in third person, and make the comparison genuine — an oddly gentle treatment of one citation is a de-anonymizing tell.
- Concurrent-work etiquette for the overlapping April/June cycles (how to treat a just-appeared ISCA paper): current-cycle policy 待核实; the safe default is to cite and position, since reviewers sit on both PCs and will know it exists.
Timing the sweep
Run the literature sweep twice: once at project start (it shapes the mechanism — finding the nearest neighbor early is cheaper than in review), and once in the final month before the April deadline, because the November ISCA and February HPCA programs land new neighbors mid-project. The second sweep is diff-only: new papers in the five lanes since the first pass, each triaged to cite, differentiate, or reimplement-and-compare.
Building the section under MICRO's page economics
Because references are unlimited but content pages are scarce and appendix-free, the winning structure is dense prose, broad bibliography:
- Open with a two-sentence taxonomy of the mechanism space (the axes along which designs differ — training signal, storage grain, commitment point).
- Spend one structural-difference sentence on each of the 3–5 nearest neighbors.
- Group the rest by lane with clustered citations — ten grouped citations cost two lines of body text and zero content-page pressure.
- Close by naming which neighbors appear in the evaluation and why the others cannot (different simulator assumptions, unavailable parameters) — preempting the "why didn't you compare against [23]?" review.
Keep a positioning.md in the artifact repo mapping each neighbor to its delta
sentence and its evaluation status; rebuttal season reuses it verbatim.
Output format
[Lane coverage] ancestors / other-layer / tools / industry / workloads: N citations each
[Nearest neighbors] <papers> — structural-difference sentence written: yes/no each
[Eval linkage] neighbors reimplemented in evaluation: list vs excuses
[Industry check] patents/manuals/HotChips swept for shipped equivalents: yes / no
[Attribution] all classics dblp-verified: yes / unverified list
[Format] all-author entries confirmed / et-al violations: N© 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 MICRO-Skills/skills/micro-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Micro 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 |
|---|---|---|---|---|---|---|
| Micro Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | 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 Micro Related Work
What does Micro Related Work do?
A skill your agent uses when building a MICRO paper's related-work coverage and positioning — sweeping the four-venue architecture literature plus journals and industry disclosures, differentiating…. Micro Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when building a MICRO paper's related-work coverage and positioning — sweeping the four-venue architecture literature plus journals and industry disclosures, differentiating by mechanism structure and cost rather than by numbers, obeying MICRO's all-author citation format, and verifying venue attribution via dblp before citing.
When should I use Micro Related Work?
Micro Related Work fits situations like: differentiating by mechanism structure and cost rather than by numbers; obeying MICROs all-author citation format; verifying venue attribution via dblp before citing.
How do I install Micro Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-related-work -a claude-code`. Or copy the skill folder (MICRO-Skills/skills/micro-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/micro-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Micro Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-related-work -a codex`. Or copy the skill folder (MICRO-Skills/skills/micro-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/micro-related-work in your project. Codex loads it when a task matches its description.
Can I use Micro 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 micro-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/micro-related-work, .gemini/skills/micro-related-work, .github/skills/micro-related-work and .opencode/skills/micro-related-work in your project.
What does Micro Related Work need to run?
Going by SKILL.md and its folder, Micro Related Work needs the command-line tools its instructions call (curl and python3). Our summary lists: Python 3.
Does Micro Related Work access the network?
SKILL.md names 1 domain. In commands or code: dblp.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Micro 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 Micro Related Work use?
Micro 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 Micro Related Work use?
About 1.8k tokens (SKILL.md is roughly 7k 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 Micro Related Work?
Skills that share tags, products or a category with Micro 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 Micro 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.