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.
In this repository3 other files it gives its agents.
- citation-verifierSkill
- comparative-synthesisSkill
- deepscan-monitorSkill
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
- Very specific: line 8
Use this skill when a user wants a high-signal research briefing grounded in the hosted papersflow-mcp server.
- Very specific: line 13
Start with search_literature for broad discovery.
- Very specific: line 14
Use verify_citation when the user gives a citation string, DOI, URL, PubMed ID, arXiv ID, or uncertain bibliographic reference.
- Very specific: line 15
Use find_related_papers when the user wants nearby work around a seed paper.
- Very specific: line 16
Use get_citation_graph when the user wants a graph view with references, incoming citations, and optionally similar papers.
- Very specific: line 17
Use get_paper_neighbors when the user wants a one-hop grouped view instead of a graph-first view.
- Very specific: line 18
Use expand_citation_graph only after you already have seed node ids from a previous graph result.
- Very specific: line 19
Use fetch when the user wants a richer single-paper record after search or graph exploration.
- Distinctive: line 23
Prefer short grouped sections over long prose.
- Distinctive: line 25
If the user asked for a graph-oriented answer, explicitly distinguish:
- Distinctive: line 29
If the graph result looks noisy, say so instead of pretending the neighborhood is authoritative.
- Distinctive: line 56
Prefer this when the user explicitly asks for a graph, network, map, or influence chain.
- Distinctive: line 65
Prefer this over the graph tool when the user cares more about grouped lists than graph structure.
- Distinctive: line 74
Do not guess node ids.
≈ “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
Research Briefing
Use this skill when a user wants a high-signal research briefing grounded in the hosted papersflow-mcp server.
Workflow
- Resolve the user's target topic, title, DOI, or seed paper.
- Start with
search_literaturefor broad discovery. - Use
verify_citationwhen the user gives a citation string, DOI, URL, PubMed ID, arXiv ID, or uncertain bibliographic reference. - Use
find_related_paperswhen the user wants nearby work around a seed paper. - Use
get_citation_graphwhen the user wants a graph view with references, incoming citations, and optionally similar papers. - Use
get_paper_neighborswhen the user wants a one-hop grouped view instead of a graph-first view. - Use
expand_citation_graphonly after you already have seed node ids from a previous graph result. - Use
fetchwhen 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."
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.

