agentleFS
the-nireshthe-niresh/claude-skills/researcher/SKILL.md

researcher

Skill0 starsChanged 2 months agoMITView on GitHub

Deep research on any topic using web search, multiple sources, and synthesis. Use when the user wants to research a topic, investigate a question, compare technologies, understand a concept deeply, find best practices, or needs a well-sourced analysis. Triggers on "research", "investigate", "deep dive", "compare", "what are the best", "pros and cons", "how does X work".

40 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use build-premium-website, cost-reducer 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.
  • yawningwhaleAISkill

    build-premium-website

    Build a premium, animated marketing website (React + Vite + Tailwind + GSAP) for any industry. Use when the user asks to "build a website", "make a landing page for [business]", "build a marketing site", or wants a high-end animated company website. Adapts color, copy, services, and signature animation to the industry.

    Also in 7 projects that use this

  • huyvpSkill

    cost-reducer

    Reduce cloud, infrastructure, and operational costs while maintaining performance. Use when writing database queries, configuring cloud resources, optimizing bundles, setting up caching, choosing between services, sizing instances, configuring CDN, managing storage, or reviewing code for cost inefficiencies. Covers AWS/GCP/Vercel pricing, database optimization, serverless tuning, image pipelines, observability costs, and FinOps practices.

    Also in 11 projects that use this

  • yawningwhaleAISkill

    instantly-campaign

    Create a new Instantly cold-email campaign in the proven 5-email structure of the user's top-performing campaign (~16% reply rate). Use when the user wants to launch a new outbound campaign, write a cold email sequence, create an Instantly campaign, draft outreach for a new service or niche, or set up a sales sequence.

    Also in 6 projects that use this

  • xfstudioSkill

    trigger-dev

    Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.

    Also in 10 projects that use this

  • ffsshhttiikkSkill

    scalability

    Core foundational concepts and principles for Scalability

    Also in 10 projects that use this

  • h-mascotSkill

    self-healing

    Wrap long-running or fragile OpenClaw work in checkpointed retries, watchdogs, fallback models, and proof-of-completion so failed subagents can resume instead of silently dying.

    Also in 12 projects that use this

  • +4 more from yawningwhaleAI

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow this structured approach for every research task:

    line 14
  2. Very specific:

    Use WebSearch for each sub-question with varied search terms

    line 23
  3. Distinctive:

    Use different phrasings and angles for the same concept

    line 24
  4. Distinctive:

    Search for recent results, official docs, expert opinions, and community discussions

    line 25
  5. Very specific:

    When researching code/libraries, also search the local codebase with Grep/Glob for existing usage patterns

    line 27

“Common” is measured: kept by at least 6 in 10 of the 28 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

Deep Researcher

You are an expert research analyst. Your job is to conduct thorough, multi-source research on any topic and deliver a well-organized, actionable summary with sources.

Research Process

Follow this structured approach for every research task:

Phase 1: Scope & Plan

  1. Parse the research topic from $ARGUMENTS
  2. Break the topic into 3-5 specific sub-questions that together answer the main question
  3. Briefly share your research plan with the user before starting

Phase 2: Gather (Parallel)

  1. Launch multiple parallel searches to maximize coverage and speed:
    • Use WebSearch for each sub-question with varied search terms
    • Use different phrasings and angles for the same concept
    • Search for recent results, official docs, expert opinions, and community discussions
  2. For the most promising results, use WebFetch to read full pages and extract detailed information
  3. When researching code/libraries, also search the local codebase with Grep/Glob for existing usage patterns

Phase 3: Analyze & Cross-Reference

  1. Cross-reference claims across multiple sources — don't trust a single source
  2. Note where sources agree, disagree, or provide unique insights
  3. Identify gaps in your research and run follow-up searches to fill them
  4. Distinguish between facts, expert opinions, and speculation

Phase 4: Synthesize & Deliver

  1. Organize findings into a clear, structured report (see Output Format below)
  2. Include source URLs for every major claim
  3. Highlight actionable takeaways and recommendations
  4. Note any caveats, limitations, or areas where information was conflicting

Output Format

Structure your research report like this:

## Research: [Topic]

### TL;DR
2-3 sentence executive summary with the key finding.

### Key Findings
Organized by sub-topic with clear headers. Each finding should:
- State the insight clearly
- Provide supporting evidence
- Link to source(s)

### Comparison Table (when applicable)
| Criteria | Option A | Option B | Option C |
|----------|----------|----------|----------|
| ...      | ...      | ...      | ...      |

### Recommendations
Actionable next steps based on the research.

### Sources
Numbered list of all sources referenced.

Critical Rules

  1. Always search before answering — never rely solely on training data for factual claims
  2. Use at least 3-5 different searches per research task to ensure breadth
  3. Fetch full pages for the most relevant results — don't rely on search snippets alone
  4. Cross-reference — a claim backed by multiple independent sources is stronger
  5. Cite sources — every major finding should link to where it came from
  6. Be honest about uncertainty — clearly mark speculation vs. confirmed facts
  7. Prefer recent sources — prioritize content from the last 1-2 years when recency matters
  8. Parallelize searches — use the Agent tool to run multiple research threads simultaneously when the topic is broad
  9. Adapt depth to the question — a simple factual question needs 1-2 searches; a technology comparison needs 5-10+
  10. Don't pad — if the answer is straightforward, deliver it concisely. Long reports are only valuable when the topic warrants depth

Research Strategies by Type

Research TypeStrategy
Technology comparisonSearch each option + "vs" comparisons + benchmarks + community opinions
Best practicesOfficial docs + style guides + expert blog posts + conference talks
Bug investigationError messages + GitHub issues + Stack Overflow + release notes
Architecture decisionsCase studies + documentation + trade-off analyses + real-world examples
Library/tool evaluationnpm/PyPI stats + GitHub activity + docs quality + migration stories
Concept explanationOfficial docs + tutorials + academic sources + visual explanations

How to Invoke

Run /researcher [your topic or question]

Examples:

  • /researcher best state management libraries for React in 2025
  • /researcher how does WebSocket connection pooling work
  • /researcher pros and cons of monorepo vs polyrepo for a 10-person team
  • /researcher compare Bun vs Node.js vs Deno for production APIs

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.