deepxiv-baseline-table
Skill843 starsChanged 8 months agoMITView on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- amaxz/hermes-skillsword for word, first seen May 10, 2026
Other versions1 project uses a version of this.
Word for word · 1
- amaxz/hermes-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- deepxiv-cliSkill
- deepxiv-fa-appraiseSkill
- deepxiv-fa-casesSkill
- deepxiv-fa-cveSkill
- deepxiv-fa-drugsSkill
- deepxiv-fa-filingsSkill
- deepxiv-fa-frSkill
- deepxiv-fa-grantsSkill
- deepxiv-fa-lawSkill
- deepxiv-fa-osvSkill
- deepxiv-fa-standardsSkill
- deepxiv-fa-stocksSkill
- deepxiv-fa-talentSkill
- deepxiv-fa-trialsSkill
- deepxiv-fa-uk-eu-lawSkill
- deepxiv-fa-us-lawSkill
- deepxiv-trending-digestSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
30 rules. About 0 are common, 20 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈20
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when the user wants to map a topic into a comparison table, baseline survey, benchmark roundup, or "what papers evaluated on …
- Very specific: line 19
Search recent papers with deepxiv search
- Distinctive: line 21
Keep the relevant papers, prioritizing papers with GitHub/code
- Very specific: line 23
Read experiment-related sections with deepxiv paper <id> --section ...
- Distinctive: line 25
Write a markdown table summarizing the baselines
- Distinctive: line 31
Use a broad search first.
- Distinctive: line 38
Use the user’s exact topic phrase first
- Very specific: line 39
Keep --limit high enough to avoid missing relevant papers
- Distinctive: line 40
If results are noisy, refine the query with close variants
- Distinctive: line 71
Keep papers that are actually about the topic, not just adjacent terms.
- Distinctive: line 85
If the list is still large, keep a primary set and a secondary set:
- Very specific: line 97
Use --head to find experiment-bearing sections such as:
- Very specific: line 121
Start with Experiments or Evaluation
- Very specific: line 122
Read Results if the metrics are not clear
- Very specific: line 123
Read Introduction only if the task setup is still ambiguous
- Very specific: line 124
Read Appendix only if benchmark details are missing from the main paper
- Distinctive: line 126
Avoid reading the entire paper unless the user explicitly asks for it.
- Distinctive: line 143
If exact scores are not clearly available from the inspected sections:
- Very specific: line 144
leave the score field as Not clearly stated
- Distinctive: line 145
do not invent or infer a number
- Distinctive: line 147
If datasets are only partially visible:
- Distinctive: line 153
Write a markdown file in the workspace unless the user specifies another path.
- Distinctive: line 204
Prefer verified facts over broad summaries
- Distinctive: line 208
Keep the table compact but useful
- Distinctive: line 209
Add short notes when comparisons are not apples-to-apples
- Distinctive: line 213
Always start with search and brief
- Distinctive: line 214
Prefer papers with GitHub when deciding which ones to inspect first
- Very specific: line 215
Use --head before --section
- Distinctive: line 216
Read only the sections needed to recover datasets and scores
- Distinctive: line 217
If the topic is broad, tell the user when the table mixes multiple subtask types
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
deepxiv search "agentic memory" --date-from 2026-03-01 --limit 100 --format jsonDefault 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:
deepxiv search "agentic memory" --date-from 2026-03-01 --limit 100 --format json
deepxiv search "memory agents long-horizon" --date-from 2026-03-01 --limit 100 --format json
deepxiv search "agent memory benchmark" --date-from 2026-03-01 --limit 100 --format json2. Brief all candidates
For each arXiv ID, fetch:
deepxiv paper <arxiv_id> --briefCapture:
- 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:
deepxiv paper <arxiv_id> --headUse --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:
deepxiv paper <arxiv_id> --section Experiments
deepxiv paper <arxiv_id> --section Evaluation
deepxiv paper <arxiv_id> --section ResultsSection 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:
<topic>-baseline-table-YYYY-MM-DD.mdExample:
agentic-memory-baseline-table-2026-04-01.mdRecommended output structure:
# Agentic Memory Baseline Table
Topic: agentic memory
Date range: 2026-03-01 to 2026-04-01
Search source: deepxiv
## Summary
- Number of search results
- Number of relevant papers retained
- Number with public code
- Main recurring datasets or benchmark families
## Baseline Table
| Title | arXiv | URL | Open Source | Code URL | Datasets / Benchmarks | Metrics / Scores | Notes |
| --- | --- | --- | --- | --- | --- | --- | --- |
| ... | ... | ... | ... | ... | ... | ... | ... |
## Inclusion Notes
- Which papers were excluded and why
- Which rows are based only on `--brief`
- Which rows were verified through `--head` and experiment/result sections
## Observations
- Common evaluation datasets
- Which papers appear strongest
- Where the benchmark story is still fragmentedWriting 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
deepxiv search "agentic memory" --date-from 2026-03-01 --limit 100 --format json
deepxiv paper 2603.21489 --brief
deepxiv paper 2603.21489 --head
deepxiv paper 2603.21489 --section ExperimentsThen write a markdown table with:
- title
- paper URL
- open-source status
- code URL
- datasets / benchmarks
- metrics / scores
- short notes on what was actually verified
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

