agentleFS
jonathanmalkinjonathanmalkin/jules/.claude/skills/research/SKILL.md

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

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.
  • truongtv22Skill

    Problem-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

  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • liufeng1976Skill

    setup-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

  • parcadeiSkill

    ast-grep-find

    AST-based code search and refactoring via ast-grep MCP

    Also in 4 projects that use this

  • SireJeffSkill

    context-optimize

    Context Optimization - Orchestrate RPI workflow TODO generation with interactive scoping

    Also in 4 projects that use this

  • +5 more from Lambenthan

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
  1. Very specific:

    Check Documents/Field-Notes/Research/ for an existing file matching the topic (fuzzy match on filename)

    line 22
  2. Distinctive:

    If found: read it, present the existing document, and offer: "Continue from [date] or start fresh?"

    line 23
  3. Distinctive:

    If not found: proceed to Phase 1

    line 24
  4. Very specific:

    If the user provides a topic directly (e.g., /research multi-agent systems), use that.

    line 30
  5. Distinctive:

    If no topic provided, ask: "What would you like me to research?"

    line 32
  6. Distinctive:

    If Context7 isn't configured, fall back to WebSearch + WebFetch.

    line 49
  7. Distinctive:

    Search for community discussion, questions, and solutions on the topic.

    line 57
  8. Distinctive:

    Search the topic on Hacker News, dev blogs, GitHub Discussions

    line 65
  9. Distinctive:

    Search for authoritative sources: official docs, research papers, expert blog posts.

    line 84
  10. Distinctive:

    If topic involves a known library, resolve-library-id → query-docs

    line 87
  11. Distinctive:

    If miss or not a library topic, skip to WebSearch

    line 88
  12. Distinctive:

    Search [Your Name]'s workspace for first-party experience on the topic.

    line 108
  13. Distinctive:

    Use a Sonnet subagent to merge all research outputs.

    line 130
  14. Distinctive:

    Source review is opt-in: Don't wait for approval unless [Your Name] asks to see sources.

    line 144
  15. Distinctive:

    Check against anti-patterns: em-dashes, hedge words, preamble, corporate chatbot

    line 160
  16. Very specific:

    Write the finished report to Documents/Field-Notes/Research/YYYY-MM-DD-<Topic-Slug>.md

    line 164
  17. Distinctive:

    Don't push chaining. Offer it once.

    line 178

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Check Documents/Field-Notes/Research/ for an existing file matching the topic (fuzzy match on filename)
  2. If found: read it, present the existing document, and offer: "Continue from [date] or start fresh?"
  3. 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 TypeToolWhy
Community discussion, opinions, experiencesReddit MCP (search_reddit, get_post_details)Direct access to threads and comments
General web search, news, blog postsWebSearch (built-in)Broad coverage, keyword-based
Library docs, API referencesContext7 (resolve-library-id → query-docs)Returns actual docs, prevents hallucinated APIs
Full page content extractionWebFetch with a descriptive promptPrompt 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_reddit with 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 Y

Agent 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 notes
  • Documents/Content-Pipeline/00-Seeds/ — session-mined seeds
  • .claude/plans/ — prior plans touching this topic
  • Code/ — 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:

  1. Deduplicate sources across agents
  2. Categorize findings: consensus views, contradicting positions, coverage gaps
  3. Identify where [Your Name]'s production experience adds something the internet doesn't have
  4. 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:

  1. The synthesized research from Phase 3
  2. The report template from references/report-template.md (if available)
  3. Technical register — practitioner voice, not academic
  4. 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

  1. Write the finished report to Documents/Field-Notes/Research/YYYY-MM-DD-<Topic-Slug>.md
  2. Save research artifacts alongside:
    • Documents/Field-Notes/Research/<Topic-Slug>/sources.md — full source inventory
    • Documents/Field-Notes/Research/<Topic-Slug>/research-notes.md — merged subagent outputs
  3. Present a 3-5 bullet summary of key findings.
  4. 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

PhaseModelRationale
Research dispatch (Agents A/B/C)HaikuData gathering, not synthesis
Source synthesisSonnetMerging and analysis needs quality
Report draftingSonnetVoice and structure
Voice checkInlineQuick pass, no subagent needed

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.