deepxiv/deepxiv_sdk/deepxiv-baseline-table
Claude Code and agent skill by deepxiv/deepxiv_sdk
- community
Checking that the SKILL.md file is still in the repository.
Build a markdown baseline table for a research topic using deepxiv search, brief, head, and experiment-section reads, extracting paper title, URL, open-source status, datasets, benchmark scores, and other comparison-ready details.
Install
npx vskill@latest install deepxiv/deepxiv_sdk/deepxiv-baseline-tableSKILL.md
DeepXiv Baseline Table
Use this skill when the user wants to map a topic into a comparison table, baseline survey, benchmark roundup, or "what papers evaluated on which datasets with what scores and whether code is open".
Typical requests:
- "Find recent baseline papers on agentic memory"
- "What papers in the last month evaluated on dataset X?"
- "Make me a markdown table of methods, datasets, and scores"
Goal
Turn a topic search into a structured markdown table:
- Search recent papers with
deepxiv search - Brief all candidates with
deepxiv paper <id> --brief - Keep the relevant papers, prioritizing papers with GitHub/code
- Inspect promising papers with
deepxiv paper <id> --head - Read experiment-related sections with
deepxiv paper <id> --section ... - Extract datasets, evaluation setup, and reported scores
- Write a markdown table summarizing the baselines
Default Workflow
1. Search by topic and date range
Use a broad search first.
Default heuristics:
- Use the user’s exact topic phrase first
- Keep
--limithigh enough to avoid missing relevant papers - If results are noisy, refine the query with close variants
Examples:
2. Brief all candidates
For each arXiv ID, fetch:
Capture:
- title
- arXiv ID
- publish date
- TLDR
- keywords
- GitHub URL
- PDF/source URL
This is the screening step. Do not read full sections yet.
3. Filter and prioritize
Keep papers that are actually about the topic, not just adjacent terms.
Prioritize:
- papers directly centered on the topic
- empirical papers over purely conceptual ones
- papers with GitHub/code
- benchmark or comparison papers
- papers with clear experiment sections
De-prioritize:
- purely opinion or survey papers unless the user asked for surveys
- papers with no clear evaluation evidence
- papers only loosely related to the topic
If the list is still large, keep a primary set and a secondary set:
- Primary: strongest and most relevant baselines
- Secondary: adjacent or weaker evidence
4. Inspect paper structure
For retained papers:
Use --head to find experiment-bearing sections such as:
- Experiments
- Evaluation
- Results
- Benchmark
- Main Results
- Analysis
Also capture:
- abstract
- total token count
- section names
5. Read only experiment-relevant sections
Once the right sections are known, read only those:
Section selection guidance:
- Start with
ExperimentsorEvaluation - Read
Resultsif the metrics are not clear - Read
Introductiononly if the task setup is still ambiguous - Read
Appendixonly if benchmark details are missing from the main paper
Avoid reading the entire paper unless the user explicitly asks for it.
Extraction Targets
For each retained paper, try to extract:
- Title
- arXiv ID
- Paper URL
- GitHub/code URL
- Open-source status:
Yes,No, orUnknown - Main task
- Evaluation datasets / benchmarks
- Key metrics
- Best reported scores
- Notes on experimental setting
If exact scores are not clearly available from the inspected sections:
- leave the score field as
Not clearly stated - do not invent or infer a number
If datasets are only partially visible:
- include the datasets you can verify
- mention that the list may be incomplete
Markdown Output
Write a markdown file in the workspace unless the user specifies another path.
Recommended filename:
Example:
Recommended output structure:
Writing Rules
- Prefer verified facts over broad summaries
- Separate "paper is relevant" from "paper has strong benchmark evidence"
- Be explicit when a row is missing score details
- Mark open-source status conservatively
- Keep the table compact but useful
- Add short notes when comparisons are not apples-to-apples
Decision Rules
- Always start with search and brief
- Prefer papers with GitHub when deciding which ones to inspect first
- Use
--headbefore--section - Read only the sections needed to recover datasets and scores
- If the topic is broad, tell the user when the table mixes multiple subtask types
Minimal Example
Then write a markdown table with:
- title
- paper URL
- open-source status
- code URL
- datasets / benchmarks
- metrics / scores
- short notes on what was actually verified
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 repositoryCheckingskills/deepxiv-baseline-table/SKILL.md
Popularity
- Repository stars
- 717
- Repository forks
- 40
- 7-day trend score
- 33
Stars and forks are for the whole GitHub repository, not this skill alone. 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/deepxiv/deepxiv_sdk/deepxiv-baseline-table)