Agent skill · Backend & API

semantic-scholar

Search published venue papers (IEEE, ACM, Springer, etc.) via Semantic Scholar API. Complements /arxiv (preprints) with citation counts, venue metadata, and TLDR. Use when user says "search semantic scholar", "find IEEE papers", "find journal papers", "venue papers", "citation search", or wants published literature beyond arXiv preprints.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill semantic-scholar-wanshuiyin-auto-claude-code-res --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Allowed tools: Bash(*)ReadWrite
Path: skills/analysis/semantic-scholar-wanshuiyin-auto-claude-code-res/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Semantic Scholar Paper Search Search topic or paper ID: $ARGUMENTS ## Role & Positioning This skill is the **published venue** counterpart to `/arxiv`: | Skill | Source | Best for | |-------|--------|----------| | `/arxiv` | arXiv API | Latest preprints, cutting-edge unrefereed work | | `/semantic-scholar` | Semantic Scholar API | **Published** journal/conference papers (IEEE, ACM, Springer, etc.) 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" -

What's inside
Steps it walks through
  1. Role & Positioning
  2. Constants
  3. Workflow
  4. Step 1: Parse Arguments
  5. Step 2: Search Papers
  6. Step 3: Fetch Details for a Specific Paper
  7. Step 4: De-duplicate Against arXiv
  8. Step 5: Present Results
  9. Step 6: Detailed Summary
  10. Step 7: Update Research Wiki (if active)
  11. Step 8: Final Output
  12. Key Rules
Ships with 1 file
  • metadata.json
Commands it runs
python3 "$SCRIPT" search "QUERY" --max MAX_RESULTS \
python3 "$SCRIPT" search-bulk "QUERY" --max MAX_RESULTS \
python3 "$SCRIPT" paper "PAPER_ID"
More from claude-skill-registry
All skills →
About this skill
What does the semantic-scholar skill do?

Search published venue papers (IEEE, ACM, Springer, etc.) via Semantic Scholar API. Complements /arxiv (preprints) with citation counts, venue metadata, and TLDR. Use when user says "search semantic scholar", "find IEEE papers", "find journal papers", "venue papers", "citation search", or wants published literature beyond arXiv preprints.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill semantic-scholar-wanshuiyin-auto-claude-code-res --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going