agentleFS
texra-aitexra-ai/texra-scientific-skills/skills/literature-search/SKILL.md

literature-search

Skill4 starsChanged 7 months agoMITView on GitHub

Discover, verify, and synthesize academic literature and web sources for research tasks. Use when Codex needs to find recent papers, trace citations, compare preprints with published versions, verify attributed claims, or build a source-backed literature summary with primary references.

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use systematic-review.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • xjtulycSkill

    systematic-review

    Use this Skill when conducting a systematic literature review following PRISMA 2020: PICO framework, database search strategy, title/abstract screening, full-text eligibility, data extraction, and GRADE evidence grading.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for related-work searches, citation verification, research briefings, source-backed summaries, and claim checking across …

    line 10
  2. Distinctive:

    Start from the actual question.

    line 14
  3. Distinctive:

    Prefer primary sources. Use publisher pages, DOI metadata, arXiv records, official project pages, and original papers before secondary …

    line 15
  4. Distinctive:

    When the user needs a recommendation or synthesis, explain the tradeoffs and evidence rather than only listing papers.

    line 20
  5. Distinctive:

    Do not present unverified claims as settled fact.

    line 24
  6. Distinctive:

    Prefer the latest authoritative version when preprint and journal versions differ.

    line 25
  7. Distinctive:

    Keep citation details precise enough that a researcher can find the source immediately.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Literature Search

When to use this skill

Use this skill for related-work searches, citation verification, research briefings, source-backed summaries, and claim checking across papers, arXiv, DOIs, and the open web.

Workflow

  1. Start from the actual question. Identify the topic, time window, field, and whether the user wants breadth, depth, recency, or verification.
  2. Prefer primary sources. Use publisher pages, DOI metadata, arXiv records, official project pages, and original papers before secondary summaries.
  3. Distinguish source types clearly: peer-reviewed publication, preprint, project page, documentation, benchmark site, or news coverage.
  4. Capture bibliographic facts while searching: title, authors, venue, year, DOI, arXiv ID, and URL.
  5. Cross-check important claims across more than one source when possible, especially for dates, quantitative results, and priority claims.
  6. For literature reviews, group findings by theme or method rather than presenting an unstructured list.
  7. When the user needs a recommendation or synthesis, explain the tradeoffs and evidence rather than only listing papers.

Quality Bar

  • Do not present unverified claims as settled fact.
  • Prefer the latest authoritative version when preprint and journal versions differ.
  • Keep citation details precise enough that a researcher can find the source immediately.
  • Separate what a paper claims from what you infer from it.
  • Note recency explicitly when the topic is moving quickly.

For a deeper evaluation pass, use references/source-evaluation.md when comparing conflicting sources, building a formal literature review, or checking whether a citation really supports a claim.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.