Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
A skill your agent uses when positioning a CIKM submission against three literatures at once — retrieval, mining, and knowledge management/databases — building the boundary-work paragraph, guarding…
Install Cikm Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-related-work .claude/skills/cikm-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 "cikm-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-related-work into .claude/skills/cikm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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/CIKM-Skills/skills/cikm-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 cikm-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-related-work .agents/skills/cikm-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 "cikm-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-related-work into .agents/skills/cikm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 cikm-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-related-work .cursor/skills/cikm-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 "cikm-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-related-work into .cursor/skills/cikm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 CIKM-Skills/skills/cikm-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 cikm-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cikm-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/CIKM-Skills/skills/cikm-related-work .gemini/skills/cikm-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 "cikm-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-related-work into .gemini/skills/cikm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 cikm-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 cikm-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/CIKM-Skills/skills/cikm-related-work .github/skills/cikm-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 "cikm-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-related-work into .github/skills/cikm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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 cikm-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 cikm-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/CIKM-Skills/skills/cikm-related-work .opencode/skills/cikm-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 "cikm-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CIKM-Skills/skills/cikm-related-work into .opencode/skills/cikm-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cikm-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
cikm-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 845 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when positioning a CIKM submission against three literatures at once — retrieval, mining, and knowledge management/databases — building the boundary-work paragraph, guarding…
- Positioning a CIKM submission against three literatures at once — retrieval
- SKILL.md covers Three-front coverage plan, The boundary-work paragraph, Misattribution guard and Recency expectations by front, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Knowledge management/databases — building the boundary-work paragraph
What it does
Cikm Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a CIKM submission against three literatures at once — retrieval, mining, and knowledge management/databases — building the boundary-work paragraph, guarding against misattributing SIGIR/KDD/ICDM classics to CIKM, and handling preprints under the arXiv-declaration and dual-submission rules.
Its SKILL.md is about 1.7k 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 Academic paper search and Literature review. It works with arXiv. 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 a CIKM submission against three literatures at once — retrieval
- Knowledge management/databases — building the boundary-work paragraph
- Guarding against misattributing SIGIR/KDD/ICDM classics to CIKM
- Handling preprints under the arXiv-declaration and dual-submission rules
Example prompts
- “/cikm-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
Cikm Related Work loads about 1.7k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 845 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). 845 words, ~1,704 tokens.
Download SKILL.mdSave it as
.claude/skills/cikm-related-work/SKILL.md (or your agent's skills folder).- name
- cikm-related-work
- description
- Use when positioning a CIKM submission against three literatures at once — retrieval, mining, and knowledge management/databases — building the boundary-work paragraph, guarding against misattributing SIGIR/KDD/ICDM classics to CIKM, and handling preprints under the arXiv-declaration and dual-submission rules.
CIKM Related Work
Related work at CIKM is a three-front obligation. A submission claiming the IR-mining-KM boundary must show command of each literature it borrows from, plus the smaller literature that lives on the boundary — much of which is CIKM's own back catalog. A section citing only one lane tells two-thirds of the reviewer pool that their field's relevant results may be unknown to the authors.
Three-front coverage plan
| Front | Lineage to command | What its reviewer checks |
|---|---|---|
| Retrieval | Ranking models, neural matching (DRMM-line), evaluation practice | Is the nearest ranking method compared or distinguished? |
| Mining | Representation learning (GraRep-line), graph/sequence models, scale methods | Is the mechanism's delta over the nearest mining method stated? |
| KM / databases | Entity linking (TAGME-line), integration, KG construction and quality | Is the data-management cost and lineage acknowledged? |
The verified exemplars in ../../resources/exemplars/library.md mark where these
lineages pass through CIKM itself; citing the venue's own milestones — DSSM for
click-supervised semantic matching, RippleNet/BERT4Rec for KG- and
transformer-based recommendation — signals to the panel that the authors know whose
house they are submitting to.
The boundary-work paragraph
After the three lane surveys, CIKM related-work sections need one paragraph the single-lane venues do not: the works that already tried to combine the same lanes. Structure it as three sentences — who combined what ("X fused KG signals into ranking..."), what they could not do ("...but only for static graphs at million-triple scale"), what this paper changes at the seam ("we make the fusion incremental, which is what deployment requires"). Reviewers use exactly this paragraph to locate the contribution; write it so it can be quoted in a meta-review.
Misattribution guard
CIKM sits so close to its siblings that venue misattribution is a live review risk — and a credibility hit when a reviewer authored the misplaced paper. Checked traps (dblp-verified, 2026-07-08):
- DeepWalk, node2vec, metapath2vec → KDD, not CIKM; CIKM's graph-embedding milestone is GraRep (CIKM 2015).
- SASRec → ICDM 2018; the transformer-recommender at CIKM is BERT4Rec (CIKM 2019).
- NGCF and LightGCN → SIGIR (2019/2020); CIKM's KG-recommendation landmark is RippleNet (CIKM 2018).
- Conv-KNRM → WSDM 2018, while DRMM → CIKM 2016; the neural-IR lineage hops venues paper by paper.
- TransE → NeurIPS 2013 — KG-embedding origins are not CIKM even though KG applications are core CIKM territory.
Rule: before writing "(CIKM 20xx)", confirm on dblp's conf/cikm index; before
writing "prior CIKM work has not...", search the last three CIKM proceedings in the
ACM DL — with many hundreds of papers per recent edition, the prior work usually
exists.
Recency expectations by front
The three fronts age at different speeds, and reviewers calibrate accordingly. A workable recency floor when drafting:
| Front | Staleness signal reviewers flag | Floor |
|---|---|---|
| Neural retrieval / RAG-adjacent | No baseline or citation from the last ~18 months | Current-year and previous-year venue papers present |
| Graph/sequence mining | Comparing only against pre-transformer-era methods | At least one recent strong method compared, not just cited |
| KM / KG construction | Ignoring the current ecosystem (modern KG tooling, LLM-assisted curation) | Ecosystem named, position stated |
| Foundations | — | Foundational citations never go stale; DSSM-era work still anchors lineages |
Recency is about baselines even more than bibliography: citing a recent method
while comparing only against old ones is the version of staleness that costs
scores (cikm-experiments owns that half of the problem).
Show full SKILL.md (321 more words)Show less
Citation hygiene mechanics
- Cite the published venue version once it exists — the CIKM/SIGIR/KDD record, not the arXiv preprint the PDF happened to be downloaded from. dblp resolves this in seconds and the ACM reference format carries the DOI.
- Keep bibliography entries consistent in format; a references section mixing five citation styles reads as assembled-by-paste, and at CIKM the references are uncounted — there is no budget excuse for truncated entries.
- When a line of work spans venues (the neural-matching lineage deliberately does), cite the actual hops rather than attributing the whole line to one venue — the misattribution guard above exists because reviewers notice.
Preprints, concurrency, and the declaration rule
CIKM 2026 bans concurrent submission outright and requires declaring any public
non-anonymized version on the EasyChair form (cikm-submission). In the related-work
text itself: cite your own preprint in third person like a stranger's work; cite
independent concurrent arXiv work neutrally with a technical contrast and no
priority argument; and never let a citation resolve the authors' identity (e.g., a
footnoted repository URL owned by an author).
Auditing the novelty sentence
The contribution statement should survive this adversarial read: for each clause, name the closest prior work that could claim the same clause, and state the surviving difference in mechanism terms, not adjective terms.
Draft: "We are the first to use knowledge graphs for enterprise search."
Audit: KG-for-search has a decade of work (the RippleNet-line alone applies KG propagation to ranking-adjacent tasks); "first" fails on contact. Repaired: "Prior KG-augmented retrieval assumes a static graph resolved at index time; we resolve links at query time against a continuously edited graph, which no prior system in this line supports." The repaired sentence names the lineage, concedes its existence, and stakes a mechanism-level difference a reviewer can verify rather than a primacy claim they can falsify with one citation — the only kind of novelty sentence that is safe in front of a pool this broad.
Output format
[Front coverage] retrieval / mining / KM-DB — each surveyed with nearest work named
[Boundary paragraph] <who-combined-what → gap → this paper's seam move>
[CIKM back-catalog] <own-venue milestones cited where they exist>
[Misattribution scan] <every "(CIKM 20xx)" dblp-checked; sibling classics placed right>
[Declaration state] <own preprints third-person, form declaration consistent>© 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 CIKM-Skills/skills/cikm-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Cikm 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 |
|---|---|---|---|---|---|---|
| Cikm Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Systematic Literature Review Builderbytedance/deer-flow | 84k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Paper Research on arXivXiaomiMiMo/MiMo-Code | 14k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Literature Review AgentAr9av/PaperOrchestra | 679 | 1 repos | ~5.2k | Automated safety check: Pass | Custom licence | |
| Arxiv MCP Serverblazickjp/arxiv-mcp-server | 3.2k | — | ~353 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Systematic Literature Review Builder
bytedance/deer-flow
Searches arXiv across many papers on one topic, extracts each paper's methodology and findings in parallel, and synthesizes a cited literature review.
Paper Research on arXiv
XiaomiMiMo/MiMo-Code
Searches arXiv, fetches metadata, generates BibTeX, downloads PDFs and finds citations and related papers using a bundled Python script.
Literature Review Agent
Ar9av/PaperOrchestra
Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). An agent skill from Ar9av/PaperOrchestra.
Arxiv MCP Server
blazickjp/arxiv-mcp-server
A skill your agent uses when finding, comparing, reading, or monitoring arXiv papers, including requests for abstracts, citation graphs, original LaTeX, section-level technical details, or…
Arxiv Paper Writer
appautomaton/latex-arxiv-SKILL
Write LaTeX ML/AI review articles for arXiv using the IEEEtran template and verified BibTeX citations.
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
Works with
Categories
Questions about Cikm Related Work
What does Cikm Related Work do?
A skill your agent uses when positioning a CIKM submission against three literatures at once — retrieval, mining, and knowledge management/databases — building the boundary-work paragraph, guarding…. Cikm Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a CIKM submission against three literatures at once — retrieval, mining, and knowledge management/databases — building the boundary-work paragraph, guarding against misattributing SIGIR/KDD/ICDM classics to CIKM, and handling preprints under the arXiv-declaration and dual-submission rules.
When should I use Cikm Related Work?
Cikm Related Work fits situations like: positioning a CIKM submission against three literatures at once — retrieval; knowledge management/databases — building the boundary-work paragraph; guarding against misattributing SIGIR/KDD/ICDM classics to CIKM; handling preprints under the arXiv-declaration and dual-submission rules.
How do I install Cikm Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-related-work -a claude-code`. Or copy the skill folder (CIKM-Skills/skills/cikm-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cikm-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Cikm Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cikm-related-work -a codex`. Or copy the skill folder (CIKM-Skills/skills/cikm-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cikm-related-work in your project. Codex loads it when a task matches its description.
Can I use Cikm 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 cikm-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/cikm-related-work, .gemini/skills/cikm-related-work, .github/skills/cikm-related-work and .opencode/skills/cikm-related-work in your project.
What does Cikm Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Cikm Related Work is instructions for the agent only.
Does Cikm 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 Cikm 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 Cikm Related Work use?
Cikm 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 Cikm Related Work use?
About 1.7k tokens (SKILL.md is roughly 6.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 Cikm Related Work?
Skills that share tags, products or a category with Cikm Related Work: Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Systematic Literature Review Builder (bytedance/deer-flow, 84k stars), Paper Research on arXiv (XiaomiMiMo/MiMo-Code, 14k stars) and Literature Review Agent (Ar9av/PaperOrchestra, 679 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cikm 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.