immortalqx/my_codex_skills/research-lit
Claude Code and agent skill by immortalqx/my_codex_skills
- community
Checking that the SKILL.md file is still in the repository.
Search and analyze research papers, find related work, summarize key ideas. Use when user says \"find papers\", \"related work\", \"literature review\", \"what does this paper say\", or needs to understand academic papers.
Install
npx vskill@latest install immortalqx/my_codex_skills/research-litSKILL.md
Research Literature Review
Research topic: $ARGUMENTS
Purpose
Use this skill to build a grounded paper landscape from:
- local PDFs already present in the workspace,
- public web search and official paper pages,
- structured arXiv metadata from the bundled helper script.
This skill is intentionally standalone. Its default path uses only local PDFs, public web search, and the bundled arXiv helper.
Runtime Knobs
- PAPER_LIBRARY Search these locations in order:
- a path explicitly provided by the user, e.g.
paper library: ~/my_papers/ papers/in the current projectliterature/in the current project
- MAX_LOCAL_PAPERS = 20 Maximum number of local PDFs to read at the title / abstract / intro level.
- ARXIV_DOWNLOAD = false When
true, download the top relevant arXiv PDFs after ranking. - ARXIV_MAX_DOWNLOAD = 5 Maximum number of arXiv PDFs to download.
Argument Directives
Parse $ARGUMENTS for optional directives:
paper library: <path>sources: localsources: websources: local, websources: allarxiv download: truemax download: <N>
If sources: is not specified, default to all.
Examples:
Source Table
| Priority | Source | ID | Detection | What it provides | |
|---|---|---|---|---|---|
| 1 | Local PDFs | local | papers/**/*.pdf, literature/**/*.pdf, or a user-provided library path | Existing papers the user already has | |
| 2 | Web search | web | Current agent web tools or direct HTTP access | Official paper pages, OpenReview, author pages, Semantic Scholar pages, venue pages | |
| 3 | Bundled arXiv helper | arxiv | scripts/arxiv_fetch.py inside this skill | Structured metadata and optional PDF download |
Workflow
Step 0: Scan Local Papers First
Before going outward, check whether the user already has relevant papers locally.
- Locate the paper library.
- Enumerate candidate PDFs under
papers//literature/or the user-provided path. - Filter by filename relevance first.
- For promising PDFs, read the first 3 pages and extract:
- title
- authors
- year
- venue if visible
- one-line core contribution
- why it matters to the current topic
- Build a "local papers already available" section.
If no relevant local papers are found, continue normally.
Step 1: Search the Web
Search the public web for recent and canonical papers on the topic.
Preferred targets:
- official conference or journal pages
- OpenReview
- arXiv abstract pages
- author project pages
- Semantic Scholar result pages
Rules:
- Prefer the published venue page when both a venue version and an arXiv mirror exist.
- Use arXiv or author pages when they are the most accessible legal source.
- Focus on the last 2 years unless the topic clearly requires older foundational work.
- De-duplicate against the local-paper set.
Step 2: Run the Bundled arXiv Helper
Always run the local helper for a structured arXiv pass:
This returns richer structured data than a generic search snippet:
- title
- abstract
- author list
- categories
- published / updated dates
- abstract URL
- PDF URL
Merge the arXiv results with the web-search findings and de-duplicate.
Optional PDF download, only when ARXIV_DOWNLOAD = true:
Download rules:
- only download the top
ARXIV_MAX_DOWNLOADitems - skip papers already present locally
- verify each PDF is larger than 10 KB
Step 3: Analyze Each Relevant Paper
For each paper retained after de-duplication, extract:
- Problem: what gap does it address?
- Method: what is the core technical contribution?
- Results: what numbers or concrete claims matter?
- Relevance: how does it relate to the current task?
- Source:
local,web, orarxiv
Step 4: Synthesize the Landscape
- group papers by method family or research theme
- identify consensus, disagreement, and open gaps
- distinguish directly competing work from supporting context
- surface what is genuinely new versus what is already standard
Step 5: Output
Present a structured table:
Then add a short narrative summary of the field:
- what the main clusters are
- what recent trends changed
- where the strongest baselines come from
- what the current blind spots appear to be
Step 6: Save Artifacts When Requested
If the user wants files:
- save PDFs into
papers/,literature/, or the specified library path - save the literature note or comparison note in the workspace
Key Rules
- Always include citation metadata: authors, year, venue or preprint status.
- Always separate peer-reviewed papers from preprints when it matters.
- Never fake certainty about novelty or claim strength.
- Never assume another installed skill is required for the default path.
- Use the bundled
scripts/arxiv_fetch.pyhelper instead of external install paths. - If one source is missing or weak, continue with the others instead of failing.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingresearch-lit/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/immortalqx/my_codex_skills/research-lit)