Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Open pipeline for generating deep research trajectories with LLMs
.claude/skills/brycewang-stanford-open-researcher-guide/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✗→✓ | ▲ Improved | -9% | 0% |
| case-01 | ✗→✓ | ▲ Improved | -55% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -31% | 0% |
| case-04 | ✗→✓ | ▲ Improved | 92% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -28% | 0% |
OpenResearcher is a fully open pipeline for long-horizon deep research trajectory synthesis. It breaks complex research questions into sub-questions, iteratively searches and reads literature, builds internal knowledge representations, and synthesizes comprehensive answers. Unlike single-shot approaches, it models the researcher's thought process — reading, questioning, connecting, and refining understanding over multiple rounds.
pythonfrom open_researcher import OpenResearcher researcher = OpenResearcher(llm_provider="anthropic") # Complex research question result = researcher.research( "How do retrieval-augmented generation systems handle " "knowledge conflicts between parametric and retrieved knowledge, " "and what are the current mitigation strategies?" ) # Automatically decomposes into sub-questions: # SQ1: What types of knowledge conflicts occur in RAG? # SQ2: How are conflicts detected? # SQ3: What resolution strategies exist? # SQ4: How effective are these strategies?
python# Each sub-question triggers: # - Academic search (OpenAlex, arXiv) # - Paper reading (abstract + key sections) # - Evidence extraction # - Follow-up question generation # Configuration researcher = OpenResearcher( search_backends=["openalex", "arxiv"], max_iterations=5, # Research rounds per sub-question papers_per_iteration=10, # Papers to read per round follow_up_questions=True, # Generate follow-up questions )
python# Internally builds a knowledge representation: # - Claims linked to source papers # - Relationships between concepts # - Contradictions flagged # Access the knowledge graph kg = result.knowledge_graph print(f"Concepts: {len(kg.nodes)}") print(f"Relations: {len(kg.edges)}") print(f"Contradictions: {len(kg.contradictions)}")
python# Multi-section synthesis report = result.report # Sections: # 1. Introduction and scope # 2. Sub-question answers with evidence # 3. Cross-cutting themes # 4. Open questions and future directions # 5. Full bibliography report.save("research_report.md") report.export_bibliography("refs.bib")
pythonresearcher = OpenResearcher( llm_provider="anthropic", model="claude-sonnet-4-20250514", search_config={ "backends": ["openalex", "arxiv"], "max_results_per_query": 20, }, reading_config={ "sections": ["abstract", "introduction", "methods", "conclusion"], "max_tokens_per_paper": 3000, }, synthesis_config={ "style": "academic", # academic, technical, accessible "include_contradictions": True, "cite_inline": True, }, )
python# Inspect the research trajectory trajectory = result.trajectory for step in trajectory: print(f"Round {step.round}: {step.action}") print(f" Query: {step.query}") print(f" Papers read: {step.papers_read}") print(f" Key findings: {step.findings[:100]}...") print(f" Follow-ups: {step.follow_up_questions}")
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-02 | fail→pass | 17,973 | 10,014 | -44% | 1 | 1 | 0% | 2,744 | 2,507 | -9% | 0 | 0 | — |
case-01 | fail→pass | 35,892 | 24,777 | -31% | 1 | 1 | 0% | 7,206 | 3,263 | -55% | 0 | 0 | — |
case-03 | fail→pass | 25,486 | 8,358 | -67% | 1 | 1 | 0% | 4,138 | 2,870 | -31% | 0 | 0 | — |
case-04 | fail→pass | 8,761 | 10,127 | +16% | 1 | 1 | 0% | 1,595 | 3,069 | +92% | 0 | 0 | — |
case-05 | fail→pass | 16,638 | 6,244 | -62% | 1 | 1 | 0% | 2,887 | 2,085 | -28% | 0 | 0 | — |
case-06 | fail→pass | 12,938 | 5,077 | -61% | 1 | 1 | 0% | 2,395 | 1,838 | -23% | 0 | 0 | — |
case-07 | fail→pass | 14,847 | 4,987 | -66% | 1 | 1 | 0% | 2,419 | 1,858 | -23% | 0 | 0 | — |
case-08 | fail→pass | 11,171 | 7,263 | -35% | 1 | 1 | 0% | 2,105 | 2,200 | +5% | 0 | 0 | — |
case-09 | fail→pass | 12,284 | 2,258 | -82% | 1 | 1 | 0% | 1,834 | 1,376 | -25% | 0 | 0 | — |
case-10 | fail→pass | 8,921 | 4,442 | -50% | 1 | 1 | 0% | 1,578 | 1,514 | -4% | 0 | 0 | — |
case-11 | fail→pass | 8,558 | 2,787 | -67% | 1 | 1 | 0% | 1,660 | 1,494 | -10% | 0 | 0 | — |
case-12 | pass→pass | 5,398 | 2,901 | -46% | 1 | 1 | 0% | 792 | 1,347 | +70% | 0 | 0 | — |
case-13 | fail→pass | 14,350 | 3,023 | -79% | 1 | 1 | 0% | 2,012 | 1,434 | -29% | 0 | 0 | — |
case-14 | fail→pass | 12,391 | 5,431 | -56% | 1 | 1 | 0% | 1,838 | 1,908 | +4% | 0 | 0 | — |
case-15 | fail→pass | 8,073 | 3,666 | -55% | 1 | 1 | 0% | 1,481 | 1,409 | -5% | 0 | 0 | — |
case-16 | fail→pass | 10,533 | 3,510 | -67% | 1 | 1 | 0% | 1,678 | 1,460 | -13% | 0 | 0 | — |
case-17 | fail→pass | 14,973 | 2,910 | -81% | 1 | 1 | 0% | 2,582 | 1,406 | -46% | 0 | 0 | — |
case-18 | fail→pass | 13,179 | 3,226 | -76% | 1 | 1 | 0% | 2,308 | 1,434 | -38% | 0 | 0 | — |
case-19 | fail→pass | 14,013 | 3,316 | -76% | 1 | 1 | 0% | 2,205 | 1,489 | -32% | 0 | 0 | — |
case-20 | pass→pass | 11,626 | 12,106 | +4% | 1 | 1 | 0% | 1,863 | 2,683 | +44% | 0 | 0 | — |
case-21 | pass→pass | 7,825 | 10,339 | +32% | 1 | 1 | 0% | 1,692 | 2,616 | +55% | 0 | 0 | — |
case-22 | pass→pass | 8,819 | 9,612 | +9% | 1 | 1 | 0% | 1,871 | 2,499 | +34% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +82 percentage points is the difference between those two pass rates over the 22 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.