artivilla/paper-mcp
skills/paper-mcp/SKILL.md
Use the Paper MCP server to fetch paper metadata, sections, figures, citations, and full-text context, then translate that context into structured outputs such as summaries, extraction tables, and implementation-ready notes. Trigger when a task involves paper links/DOIs/arXiv IDs, literature review, citation extraction, or Paper MCP setup and troubleshooting.
tools
Updated Jun 9, 2026
$ install --global
skillsauthnpx skillsauth add artivilla/agents-config paper-mcpInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 9, 2026, 3:07 AM57.5s3 files scanned
SKILL.md
- name:
- paper-mcp
- description:
- Use the Paper MCP server to fetch paper metadata, sections, figures, citations, and full-text context, then translate that context into structured outputs such as summaries, extraction tables, and implementation-ready notes. Trigger when a task involves paper links/DOIs/arXiv IDs, literature review, citation extraction, or Paper MCP setup and troubleshooting.
Paper MCP
Use the Paper MCP server for paper-driven research and implementation tasks. For setup and debugging details (env vars, config, verification), see references/paper-mcp-config.md.
Paper MCP integration rules
These rules define how to translate paper inputs into reliable outputs and must be followed for every paper-driven change.
Required flow (do not skip)
- Resolve the paper first (URL/DOI/arXiv/PMID) and fetch high-level metadata before requesting full text.
- If the full response is large or truncated, fetch section-level context and work section-by-section.
- Fetch a stable citation list before drafting any claims that depend on references.
- If figures/tables are relevant, fetch those assets and capture captions prior to synthesis.
- Only after metadata plus content context are collected, generate the user output (summary/table/notes/code-facing plan).
- Validate all key claims against source excerpts before marking complete.
Tool mapping rule
- Paper MCP deployments may expose different tool names.
- Start by listing available paper MCP tools, then map this workflow to equivalent tools in the current server.
- If a required capability is missing (for example, no section fetch or no citation endpoint), note the limitation and continue with the best available fallback.
Implementation rules
- Treat paper MCP responses as source context, not final prose.
- Keep outputs traceable: tie each important claim to a section, figure, or citation.
- Distinguish evidence from inference clearly.
- Preserve units, metrics, and dataset/task names exactly as written in source context.
- Prefer concise structured output (tables/checklists) when comparing multiple papers.
- For code-facing tasks, extract actionable constraints (input shapes, evaluation metrics, baseline numbers, reproducibility requirements).
Quality rules
- Do not invent citations, metrics, or section names.
- Call out uncertainty when context is partial, truncated, or conflicting.
- If two sources disagree, present both with scope and date/context differences.
- Keep quoted text short and use paraphrasing for long passages.
References
references/paper-mcp-config.md- setup, verification, troubleshooting, and input ID guidance.references/paper-tools-and-prompts.md- tool mapping checklist and prompt templates for common paper workflows.
Related Skills
artivilla/web-interface-guidelines
development
VerifiedTrustedCommunity
Review UI code against Vercel's Web Interface Guidelines. Use when checking interactions, animation, layout, content, accessibility, performance, and design standards with MUST/SHOULD/NEVER rules.
SKILL.mdUpdated Jun 9, 2026
artivilla/web-design-guidelines
development
VerifiedTrustedCommunity
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
SKILL.mdUpdated Jun 9, 2026
artivilla/vercel-react-best-practices
development
VerifiedTrustedCommunity
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
SKILL.mdUpdated Jun 9, 2026
artivilla/vercel-composition-patterns
development
VerifiedTrustedCommunity
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
SKILL.mdUpdated Jun 9, 2026