
from drsai12
Search academic papers, extract structured metadata (title, authors, venue, citations, PDF/BibTeX) across arXiv, Semantic Scholar, PubMed, ACM, IEEE and CNKI us
This skill provides robust academic search and metadata-extraction capabilities. It helps an agent locate papers, gather structured metadata (title, authors, year, venue, citation counts, DOI/arXiv IDs), fetch PDFs or BibTeX entries, and combine results from multiple platforms into a deduplicated schema. The skill includes guidance on selecting the right source (arXiv, Semantic Scholar, PubMed, Papers With Code, ACM DL, IEEE Xplore, CNKI) and when to use browser automation (CDP) for sites without APIs like Google Scholar or CNKI.
Use this skill when a user asks to find papers, build a literature review, retrieve citation counts or citation graphs, export BibTeX, fetch PDFs, or assemble an annotated bibliography. It triggers on queries about papers, venues, citations, authors, arXiv/DOI lookups, and when links to known academic domains appear.
Best suited for agents with HTTP and headless-browser capabilities (Claude Code / agents that can run Node/Curl and CDP). The skill assumes access to network APIs and optionally a CDP proxy for Google Scholar and CNKI.
Comprehensive academic paper search skill covering arXiv, Semantic Scholar, PubMed, Google Scholar, CNKI and more. Well-structured SKILL.md with bilingual triggers and detailed platform-specific guidance. CDP proxy script is production-quality Node.js for browser automation. Check-deps script ran successfully; self-test and release-test failed due to Chrome not being available in this environment (expected). No security concerns found — all connections are localhost-only, no credential exfiltration or destructive commands.
chrome/chromium (CDP mode only)ripgrep (rg) for release-test.shVery well-crafted skill. The CDP proxy /eval endpoint allows arbitrary JS execution but this is by design and localhost-only. Bilingual documentation (Chinese primary) is thorough. Reference structure with disciplines/, site-patterns/, workflows/ is exemplary. Only the test scripts failed due to environment constraints (no Chrome), not code quality issues.