agentleFS
papersflow-aipapersflow-ai/papersflow-skills/skills/research-briefing/SKILL.md

research-briefing

Skill4 starsChanged 8 months agoMITView on GitHub

Build a focused literature and citation briefing from PapersFlow. Use when the user wants paper search, citation verification, related-paper discovery, or citation graph exploration.

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 6 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when a user wants a high-signal research briefing grounded in the hosted papersflow-mcp server.

    line 8
  2. Very specific:

    Start with search_literature for broad discovery.

    line 13
  3. Very specific:

    Use verify_citation when the user gives a citation string, DOI, URL, PubMed ID, arXiv ID, or uncertain bibliographic reference.

    line 14
  4. Very specific:

    Use find_related_papers when the user wants nearby work around a seed paper.

    line 15
  5. Very specific:

    Use get_citation_graph when the user wants a graph view with references, incoming citations, and optionally similar papers.

    line 16
  6. Very specific:

    Use get_paper_neighbors when the user wants a one-hop grouped view instead of a graph-first view.

    line 17
  7. Very specific:

    Use expand_citation_graph only after you already have seed node ids from a previous graph result.

    line 18
  8. Very specific:

    Use fetch when the user wants a richer single-paper record after search or graph exploration.

    line 19
  9. Distinctive:

    Prefer short grouped sections over long prose.

    line 23
  10. Distinctive:

    If the user asked for a graph-oriented answer, explicitly distinguish:

    line 25
  11. Distinctive:

    If the graph result looks noisy, say so instead of pretending the neighborhood is authoritative.

    line 29
  12. Distinctive:

    Prefer this when the user explicitly asks for a graph, network, map, or influence chain.

    line 56
  13. Distinctive:

    Prefer this over the graph tool when the user cares more about grouped lists than graph structure.

    line 65
  14. Distinctive:

    Do not guess node ids.

    line 74

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

Research Briefing

Use this skill when a user wants a high-signal research briefing grounded in the hosted papersflow-mcp server.

Workflow

  1. Resolve the user's target topic, title, DOI, or seed paper.
  2. Start with search_literature for broad discovery.
  3. Use verify_citation when the user gives a citation string, DOI, URL, PubMed ID, arXiv ID, or uncertain bibliographic reference.
  4. Use find_related_papers when the user wants nearby work around a seed paper.
  5. Use get_citation_graph when the user wants a graph view with references, incoming citations, and optionally similar papers.
  6. Use get_paper_neighbors when the user wants a one-hop grouped view instead of a graph-first view.
  7. Use expand_citation_graph only after you already have seed node ids from a previous graph result.
  8. Use fetch when the user wants a richer single-paper record after search or graph exploration.

Output Style

  • Prefer short grouped sections over long prose.
  • Include paper titles, years, identifiers, and why they matter.
  • If the user asked for a graph-oriented answer, explicitly distinguish:
    • references
    • later citations
    • similar papers
  • If the graph result looks noisy, say so instead of pretending the neighborhood is authoritative.

Tool Guidance

Use search_literature

Use for:

  • topic exploration
  • early-stage paper discovery
  • short lists of candidate seed papers

Use verify_citation

Use for:

  • checking a citation string
  • normalizing a DOI or paper URL
  • producing a reliable paper identifier before deeper exploration

Use get_citation_graph

Use for:

  • seed-centered graph exploration
  • showing how a paper connects to prior and later work

Prefer this when the user explicitly asks for a graph, network, map, or influence chain.

Use get_paper_neighbors

Use for:

  • concise grouped neighbors
  • "show me the references / citations / similar papers" requests

Prefer this over the graph tool when the user cares more about grouped lists than graph structure.

Use expand_citation_graph

Use only when:

  • you already have valid node ids from a previous graph result
  • the user wants to grow the graph one hop farther

Do not guess node ids.

Examples

  • User asks: "Find five strong papers on retrieval-augmented generation evaluation and tell me which one to start with."
  • User asks: "Verify this citation and give me a normalized version."
  • User asks: "Show me the citation graph around Attention Is All You Need."
  • User asks: "Expand the graph from these two node ids and tell me where the important branches are."

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.