agentleFS
orange4664orange4664/research-skills/paper-finder/SKILL.md

paper-finder

Skill41 starsChanged 8 months agoMITView on GitHub

Search for academic papers and their source code repositories using multi-source APIs (arXiv, Semantic Scholar, HuggingFace Papers, GitHub).

  • Reads credentials
  • Installs packages

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    After execution, read workspace/paper_info.json to get:

    line 34
  2. Distinctive:

    If Semantic Scholar returns 429 (rate limited), the search continues with other sources

    line 85
  3. Distinctive:

    If no paper is found, suggest the user try a different query format

    line 86
  4. Distinctive:

    If paper is found but no code, inform the user that the paper may not have public code

    line 87
  5. Very specific:

    Check search_log in the output for detailed step-by-step information

    line 88

“Common” is measured: kept by at least 6 in 10 of the 3 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

Paper Finder Skill

Purpose

Find academic paper metadata and associated source code repositories from multiple data sources. This is the first step in our paper reproduction pipeline.

When to Use

  • User asks to "find", "search", or "look up" a paper
  • User provides an arXiv ID, DOI, paper title, or URL
  • User asks to "reproduce" or "replicate" a paper (run this first to find the paper and code)
  • User wants to know if a paper has official source code

How to Use

Step 1: Run the Search Script

Execute the Python script with the user's query:

python skills/paper-finder/scripts/search_paper.py "<query>" --output workspace/paper_info.json

Supported query formats:

  • arXiv ID: 1706.03762, 2301.12345
  • arXiv URL: https://arxiv.org/abs/1706.03762
  • DOI: 10.5555/3295222.3295349
  • Paper title: Attention Is All You Need
  • PDF path: /path/to/paper.pdf (uses filename as title hint)

Step 2: Read the Results

After execution, read workspace/paper_info.json to get:

{
  "found": true/false,
  "paper": {
    "title": "...",
    "authors": ["..."],
    "arxiv_id": "...",
    "doi": "...",
    "pdf_url": "...",
    "venue": "...",
    "citation_count": 123,
    "journal_url": "https://doi.org/..."
  },
  "code": {
    "found": true/false,
    "repositories": [
      {
        "url": "https://github.com/...",
        "is_official": true/false,
        "confidence": 0.85,
        "source": "hf_papers|abstract_url|github_search",
        "reason": "..."
      }
    ]
  }
}

Step 3: Interpret Results

  • is_official: true (confidence ≥ 0.50): Likely the authors' official repository
  • source: "abstract_url": GitHub URL was found directly in the paper text — very reliable
  • source: "hf_papers": Repository linked by HuggingFace community — reliable
  • source: "github_search": Found via GitHub search — verify manually

Step 4: Present Findings to User

Summarize the results in a clear format:

  1. Paper title, authors, year
  2. PDF download link
  3. Code repositories found (sorted by confidence)
  4. Whether official code was identified

Dependencies

  • Python 3.10+
  • requests library (pip install requests)

Optional: GitHub Token

Set GITHUB_TOKEN environment variable for higher GitHub API rate limits (30 req/min vs 10 req/min). Without a token, the tool still works but may hit rate limits during heavy use.

Error Handling

  • If Semantic Scholar returns 429 (rate limited), the search continues with other sources
  • If no paper is found, suggest the user try a different query format
  • If paper is found but no code, inform the user that the paper may not have public code
  • Check search_log in the output for detailed step-by-step information

Data Sources

  1. arXiv API — Paper metadata and PDF links
  2. Semantic Scholar — Journal DOI, citation count, cross-references
  3. HuggingFace Papers — Paper → GitHub repo mapping (replaced Papers with Code)
  4. GitHub Search — Fallback repository search

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.