agentleFS
catalsqlb-cmdcatalsqlb-cmd/Prism-H/skills/semantic-scholar/SKILL.md

semantic-scholar

Skill16 starsChanged 6 months agoMITView on GitHub

Search published venue papers (journals, university presses, conference proceedings) via Semantic Scholar API. Provides citation counts, venue metadata, and TLDR. Use when user says "search semantic scholar", "find journal papers", "venue papers", "citation search", or wants published scholarly literature.

  • Reads credentials

8 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use deepxiv, invention-structuring and 4 more.

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.
  • raja21068Skill

    deepxiv

    Search and progressively read open-access academic papers through DeepXiv. Use when the user wants layered paper access, section-level reading, trending papers, or DeepXiv-backed literature retrieval.

    Also in 4 projects that use this

  • raja21068Skill

    invention-structuring

    Structure a raw invention idea into a formal invention disclosure. Use when user says \"构建发明\", \"structure invention\", \"发明构建\", \"invention disclosure\", or wants to formalize a rough idea into a patent-ready structure.

    Also in 3 projects that use this

  • +4 more from raja21068

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 5 are common, 0 are distinctive, and 9 are very specific to this project.

  • 5

    Common

    Most of the 7 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 9

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Search topic or paper ID: $ARGUMENTS

    line 10
  2. Very specific:

    Do NOT duplicate arXiv's job: If results contain an externalIds.ArXiv field, the paper is also on arXiv — note this but do not re-fetch …

    line 21
  3. Very specific:

    - sort: citations|date: use search-bulk with --sort citationCount:desc or publicationDate:desc

    line 57
  4. Very specific:

    If the argument matches a DOI pattern (10.XXXX/...), a Semantic Scholar ID (40-char hex), or a prefixed ID (ARXIV:..., CorpusId:...), skip …

    line 59
  5. Very specific:

    If semantic_scholar_fetch.py is not found, fall back to inline Python using urllib against …

    line 87
  6. Common:

    When a single paper ID is requested:

    line 102
  7. Common:

    If present → paper is also on arXiv.

    line 117
  8. Common:

    If absent → paper is venue-only (e.g.

    line 118
  9. Very specific:

    Open Access PDF: if openAccessPdf.url is non-empty, show it

    line 132
  10. Common:

    TLDR: if available, show the one-line summary

    line 133
  11. Very specific:

    Also on arXiv: if externalIds.ArXiv exists, note the arXiv ID

    line 134
  12. Very specific:

    Default to filtered search: Always apply --fields-of-study and --publication-types unless user says - fields: all.

    line 198
  13. Very specific:

    DOI is the canonical ID for published papers: Always show DOI links for IEEE/ACM/Springer papers.

    line 201
  14. Very specific:

    If the S2 API is unreachable, suggest using /research-lit "topic" - sources: web as fallback.

    line 205

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

Semantic Scholar Paper Search

Search topic or paper ID: $ARGUMENTS

Role & Positioning

This skill targets published venue scholarship:

SkillSourceBest for
/research-lit (web)WebSearch / arXivBroad surveys, preprints, foundational works
/semantic-scholarSemantic Scholar APIPublished journal/conference papers and books with citation counts, venue info, TLDR

Do NOT duplicate arXiv's job. If results contain an externalIds.ArXiv field, the paper is also on arXiv — note this but do not re-fetch from arXiv.

Constants

  • MAX_RESULTS = 10 — Default number of search results.
  • FETCH_SCRIPT — tools/semantic_scholar_fetch.py relative to the project root. Fall back to inline Python if not found.
  • DEFAULT_FILTERS — For general research queries, apply these by default to reduce noise:
    • --fields-of-study "Computer Science,Engineering"
    • --publication-types JournalArticle,Conference

Overrides (append to arguments):

  • /semantic-scholar "topic" - max: 20 — return up to 20 results
  • /semantic-scholar "topic" - type: journal — only journal articles
  • /semantic-scholar "topic" - type: conference — only conference papers
  • /semantic-scholar "topic" - min-citations: 50 — only highly-cited papers
  • /semantic-scholar "topic" - year: 2022- — papers from 2022 onward
  • /semantic-scholar "topic" - fields: all — remove default field-of-study filter
  • /semantic-scholar "topic" - sort: citations — bulk search sorted by citation count
  • /semantic-scholar "DOI:10.1109/..." — fetch a single paper by DOI

Workflow

Step 1: Parse Arguments

Parse $ARGUMENTS for directives:

  • Query or ID: main search term, or a paper identifier:
    • DOI: 10.1109/TWC.2024.1234567
    • Semantic Scholar ID: f9314fd99be5f2b1b3efcfab87197d578160d553
    • ArXiv: ARXIV:2006.10685
    • Corpus: CorpusId:219792180
  • - max: N: override MAX_RESULTS
  • - type: journal|conference|review|all: map to --publication-types
  • - min-citations: N: map to --min-citations
  • - year: RANGE: map to --year (e.g. 2022-, 2020-2024)
  • - fields: FIELDS: override --fields-of-study (use all to remove filter)
  • - sort: citations|date: use search-bulk with --sort citationCount:desc or publicationDate:desc

If the argument matches a DOI pattern (10.XXXX/...), a Semantic Scholar ID (40-char hex), or a prefixed ID (ARXIV:..., CorpusId:...), skip search and go directly to Step 3.

Step 2: Search Papers

Locate the fetch script:

SCRIPT=$(find tools/ -name "semantic_scholar_fetch.py" 2>/dev/null | head -1)
[ -z "$SCRIPT" ] && SCRIPT=$(find ~/.claude/skills/semantic-scholar/ -name "semantic_scholar_fetch.py" 2>/dev/null | head -1)

Standard search (default — relevance-ranked):

python3 "$SCRIPT" search "QUERY" --max MAX_RESULTS \
  --fields-of-study "Computer Science,Engineering" \
  --publication-types JournalArticle,Conference

Bulk search (when - sort: is specified, or MAX_RESULTS > 100):

python3 "$SCRIPT" search-bulk "QUERY" --max MAX_RESULTS \
  --sort citationCount:desc \
  --fields-of-study "Computer Science" \
  --year "2020-"

If semantic_scholar_fetch.py is not found, fall back to inline Python using urllib against https://api.semanticscholar.org/graph/v1/paper/search.

Recommended filter combos (from testing):

GoalFlags
High-quality journal papers--publication-types JournalArticle --min-citations 10
CS/EE papers, recent--fields-of-study "Computer Science,Engineering" --year "2022-"
Foundational / high-impactsearch-bulk --sort citationCount:desc --fields-of-study "Computer Science"
Conference papers only--publication-types Conference

Note: --venue requires exact venue names (e.g. "IEEE Transactions on Signal Processing"), not partial matches like "IEEE". Avoid using --venue in automated flows — prefer --publication-types + --fields-of-study.

Step 3: Fetch Details for a Specific Paper

When a single paper ID is requested:

python3 "$SCRIPT" paper "PAPER_ID"

Where PAPER_ID can be:

  • DOI: 10.1109/TSP.2021.3071210
  • ArXiv: ARXIV:2006.10685
  • CorpusId: CorpusId:219792180
  • S2 ID: f9314fd99be5f2b1b3efcfab87197d578160d553

Step 4: De-duplicate Against arXiv

For each result, check externalIds.ArXiv:

  • If present → paper is also on arXiv. Note this in output but do NOT re-fetch the preprint.
  • If absent → paper is venue-only (e.g. a journal article or book without a preprint). This is the unique value of this skill.

Step 5: Present Results

Present results as a table:

| # | Title | Venue | Year | Citations | Authors | Type |
|---|-------|-------|------|-----------|---------|------|
| 1 | Deep Learning Enabled... | IEEE Trans. Signal Process. | 2021 | 1364 | Xie et al. | Journal |

For each paper, also show:

  • DOI link: https://doi.org/DOI (for IEEE/ACM papers, this is the canonical link)
  • Open Access PDF: if openAccessPdf.url is non-empty, show it
  • TLDR: if available, show the one-line summary
  • Also on arXiv: if externalIds.ArXiv exists, note the arXiv ID

Step 6: Detailed Summary

For each paper (or top 5 if many results):

## [Title]

- **Venue**: [venue name] ([publicationVenue.type]: journal/conference)
- **Year**: [year] | **Citations**: [citationCount]
- **Authors**: [full author list]
- **DOI**: [doi link]
- **Fields**: [fieldsOfStudy]
- **TLDR**: [tldr.text if available]
- **Abstract**: [abstract]
- **Open Access**: [openAccessPdf.url or "Not available"]
- **Also on arXiv**: [ArXiv ID if exists, else "No"]

Step 7: Update Research Wiki (if active)

Required when research-wiki/ exists in the project; skip silently otherwise. Ingest the papers presented to the user. For results with an externalIds.ArXiv field, use --arxiv-id; for venue-only papers (no arXiv mirror — common for IEEE/ACM), fall back to manual metadata:

if [ -d research-wiki/ ]:
    for each paper in results:
        if paper.externalIds.ArXiv:
            python3 tools/research_wiki.py ingest_paper research-wiki/ \
                --arxiv-id "<ArXiv>"
        else:
            python3 tools/research_wiki.py ingest_paper research-wiki/ \
                --title "<title>" --authors "<authors joined by , >" \
                --year <year> --venue "<venue>" \
                [--external-id-doi "<externalIds.DOI>"]

The helper handles slug / dedup / page / index / log — do not handwrite papers/<slug>.md. See shared-references/integration-contract.md. Backfill with /research-wiki sync --arxiv-ids <id1>,<id2>,... for arXiv-available papers.

Step 8: Final Output

Summarize what was done:

  • Found N published papers for "query"
  • Filters applied: [publication types, fields, year range, etc.]
  • N papers are venue-only (not on arXiv)
  • Wiki-ingested N papers (if research-wiki/ was present)

Suggest follow-up skills:

/research-lit "topic"    - multi-source review: Zotero + local PDFs + web + S2
/novelty-check "idea"    - verify novelty against literature

Key Rules

  • Default to filtered search: Always apply --fields-of-study and --publication-types unless user says - fields: all. Without filters, S2 returns cross-discipline noise (linguistics, psychology, etc.).
  • Citation count is gold: S2's citation data is its main advantage over arXiv. Always show citationCount prominently and use it to rank/prioritize results.
  • Venue metadata matters: Show venue and publicationVenue.type (journal vs conference) — this helps users assess paper quality.
  • DOI is the canonical ID for published papers: Always show DOI links for IEEE/ACM/Springer papers.
  • Rate limiting: S2 API without key is heavily rate-limited (~1 req/s, strict cooldown). If HTTP 429 occurs, wait and retry. Recommend users set SEMANTIC_SCHOLAR_API_KEY env var for higher limits (free at https://www.semanticscholar.org/product/api#api-key-form).
  • TLDR may be null: Some publishers (notably IEEE) elide the TLDR field. Fall back to showing the first sentence of the abstract.
  • openAccessPdf may be empty: Many IEEE papers are closed access. Always provide the DOI link as fallback.
  • If the S2 API is unreachable, suggest using /research-lit "topic" - sources: web as fallback.

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.