research-intelligence
Skill0 starsChanged 3 months agoMITView on GitHub
Use when the user wants a research question investigated with a verifiable, cited evidence trail — "research X", "deep research on Y", "investigate Z and show sources", "give me a report with citations", or wants a synthesized answer with confidence levels rather than a raw search dump. For a single named source only ("just search the web", "just check GitHub", "just check Reddit"), let that specific source skill trigger directly instead — don't route those through this orchestrator.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- sohaibdevv/Claude-Agentic-Skills2.0-versiontheir own version, first seen Jun 9, 2026
- vignesh2027/Claude-Agentic-Skills2.0-versiontheir own version, first seen May 20, 2026
- spitoglou/fabric-claude-skillstheir own version, first seen Jan 6, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- vignesh2027/Claude-Agentic-Skills2.0-version★ 6same name
- spitoglou/fabric-claude-skills★ 3same name
- sohaibdevv/Claude-Agentic-Skills2.0-version★ 2same name
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 repository10 other files it gives its agents.
- academic-researchSkill
- blog-researchSkill
- github-researchSkill
- news-researchSkill
- official-source-researchSkill
- reddit-researchSkill
- research-plannerSkill
- social-researchSkill
- source-verifySkill
- web-researchSkill
The file
Files
research-intelligence
Overview
Three stages: Planner → Router → Synthesizer. This file stays thin on purpose — sub-skills load only when actually dispatched, so a quick single-source request never pulls in the whole pipeline's token cost. See ../../ARCHITECTURE.md for the 13 locked rules everything below implements; this file doesn't restate them.
Stage 1 — Planner
Invoke research-planner. It decomposes the question into sub-questions, matches each to source skills, sets a search budget, and sets the stopping condition. For anything beyond quick-research, it confirms the drafted scope with the user before dispatch — a full pipeline can touch most of the 8 source skills and take a long time, and that's the cheap point to narrow it. Its output is a user-confirmed plan, written to the run's ledger — not evidence.
Stage 2 — Router
Dispatch the source skills the plan calls for: web-research, github-research, reddit-research, blog-research, news-research, academic-research, official-source-research, social-research. Invoke by name — never inline a source skill's procedure here; each loads only when actually needed for this run.
Each source skill writes evidence.jsonl records with verification_status: pending. When the plan's stopping condition is met (constitution rule 11: every sub-question meets its bar, or 2 consecutive rounds with no new evidence), collection ends for that run.
Then invoke source-verify on the full pending set — mandatory, no run skips this. It resolves every record to verified, rejected, or unreachable before anything downstream touches it.
Before synthesis, run the red-team pass (constitution rule 11): dispatch source skills again, this time with queries designed to refute the run's strongest emerging findings, not to confirm them. Any new evidence this surfaces goes through source-verify the same as anything else.
Stage 3 — Synthesizer
Build findings.jsonl from verified evidence per ../../engine/synthesis-contract.md: fact findings need ≥1 verified evidence id; interpretation/recommendation findings derive from other findings, and a recommendation's closure needs ≥1 verified fact (constitution rule 7). Every sentence traces to an evidence_id or a derived_from finding — no unattributed model claims (constitution rule 2).
Do not assign status by judgment — leave it null and let the validator compute it (constitution rule 3). Run python3 ../../scripts/validate_run.py --strict --write <run_dir> and fix findings until it passes clean; --write persists the computed status back to findings.jsonl so the renderer has real values to read, not null. That is what "done" means here.
--strict is the production setting, not an option: without it, warnings pass silently, and the warnings are where the "did you mean this?" cases live — evidence cited for context that doesn't count toward a bar, a finding sharing evidence with an open contradiction it doesn't list, two records with near-identical quotes filed under different roots. Run without --strict only while iterating.
Render the report with python3 ../../scripts/render_report.py <run_dir> — this is the actual implementation of constitution rule 10 ("the report always renders from findings.jsonl, never hand-written"). It reads findings.jsonl, evidence.jsonl, contradictions.jsonl, gaps.jsonl and run.json, and produces the report per ../../templates/report.md's section rules. Never write the report as free prose instead.
Choosing a workflow
Different research shapes need different Stage-2 depth. See ../../workflows/ for the parameterized versions of this same pipeline: quick-research.md (1 round, light verify), deep-research.md (loop-until-dry + red-team), competitive-research.md, market-research.md, technology-research.md, update-research.md (diffs against a prior run instead of starting fresh).
What never changes regardless of workflow
Every source skill produces evidence only (rule 1). Every record passes through source-verify before it can be cited (rule 6). Status is always validator-computed, never model-assigned (rule 3). The report always renders from findings.jsonl via the actual renderer, never free prose (rule 10). These hold in the 1-round quick workflow exactly as in the deepest one — only the budget, verify depth, and red-team pass scale.
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.

