research
Skill65 starsChanged 7 months agoMITView on GitHub
Standalone research with persistence. Dispatches parallel research agents, synthesizes sources, produces structured findings with living documents for cross-session pickup. Use when user says "research", "look into", "deep dive", "investigate", or invokes /research. Do NOT use for quick lookups (just answer directly).
189 other projects use a version of this.
Adopted by
Most recently taken up by
- bamlab/flashlighttheir own version, first seen Nov 16, 2026
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- Suge8/friedbuntheir own version, first seen Nov 15, 2026
- Fractera/Agent-Engineering-Infrastructuretheir own version, first seen Nov 15, 2026
- Fractera/Agentic-Engineering-Infrastructuretheir own version, first seen Nov 15, 2026
- iha2/superlitetheir own version, first seen Nov 15, 2026
Used with
Projects with it also use Problem-Solving Techniques, daily-arxiv 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.
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 6 projects that use this
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
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 49 projects that use this
parcadeiSkillast-grep-find
AST-based code search and refactoring via ast-grep MCP
Also in 4 projects that use this
SireJeffSkillcontext-optimize
Context Optimization - Orchestrate RPI workflow TODO generation with interactive scoping
Also in 4 projects that use this
- +5 more from Lambenthan
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★ 325ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- The-Vibe-Company/quivr★ 40ksame name
- QuivrHQ/quivr★ 40ksame name
- udecode/plate★ 17ksame name
- openai/plugins★ 7.8ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- withcoral/coral★ 5ksame 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.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- buildSkill
- debugSkill
- financial-advisorSkill
- generate-image-openaiSkill
- good-morningSkill
- pdfSkill
- planeSkill
- reply-xSkill
- search-historySkill
- send-emailSkill
- simplify-julesSkill
- skill-creatorSkill
- stop-slopSkill
- thinkSkill
- watch-contactsSkill
- wrap-upSkill
- writeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. 0 are common, 14 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 170 edited versions we read keep these.
14
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Check Documents/Field-Notes/Research/ for an existing file matching the topic (fuzzy match on filename)
- Distinctive: line 23
If found: read it, present the existing document, and offer: "Continue from [date] or start fresh?"
- Distinctive: line 24
If not found: proceed to Phase 1
- Very specific: line 30
If the user provides a topic directly (e.g., /research multi-agent systems), use that.
- Distinctive: line 32
If no topic provided, ask: "What would you like me to research?"
- Distinctive: line 49
If Context7 isn't configured, fall back to WebSearch + WebFetch.
- Distinctive: line 57
Search for community discussion, questions, and solutions on the topic.
- Distinctive: line 65
Search the topic on Hacker News, dev blogs, GitHub Discussions
- Distinctive: line 84
Search for authoritative sources: official docs, research papers, expert blog posts.
- Distinctive: line 87
If topic involves a known library, resolve-library-id → query-docs
- Distinctive: line 88
If miss or not a library topic, skip to WebSearch
- Distinctive: line 108
Search [Your Name]'s workspace for first-party experience on the topic.
- Distinctive: line 130
Use a Sonnet subagent to merge all research outputs.
- Distinctive: line 144
Source review is opt-in: Don't wait for approval unless [Your Name] asks to see sources.
- Distinctive: line 160
Check against anti-patterns: em-dashes, hedge words, preamble, corporate chatbot
- Very specific: line 164
Write the finished report to Documents/Field-Notes/Research/YYYY-MM-DD-<Topic-Slug>.md
- Distinctive: line 178
Don't push chaining. Offer it once.
“Common” is measured: kept by at least 6 in 10 of the 170 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
Research
Standalone research with living documents. Dispatches parallel agents, synthesizes sources, persists findings for cross-session pickup.
You are doing deep investigation. Thorough, source-driven, opinionated about what matters. Not a Wikipedia summary machine.
Cross-Session Persistence
Research documents live at Documents/Field-Notes/Research/YYYY-MM-DD-<Topic-Slug>.md. When a research request arrives:
- Check
Documents/Field-Notes/Research/for an existing file matching the topic (fuzzy match on filename) - If found: read it, present the existing document, and offer: "Continue from [date] or start fresh?"
- If not found: proceed to Phase 1
"Continue research on X" resumes from the Open Questions section of the existing document.
Phase 1: Topic Selection
If the user provides a topic directly (e.g., /research multi-agent systems), use that.
If no topic provided, ask: "What would you like me to research?"
Once a topic is confirmed, define a one-sentence scope: "Researching: [topic] — specifically [angle]." Confirm with the user if the scope is ambiguous.
Research Tool Selection
Pick the right tool for the query type:
See .claude/rules/search-tools.md for the full tool routing guide. Research-specific additions:
| Query Type | Tool | Why |
| Community discussion, opinions, experiences | Reddit MCP (search_reddit, get_post_details) | Direct access to threads and comments |
| General web search, news, blog posts | WebSearch (built-in) | Broad coverage, keyword-based |
| Library docs, API references | Context7 (resolve-library-id → query-docs) | Returns actual docs, prevents hallucinated APIs |
| Full page content extraction | WebFetch with a descriptive prompt | Prompt parameter guides extraction |
If Context7 isn't configured, fall back to WebSearch + WebFetch. Don't block on missing tools.
Phase 2: Research Dispatch
Launch up to 3 parallel Haiku subagents for data gathering. Each agent returns structured findings.
Agent A: Community Research (Haiku)
Search for community discussion, questions, and solutions on the topic.
Reddit (use Reddit MCP tools):
search_redditwith the topic across: r/ClaudeCode, r/LocalLLaMA, r/ClaudeAI, r/MachineLearning- For top 3-5 posts by relevance, fetch full threads with
get_post_details(include comments) - Note: upvote counts, comment counts, recurring questions, contradicting answers
Hacker News / Dev Blogs (use WebSearch):
- Search the topic on Hacker News, dev blogs, GitHub Discussions
- 3-angle minimum (3 distinct search queries before reporting sparse results)
Return format:
## Community Sources
- [Source title](URL) — [1-sentence summary of the key finding] — [N upvotes/comments]
- ...
## Key Themes
- [Theme 1]: [what the community says]
- [Theme 2]: [what the community says]
## Contradictions
- [Source A] says X, but [Source B] says YAgent B: Documentation & Expert Research (Haiku)
Search for authoritative sources: official docs, research papers, expert blog posts.
Context7 for library/framework docs:
- If topic involves a known library, resolve-library-id → query-docs
- If miss or not a library topic, skip to WebSearch
WebSearch for:
- Official documentation on the topic
- Blog posts from recognized practitioners
- GitHub repos/issues with relevant implementations
Return format:
## Authoritative Sources
- [Source title](URL) — [Verified/Single-source] — [1-sentence finding]
- ...
## Technical Details
- [Key technical finding with citation]
- ...Agent C: Local Research (Haiku)
Search [Your Name]'s workspace for first-party experience on the topic.
Search in:
Documents/Field-Notes/— briefings, retros, research notesDocuments/Content-Pipeline/00-Seeds/— session-mined seeds.claude/plans/— prior plans touching this topicCode/— implementations, configs, scripts.claude/— skills, rules, agents (the Jules infrastructure itself)
Return format:
## First-Party Experience
- [File path] — [what [Your Name]'s setup does differently]
- ...
## Production Data Points
- [Specific metric, config, or outcome from the codebase]
- ...Phase 3: Source Synthesis
Use a Sonnet subagent to merge all research outputs. The synthesis agent should:
- Deduplicate sources across agents
- Categorize findings: consensus views, contradicting positions, coverage gaps
- Identify where [Your Name]'s production experience adds something the internet doesn't have
- Flag sources older than 6 months as potentially stale
Present a brief summary to [Your Name]:
Found N sources across community/docs/local. Key tension: [main disagreement]. Your edge: [what your setup reveals that others don't have]. Proceeding to draft — say "show sources" to review the full inventory.Save the full source inventory alongside the research document.
Source review is opt-in. Don't wait for approval unless [Your Name] asks to see sources. Proceed to drafting.
Phase 4: Report Drafting
Draft a structured research report using a Sonnet subagent with:
- The synthesized research from Phase 3
- The report template from
references/report-template.md(if available) - Technical register — practitioner voice, not academic
- A critical constraint: the "What I Think" section MUST reference specific files, configs, metrics, or experiences from [Your Name]'s actual setup (from Agent C's findings). No generic observations dressed up as personal experience.
Phase 5: Voice Check
Review the draft for AI writing patterns:
- Opening and close get full [Your Name] voice treatment (problem-I-hit opener, wry close)
- Analytical middle can be more informational (findings are data, not personality)
- Check against anti-patterns: em-dashes, hedge words, preamble, corporate chatbot
Phase 6: Save + Present
- Write the finished report to
Documents/Field-Notes/Research/YYYY-MM-DD-<Topic-Slug>.md - Save research artifacts alongside:
Documents/Field-Notes/Research/<Topic-Slug>/sources.md— full source inventoryDocuments/Field-Notes/Research/<Topic-Slug>/research-notes.md— merged subagent outputs
- Present a 3-5 bullet summary of key findings.
- Offer chain options when appropriate:
- "This is starting to look like a decision. Want to run /think?"
- "There's enough here to scope an implementation. Want to run /build?"
- "Ready to turn this into content? Want to run /write?"
- "Want to go deeper on [specific sub-topic]?"
- "I'll save this — pick it up later with 'continue research on [topic]'."
Don't push chaining. Offer it once. [Your Name] decides.
Model Guidance
| Phase | Model | Rationale |
| Research dispatch (Agents A/B/C) | Haiku | Data gathering, not synthesis |
| Source synthesis | Sonnet | Merging and analysis needs quality |
| Report drafting | Sonnet | Voice and structure |
| Voice check | Inline | Quick pass, no subagent needed |
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.

