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 discovering papers, mapping related work, reading papers deeply, checking citations, or building evidence cards for an auto research task.
Install Literature Evidence Mapping
$ npx skills add BingHanOfUESTC/open_agent_team --skill literature-evidence-mapping -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team literature-evidence-mapping --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/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .claude/skills && cp -r skills-src/teams/auto_research_team/skills/literature-evidence-mapping .claude/skills/literature-evidence-mapping && 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 "literature-evidence-mapping" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/auto_research_team/skills/literature-evidence-mapping into .claude/skills/literature-evidence-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "literature-evidence-mapping", 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/BingHanOfUESTC/open_agent_team/tree/main/teams/auto_research_team/skills/literature-evidence-mappingType 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 BingHanOfUESTC/open_agent_team --skill literature-evidence-mapping -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team literature-evidence-mapping --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .agents/skills && cp -r skills-src/teams/auto_research_team/skills/literature-evidence-mapping .agents/skills/literature-evidence-mapping && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "literature-evidence-mapping" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/auto_research_team/skills/literature-evidence-mapping into .agents/skills/literature-evidence-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "literature-evidence-mapping", 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 BingHanOfUESTC/open_agent_team --skill literature-evidence-mapping -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team literature-evidence-mapping --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/teams/auto_research_team/skills/literature-evidence-mapping .cursor/skills/literature-evidence-mapping && 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 "literature-evidence-mapping" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/auto_research_team/skills/literature-evidence-mapping into .cursor/skills/literature-evidence-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "literature-evidence-mapping", 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/BingHanOfUESTC/open_agent_team.git --path teams/auto_research_team/skills/literature-evidence-mapping--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 BingHanOfUESTC/open_agent_team --skill literature-evidence-mapping -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team literature-evidence-mapping --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/teams/auto_research_team/skills/literature-evidence-mapping .gemini/skills/literature-evidence-mapping && 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 "literature-evidence-mapping" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/auto_research_team/skills/literature-evidence-mapping into .gemini/skills/literature-evidence-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "literature-evidence-mapping", 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 BingHanOfUESTC/open_agent_team literature-evidence-mappingInstalls 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 BingHanOfUESTC/open_agent_team --skill literature-evidence-mapping -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .github/skills && cp -r skills-src/teams/auto_research_team/skills/literature-evidence-mapping .github/skills/literature-evidence-mapping && 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 "literature-evidence-mapping" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/auto_research_team/skills/literature-evidence-mapping into .github/skills/literature-evidence-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "literature-evidence-mapping", 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 BingHanOfUESTC/open_agent_team --skill literature-evidence-mapping -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BingHanOfUESTC/open_agent_team literature-evidence-mapping --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_team.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/teams/auto_research_team/skills/literature-evidence-mapping .opencode/skills/literature-evidence-mapping && 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 "literature-evidence-mapping" agent skill from https://github.com/BingHanOfUESTC/open_agent_team/tree/main/teams/auto_research_team/skills/literature-evidence-mapping into .opencode/skills/literature-evidence-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "literature-evidence-mapping", 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
literature-evidence-mapping- GitHub stars
- 106
- Token cost
- ~949 tokens
- SKILL.md length
- 174 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when discovering papers, mapping related work, reading papers deeply, checking citations, or building evidence cards for an auto research task.
- Works in 5 steps: Search Plan → Paper Inventory → Evidence Card → …
- Discovering papers
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Mapping related work
What it does
Literature Evidence Mapping is an agent skill from BingHanOfUESTC/open_agent_team. Use this skill when discovering papers, mapping related work, reading papers deeply, checking citations, or building evidence cards for an auto research task.
Its SKILL.md is about 950 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: Build persistent multi-agent teams that collaborate like real organizations to deliver complex tasks. The licence is MIT.
When your agent uses it
- Discovering papers
- Mapping related work
- Reading papers deeply
- Checking citations
Example prompts
- “/literature-evidence-mapping”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 7e28736. 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 (its code samples are markdown).
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
Literature Evidence Mapping loads about 949 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 174 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 BingHanOfUESTC/open_agent_team at commit 7e28736, republished under its MIT licence (© BingHanOfUESTC). 174 words, ~949 tokens.
Download SKILL.mdSave it as
.claude/skills/literature-evidence-mapping/SKILL.md (or your agent's skills folder).- name
- literature-evidence-mapping
- description
- Use this skill when discovering papers, mapping related work, reading papers deeply, checking citations, or building evidence cards for an auto research task.
Literature Evidence Mapping
This skill turns search results into research-grade evidence. It should be used before ideation and again before final paper writing.
1. Search Plan
Write:
research_workspace/literature/search_plan.mdInclude:
research question
inclusion criteria
exclusion criteria
search queries
venues and indexes
date window
target benchmark or dataset namesUse recursive search when the field is unclear or the first pass returns shallow coverage:
breadth pass: collect diverse candidate papers
depth pass: follow citations, authors, code links, benchmarks
gap pass: search directly for failure modes and limitations
recency pass: search the latest arXiv/OpenReview/venue/Papers With Code entriesDefault depth floor:
screen 30-60 candidate papers
include 15-30 relevant papers
deep-read 8-12 key papers
collect at least 5 recent papers from the last 24 months when available
collect at least 3 limitation/negative-result sources2. Paper Inventory
Maintain:
research_workspace/literature/paper_inventory.tsvColumns:
id
canonical_key
title
authors
year
venue
url
code_url
data_url
task
method_family
benchmark
result_claim
evidence_level
source_pass
why_relevant
limitations_signal
statusStatus values:
candidate
included
excluded
deep_read
baseline_source
idea_source
citation_only3. Evidence Card
For every key paper, write a card under:
research_workspace/literature/cards/<paper_id>.mdTemplate:
# <paper title>
- Citation:
- Source URL:
- Code/Data:
- Problem:
- Method:
- Key assumptions:
- Experiments:
- Reported results:
- Limitations stated by authors:
- Limitations inferred by team:
- Relevance to current research:
- What can be reused:
- What should not be assumed:
- Citation key:
- Paper section/table/figure anchors:
- Related-work bucket:
- Claims allowed in paper:
- Claims not supported:Deep-read cards must come from full paper text whenever possible. If only abstract or metadata was available, mark the card as abstract_only and do not use it for method details, result comparisons, or limitations beyond the abstract text.
4. Citation Verification
Before final report:
1. Every cited paper must appear in paper_inventory.tsv.
2. Every BibTeX entry must have a source URL or DOI/arXiv ID.
3. Claims about results must point to a paper section, table, figure, or experiment log.
4. If only metadata/abstract was read, mark it and avoid detailed claims.
5. Related Work should cite at least 12 papers unless Boss explicitly requests a short report or the field is too narrow.
6. Each Related Work paragraph needs at least one citation.
7. The paper must cite dataset, benchmark, metric, and reused implementation sources where applicable.Never invent missing BibTeX. If metadata is incomplete, use a placeholder note in the report draft and resolve before final delivery.
5. Gap Map
Write:
research_workspace/literature/gap_map.mdOrganize by:
problem gap
method gap
data gap
evaluation gap
efficiency gap
robustness gap
reproducibility gapEach gap must cite evidence and include a possible experiment.
Also write:
research_workspace/literature/citation_coverage.md
research_workspace/literature/claim_ledger.mdUse citation_coverage.md to track whether the final paper has enough references by section and topic bucket. Use claim_ledger.md to prevent unsupported claims from entering the paper.
© BingHanOfUESTC, 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 teams/auto_research_team/skills/literature-evidence-mapping of BingHanOfUESTC/open_agent_team.
Open the folder on GitHubat commit 7e28736
Compare with similar skills
Literature Evidence Mapping 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 |
|---|---|---|---|---|---|---|
| Literature Evidence Mapping this skillBingHanOfUESTC/open_agent_team | 106 | — | ~949 | 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 BingHanOfUESTC/open_agent_team
All 30 skills in this repoSkill Validation And Evaluation
BingHanOfUESTC/open_agent_team
A skill your agent uses when validating a newly created or updated agent skill with structure checks, routing positive and negative examples, contamination checks, progressive disclosure review, and…
Autoresearch Orchestration
BingHanOfUESTC/open_agent_team
A skill your agent uses when autoresearchteam needs to manage an end-to-end research lifecycle from Boss brief to literature, idea, implementation, experiments, synthesis, and LaTeX delivery.
Experiment Iteration Loop
BingHanOfUESTC/open_agent_team
A skill your agent uses when designing, running, logging, diagnosing, or iterating experiments for the selected research idea.
Latex Paper Artifact
BingHanOfUESTC/open_agent_team
A skill your agent uses when producing the final arXiv-style LaTeX paper, BibTeX, figures, tables, reproducibility statement, appendix, and artifact manifest.
Media Asset Sourcing
BingHanOfUESTC/open_agent_team
A skill your agent uses when PPT slides need external images, screenshots, logos, product photos, stock-like visuals, diagrams, or videos that must be downloaded, inserted, or linked with source and…
Originality Safety Guard
BingHanOfUESTC/open_agent_team
A skill your agent uses when checking creative fiction for originality, name safety, public figure misuse, historical figure misuse, news-event overfitting, recognizable plot borrowing, IP-like…
Related
Categories
Questions about Literature Evidence Mapping
What does Literature Evidence Mapping do?
A skill your agent uses when discovering papers, mapping related work, reading papers deeply, checking citations, or building evidence cards for an auto research task. Literature Evidence Mapping is an agent skill from BingHanOfUESTC/open_agent_team. Use this skill when discovering papers, mapping related work, reading papers deeply, checking citations, or building evidence cards for an auto research task.
When should I use Literature Evidence Mapping?
Literature Evidence Mapping fits situations like: discovering papers; mapping related work; reading papers deeply; checking citations.
How do I install Literature Evidence Mapping in Claude Code?
Run `npx skills add BingHanOfUESTC/open_agent_team --skill literature-evidence-mapping -a claude-code`. Or copy the skill folder (teams/auto_research_team/skills/literature-evidence-mapping in BingHanOfUESTC/open_agent_team) into .claude/skills/literature-evidence-mapping in your project. Claude Code loads it when a task matches its description.
How do I install Literature Evidence Mapping in Codex?
Run `npx skills add BingHanOfUESTC/open_agent_team --skill literature-evidence-mapping -a codex`. Or copy the skill folder (teams/auto_research_team/skills/literature-evidence-mapping in BingHanOfUESTC/open_agent_team) into .agents/skills/literature-evidence-mapping in your project. Codex loads it when a task matches its description.
Can I use Literature Evidence Mapping 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 BingHanOfUESTC/open_agent_team --skill literature-evidence-mapping -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/literature-evidence-mapping, .gemini/skills/literature-evidence-mapping, .github/skills/literature-evidence-mapping and .opencode/skills/literature-evidence-mapping in your project.
What does Literature Evidence Mapping need to run?
SKILL.md names no scripts, command-line tools or credentials: Literature Evidence Mapping is instructions for the agent only.
Does Literature Evidence Mapping 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 Literature Evidence Mapping 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 Literature Evidence Mapping use?
Literature Evidence Mapping 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 Literature Evidence Mapping use?
About 949 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 Literature Evidence Mapping?
Skills that share tags, products or a category with Literature Evidence Mapping: 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 Literature Evidence Mapping?
BingHanOfUESTC (a GitHub user) maintains it in BingHanOfUESTC/open_agent_team, which has 106 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on June 23, 2026.
Source: BingHanOfUESTC/open_agent_team on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.