research
Skill41 starsChanged 7 days agoMITView on GitHub
Use when finding sources through iterative web exploration and synthesis
- Reads credentials
189 other projects use a version of this.
Adopted by
Most recently taken up by
- dialog-db/dialog-dbtheir own version, first seen Nov 9, 2026
- howells/skillstheir own version, first seen Nov 8, 2026
- xiaoxiaosrm/dsh-mattpocock-skillstheir own version, first seen Nov 8, 2026
- Suge8/friedbuntheir own version, first seen Nov 8, 2026
- wowyuarm/dsh-agent-teamtheir own version, first seen Nov 8, 2026
- Contexera/dsh-agent-teamtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use daily-arxiv, exp-eval and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 5 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
truongtv22SkillProblem-Solving Techniques
Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.
Also in 5 projects that use this
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 43 projects that use this
skyllwtSkillexp-pilot-eval
Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.
Also in 4 projects that use this
skyllwtSkillexp-pilot-run
Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.
Also in 4 projects that use this
- +5 more from Lambenthan
- +1 more from skyllwt
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 189
- mattpocock/skills★ 309ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- udecode/plate★ 17ksame name
- openai/plugins★ 7.8ksame name
- ArcReel/ArcReel★ 6.3ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
- withcoral/coral★ 4.9ksame name
179 more not listed
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.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 169 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 38
When mmbridge is detected (see references/mmbridge-integration.md), dispatch mmbridge research in parallel with the internal researcher.
- Distinctive: line 65
Verify actual search counts before output.
- Very specific: line 83
When --engine legacy is set or $JINA_API_KEY is unavailable, replace "Jina Search" with "WebSearch" and "Jina Reader" with "WebFetch" in …
- Very specific: line 91
news: Add after:30d and prefer established editorial sources over blogs.
- Very specific: line 102
When --engine legacy or $JINA_API_KEY is unavailable:
- Very specific: line 107
When --interactive is set, skip Jina/WebFetch and use Playwright for every URL.
- Distinctive: line 117
Write the full brief using the Write tool and tell the user the saved path.
“Common” is measured: kept by at least 6 in 10 of the 169 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Resolve runtime paths before operations.
Iron Law
No guessing. If there is no data, collect it first.
Red Flags
- "This one article covers everything" → STOP. Single-source = blind spots. Depth minimums (3/5/10) exist for a reason.
- "I already know the answer, just need a citation" → STOP. Confirmation bias produces cherry-picked sources.
- "Source is from 2022 but topic hasn't changed" → STOP. Staleness must be verified, not assumed.
- "Skip the analyst step, just list links" → STOP. Raw link dumps without gap analysis are rejected.
- "Page was blocked so I'll summarize from the URL title" → STOP. Use fallback chain (Jina → Playwright → Gaps), never hallucinate from metadata.
Research
Autonomous multi-round web research that produces structured Research Briefs.
When to Use
- User asks to research a topic, trend, or question
- Another skill (e.g.,
/scc:write,/scc:analyze) needs source material - User wants competitive intelligence, market data, or literature review
Web Engine
The researcher uses Jina Search (s.jina.ai) as the primary tool. Fallback chain: Jina Search → WebSearch + WebFetch → the unblock chain (/scc:unblock, zero-key 9-phase) → Playwright. See references/jina-guide.md and docs/skills/unblock.md.
MMBridge Enhancement
When mmbridge is detected (see references/mmbridge-integration.md), dispatch mmbridge research in parallel with the internal researcher.
Dispatch
At Step 1, also run via Bash:
mmbridge research "<topic>" --type <type> --json > /tmp/mmbridge-research-${RUN_ID}.json--type code-aware: when topic relates to the current codebase--type open: for general topics unrelated to code--depth shallow: skip mmbridge--depth medium|deep: mmbridge enabled
Merge
At Step 3, parse the mmbridge JSON output file as supplemental source material. Count each distinct cited URL from mmbridge as one source and deduplicate overlaps during gap analysis.
Step-by-Step
- Auto-load
references/research-methodology.mdandreferences/jina-guide.md. - Dispatch researcher (sonnet): run depth-appropriate Jina Search calls with varied query phrasings. If
$JINA_API_KEYis unavailable, fall back to WebSearch + WebFetch. If mmbridge is available at medium or deep depth, dispatch it in parallel. - Validate sources: reject login walls, blocked pages, empty content. For blocked URLs, run the unblock chain (
node "<plugin-root>/skills/unblock/engine/cli.mjs" "<URL>" --json); read the trace before any retry. - Dispatch analyst (sonnet): merge internal and mmbridge findings, identify gaps, and apply conflict-resolution rules from
references/research-methodology.md. - Optional second round: only when depth allows and the analyst found critical gaps.
- Dispatch writer (sonnet): synthesize the final brief with conflict annotations.
- Verify actual search counts before output. If counts exceed the depth cap, discard excess results and re-synthesize.
Options
| Flag | Values | Default | Effect |
--depth | shallow|medium|deep | medium | HARD limit on search rounds — see Depth Behavior |
--sources | web|academic|news | web | Constrains search domain |
--lang | ko|en|auto | auto | Output language. When called from another skill (write, analyze), inherits the caller's --lang value. |
--interactive | flag | off | Force Playwright for all URL fetches (useful for SPAs, dashboards) |
--engine | jina|legacy | jina | jina: use Jina Search API. legacy: use WebSearch + WebFetch |
Depth Behavior
- shallow: EXACTLY 3 Jina Search calls. No deep reads. No gap analysis round.
- medium: EXACTLY 5 Jina Search calls plus up to 2 Jina Reader deep reads.
- deep: 10+ Jina Search calls, unlimited Jina Reader deep reads, and at most 3 gap-fill rounds before documenting remaining gaps.
When --engine legacy is set or $JINA_API_KEY is unavailable, replace "Jina Search" with "WebSearch" and "Jina Reader" with "WebFetch" in the above counts.
Coverage requirements and conflict resolution rules are in references/research-methodology.md.
Source Domain (--sources)
- web (default): General web search. No domain restrictions.
- academic: Bias at least half the calls toward Google Scholar or arXiv.
- news: Add
after:30dand prefer established editorial sources over blogs.
Fallback Chain
Jina Search (s.jina.ai) ─── primary: search + content in one call
└─ blocked/empty → Jina Reader (r.jina.ai) with X-Engine: browser
└─ still fails → Playwright (browser_navigate + browser_snapshot)
└─ unavailable → note in Gaps & LimitationsWhen --engine legacy or $JINA_API_KEY is unavailable:
WebSearch → WebFetch → Playwright → Gaps & LimitationsWhen --interactive is set, skip Jina/WebFetch and use Playwright for every URL.
Cost controls: Max 3 Playwright navigations per round. Exceeding the cap means skip the rest and note the gap.
Graceful degradation: Both Jina and Playwright are optional. If $JINA_API_KEY is missing, fall back silently. If Playwright MCP is unavailable, proceed without it and note unreachable URLs.
Auto-Save
- Path:
.captures/research-{slug}-{YYYY-MM-DD}.md {slug}= topic lowercased, spaces to hyphens, max 40 chars- Write the full brief using the Write tool and tell the user the saved path.
Gotchas
| Failure Mode | Mitigation |
| Stops after 1 search | researcher MUST meet depth minimums: shallow=3, medium=5, deep=10. Fewer = restart. |
| Lists links without analysis | analyst step is required. Raw link dumps are rejected. |
| Hallucinated sources | Every URL must come from an actual Jina Search/WebSearch result. writer cannot invent URLs. |
| Duplicate queries | researcher must vary phrasing with synonyms and different angles per query. |
| Jina API key missing | Fall back to WebSearch + WebFetch silently. Do not error. |
Subagents
researcher: { model: sonnet, tools: [Bash, WebSearch, WebFetch, browser_navigate, browser_snapshot], constraint: "Jina Search when $JINA_API_KEY set, else WebSearch+WebFetch; meet depth minimums, vary phrasing, validate content, flag staleness; Playwright only when Jina+WebFetch both fail; max 3 navigations" }
analyst: { model: sonnet, tools: [], constraint: "produce gap list, flag data conflicts, verify coverage requirements" }
writer: { model: sonnet, tools: [], constraint: "every claim needs a source, no invented URLs, include conflict annotations" }Output & Integration
See references/research-methodology.md for output format template, extended gotchas table, and integration notes.
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.

