agentleFS
DeepXivDeepXiv/deepxiv_sdk/skills/deepxiv-baseline-table/SKILL.md

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

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
  1. Distinctive:

    Use this skill when the user wants to map a topic into a comparison table, baseline survey, benchmark roundup, or "what papers evaluated on …

    line 8
  2. Very specific:

    Search recent papers with deepxiv search

    line 19
  3. Distinctive:

    Keep the relevant papers, prioritizing papers with GitHub/code

    line 21
  4. Very specific:

    Read experiment-related sections with deepxiv paper <id> --section ...

    line 23
  5. Distinctive:

    Write a markdown table summarizing the baselines

    line 25
  6. Distinctive:

    Use a broad search first.

    line 31
  7. Distinctive:

    Use the user’s exact topic phrase first

    line 38
  8. Very specific:

    Keep --limit high enough to avoid missing relevant papers

    line 39
  9. Distinctive:

    If results are noisy, refine the query with close variants

    line 40
  10. Distinctive:

    Keep papers that are actually about the topic, not just adjacent terms.

    line 71
  11. Distinctive:

    If the list is still large, keep a primary set and a secondary set:

    line 85
  12. Very specific:

    Use --head to find experiment-bearing sections such as:

    line 97
  13. Very specific:

    Start with Experiments or Evaluation

    line 121
  14. Very specific:

    Read Results if the metrics are not clear

    line 122
  15. Very specific:

    Read Introduction only if the task setup is still ambiguous

    line 123
  16. Very specific:

    Read Appendix only if benchmark details are missing from the main paper

    line 124
  17. Distinctive:

    Avoid reading the entire paper unless the user explicitly asks for it.

    line 126
  18. Distinctive:

    If exact scores are not clearly available from the inspected sections:

    line 143
  19. Very specific:

    leave the score field as Not clearly stated

    line 144
  20. Distinctive:

    do not invent or infer a number

    line 145
  21. Distinctive:

    If datasets are only partially visible:

    line 147
  22. Distinctive:

    Write a markdown file in the workspace unless the user specifies another path.

    line 153
  23. Distinctive:

    Prefer verified facts over broad summaries

    line 204
  24. Distinctive:

    Keep the table compact but useful

    line 208
  25. Distinctive:

    Add short notes when comparisons are not apples-to-apples

    line 209
  26. Distinctive:

    Always start with search and brief

    line 213
  27. Distinctive:

    Prefer papers with GitHub when deciding which ones to inspect first

    line 214
  28. Very specific:

    Use --head before --section

    line 215
  29. Distinctive:

    Read only the sections needed to recover datasets and scores

    line 216
  30. Distinctive:

    If the topic is broad, tell the user when the table mixes multiple subtask types

    line 217

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.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:

  1. Search recent papers with deepxiv search
  2. Brief all candidates with deepxiv paper <id> --brief
  3. Keep the relevant papers, prioritizing papers with GitHub/code
  4. Inspect promising papers with deepxiv paper <id> --head
  5. Read experiment-related sections with deepxiv paper <id> --section ...
  6. Extract datasets, evaluation setup, and reported scores
  7. 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 json

Default heuristics:

  • Use the user’s exact topic phrase first
  • Keep --limit high 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 json

2. Brief all candidates

For each arXiv ID, fetch:

deepxiv paper <arxiv_id> --brief

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:

deepxiv paper <arxiv_id> --head

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:

deepxiv paper <arxiv_id> --section Experiments
deepxiv paper <arxiv_id> --section Evaluation
deepxiv paper <arxiv_id> --section Results

Section selection guidance:

  • Start with Experiments or Evaluation
  • Read Results if the metrics are not clear
  • Read Introduction only if the task setup is still ambiguous
  • Read Appendix only 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, or Unknown
  • 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.md

Example:

agentic-memory-baseline-table-2026-04-01.md

Recommended 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 fragmented

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 --head before --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 Experiments

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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.