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 the related-work section of an ACM CHI paper — covering the HCI venue family and the non-CS disciplines CHI draws on, positioning against the last few CHI…
Install Chi Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-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/CHI-Skills/skills/chi-related-work .claude/skills/chi-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 "chi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-related-work into .claude/skills/chi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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/CHI-Skills/skills/chi-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 chi-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-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/CHI-Skills/skills/chi-related-work .agents/skills/chi-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 "chi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-related-work into .agents/skills/chi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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 chi-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-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/CHI-Skills/skills/chi-related-work .cursor/skills/chi-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 "chi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-related-work into .cursor/skills/chi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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 CHI-Skills/skills/chi-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 chi-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-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/CHI-Skills/skills/chi-related-work .gemini/skills/chi-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 "chi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-related-work into .gemini/skills/chi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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 chi-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 chi-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/CHI-Skills/skills/chi-related-work .github/skills/chi-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 "chi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-related-work into .github/skills/chi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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 chi-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 chi-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/CHI-Skills/skills/chi-related-work .opencode/skills/chi-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 "chi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-related-work into .opencode/skills/chi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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
chi-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 602 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when building the related-work section of an ACM CHI paper — covering the HCI venue family and the non-CS disciplines CHI draws on, positioning against the last few CHI…
- Building the related-work section of an ACM CHI paper — covering the HCI venue family and the non-CS disciplines CHI draws on
- SKILL.md covers Five lanes, all checked, Position, don't inventory, Searching the field properly and Distinguishing near-neighbors…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Positioning against the last few CHI cycles
What it does
Chi Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when building the related-work section of an ACM CHI paper — covering the HCI venue family and the non-CS disciplines CHI draws on, positioning against the last few CHI cycles, keeping self-citation anonymous — in a venue where insufficient contextualization is the top assisted desk-reject ground.
Its SKILL.md is about 1.4k 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
- Building the related-work section of an ACM CHI paper — covering the HCI venue family and the non-CS disciplines CHI draws on
- Positioning against the last few CHI cycles
- Keeping self-citation anonymous — in a venue where insufficient contextualization is the top assisted desk-reject ground
Example prompts
- “/chi-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
Chi Related Work loads about 1.4k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 602 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). 602 words, ~1,441 tokens.
Download SKILL.mdSave it as
.claude/skills/chi-related-work/SKILL.md (or your agent's skills folder).- name
- chi-related-work
- description
- Use when building the related-work section of an ACM CHI paper — covering the HCI venue family and the non-CS disciplines CHI draws on, positioning against the last few CHI cycles, keeping self-citation anonymous — in a venue where insufficient contextualization is the top assisted desk-reject ground.
CHI Related Work
At CHI, related work is screened before it is reviewed: ADR-Context — "grossly insufficient literature review to contextualize the contribution" — was the most frequently cited assisted desk-reject reason at CHI 2026, applied jointly by subcommittee chairs and ACs before external review (chi2026.acm.org outcome posts, read 2026-07-08). A thin or misaimed section no longer just lowers scores; it can end the submission in October.
Five lanes, all checked
| Lane | What belongs there | Who notices its absence |
|---|---|---|
| CHI itself, last ~3 cycles | The ongoing conversation your paper joins | 1AC/2AC — instantly |
| The HCI family (CSCW, UIST, DIS, IUI, ASSETS, IMWUT, TOCHI, IJHCS) | The specialist thread of your topic | The external recruited from that thread |
| Foundational HCI | The classic your framing stands on (or contradicts) | Senior reviewers |
| Feeder disciplines | Psychology, sociology, design, communication, health, ML — wherever your constructs come from | The reviewer trained in that discipline |
| Domain/application literature | The practice context you study (education, accessibility, health...) | The reviewer who lives in that context |
The feeder-discipline lane is CHI-distinctive and the most common hole: a paper measuring "trust" that cites no trust literature outside HCI, or one deploying thematic analysis citing only its HCI users, reads as unserious to exactly the reviewer the subcommittee recruited to check it.
Position, don't inventory
The paragraph unit that survives review states a front — what the cited cluster established, where it stops, and how your work moves it:
Prior deployments of voice assistants with older adults established adoption barriers in home settings [x, y, z], but studied single-user households; multi-resident care contexts, where addressee ambiguity dominates, remain unexamined. We provide the first such deployment.
Three tests per paragraph: it cites ≥2 works in tension or sequence (else it is an annotation), it ends with a gap or relationship claim, and deleting it would weaken the introduction's contribution list. A related-work section whose paragraphs all pass is positioning; anything else is coverage theater — and coverage theater at excessive length also feeds the ADR-Contribution ground (small contribution relative to paper length).
Show full SKILL.md (270 more words)Show less
Searching the field properly
The ACM Digital Library (now fully open access since January 2026) is the canonical index for the HCI family; Google Scholar catches the feeder disciplines and preprints.
Working queries (adapt per project):
- dl.acm.org: [Title: <construct>] AND [Conference: CHI] — filter to 2022-2026
- dl.acm.org: same construct in TOCHI + CSCW + ASSETS (the thread often lives
in a sibling, published a year before the CHI wave)
- Scholar: <construct> + the feeder discipline's own term (e.g. "technology
acceptance" vs "adoption"; "self-efficacy" vs "confidence")
- Forward-citation pass on your 3 closest papers — who cited them in the last
two cycles is your actual competitive set
- arXiv/OSF preprint sweep for concurrent work; cite-and-distinguish preprints
rather than pretending the lane is emptyLog the search date. Between September submission and the December 3 resubmission,
re-run the sweep — a five-week revision that misses a newly published near-neighbor
hands round-2 reviewers a free objection (chi-author-response).
Distinguishing near-neighbors without combat
When a close paper exists (it does), CHI reviewers expect precise, generous differentiation: name the axis of difference — population, setting, method, theoretical lens, system capability — and what your position on that axis newly shows. Dismissive comparisons ("however, they only...") backfire in a community small enough that the neighbor may be your external reviewer.
Self-citation under anonymity
CHI review is anonymized but your prior work is often the nearest neighbor. The
standing convention: cite yourself in the third person ("Building on the probe
deployed by [12]...") and never write "our previous study." Omitting your own
essential prior paper is worse than citing it — reviewers who find it later infer
concealment. Anonymize the prose, not the record. Link hygiene (no named
repositories in citations) is covered in chi-submission.
Two structural choices that read as competence
- Placement: background the reader needs before understanding the study can come early (§2); comparisons that only make sense after seeing your findings can legitimately sit in the discussion ("our finding extends [x]'s account..."). CHI accepts both; choosing deliberately signals control.
- Organization: organize by intellectual front, never by venue or chronology. Section headings like "Trust in automation," "Voice interfaces in shared spaces" do positioning work; "Related work A/B/C" does not.
Output format
[Lane audit] CHI-recent: <n cited> · HCI-family: <n> · foundational: <n> ·
feeder: <n> · domain: <n> — weakest lane: <which>
[Positioning test] paragraphs passing front-gap-relevance: <n>/<n>
[Nearest neighbors] <3 papers + the axis distinguishing each>
[Concurrent work] preprint sweep date: <date> — hits handled: yes/no
[Self-citation] third-person clean: yes/no
[ADR-Context exposure] low / medium / high — <reason>© 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 CHI-Skills/skills/chi-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Chi 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 |
|---|---|---|---|---|---|---|
| Chi Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | 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 Chi Related Work
What does Chi Related Work do?
A skill your agent uses when building the related-work section of an ACM CHI paper — covering the HCI venue family and the non-CS disciplines CHI draws on, positioning against the last few CHI…. Chi Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when building the related-work section of an ACM CHI paper — covering the HCI venue family and the non-CS disciplines CHI draws on, positioning against the last few CHI cycles, keeping self-citation anonymous — in a venue where insufficient contextualization is the top assisted desk-reject ground.
When should I use Chi Related Work?
Chi Related Work fits situations like: building the related-work section of an ACM CHI paper — covering the HCI venue family and the non-CS disciplines CHI draws on; positioning against the last few CHI cycles; keeping self-citation anonymous — in a venue where insufficient contextualization is the top assisted desk-reject ground.
How do I install Chi Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-related-work -a claude-code`. Or copy the skill folder (CHI-Skills/skills/chi-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/chi-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Chi Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-related-work -a codex`. Or copy the skill folder (CHI-Skills/skills/chi-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/chi-related-work in your project. Codex loads it when a task matches its description.
Can I use Chi 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 chi-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/chi-related-work, .gemini/skills/chi-related-work, .github/skills/chi-related-work and .opencode/skills/chi-related-work in your project.
What does Chi Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Chi Related Work is instructions for the agent only.
Does Chi 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 Chi 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 Chi Related Work use?
Chi 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 Chi Related Work use?
About 1.4k tokens (SKILL.md is roughly 5.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 Chi Related Work?
Skills that share tags, products or a category with Chi 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 Chi 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.