researcher
Skill0 starsChanged 7 months agoMITView on GitHub
Enterprise-grade deep research with multi-source synthesis, citation tracking, source credibility scoring, and verified reports. Use when user says "research", "deep dive", "investigate", "compare X vs Y", "analyze trends", "state of the art", or any question requiring 3+ sources. Not for simple lookups or debugging.
40 other projects use a version of this.
Adopted by
Most recently taken up by
- Jakeschincariol/closer-skilltheir own version, first seen Nov 8, 2026
- natgalla/context-historiantheir own version, first seen Nov 6, 2026
- AhmedAbdelfattah0/AI-Skillstheir own version, first seen Nov 4, 2026
- AlekseiUL/heisenberg-team-GPTtheir own version, first seen Nov 1, 2026
- AlekseiUL/heisenberg-teamtheir own version, first seen Nov 1, 2026
- Mazalucas/El-DT-Lightweight-Armytheir own version, first seen Oct 26, 2026
Used with
Projects with it also use build-premium-website, cost-reducer and 9 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.
yawningwhaleAISkillbuild-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
huyvpSkillcost-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
yawningwhaleAISkillinstantly-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
xfstudioSkilltrigger-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
ffsshhttiikkSkillscalability
Core foundational concepts and principles for Scalability
Also in 10 projects that use this
RoxenRobloxSkillyoutube-broll-maker
Generate 10-second B-roll footage of yourself doing an action using the Higgsfield MCP (Seedance 2.0). Upload one photo of yourself, describe the action ("typing on laptop", "walking at night"), pick from 5 cinematography style presets, get an MP4. Use when the user wants B-roll, cutaway footage, "me doing X" video, YouTube B-roll, or any image-to-video of themselves performing an action.
Also in 3 projects that use this
- +4 more from yawningwhaleAI
Other versions40 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 40
- keli-wen/agy-staff★ 828same name
- bitwize-music-studio/claude-ai-music-skills★ 589same name
- understudy-ai/understudy★ 461same name
- krzysztofdudek/ResearcherSkill★ 269same name
- antonbabenko/deliberation★ 181same name
- svy04/ballast★ 73same name
- timscheuerai/content-vault★ 38same name
- Jakeschincariol/closer-skill★ 33same name
- AlekseiUL/heisenberg-team★ 17same name
- maher-naija-pro/claude-researcher★ 13same name
30 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 repository13 other files it gives its agents.
- deploy-pipelineSkill
- ecommerce-builderSkill
- hackathon-copilotSkill
- know-meSkill
- memory-managementSkill
- obsidian-memory-syncSkill
- polymarket-multi-agentSkill
- polymarket-vps-opsSkill
- self-healingSkill
- self-improvementSkill
- strategy-preflightSkill
- trade-journalSkill
- visual-promptingSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 50
Create search query strategy with variants
- Distinctive: line 91
Below 50: Use with caution, flag for verification
- Distinctive: line 99
Document verification status per claim
- Distinctive: line 105
After triangulation, compare initial scope with actual findings:
- Distinctive: line 108
Should sections be reordered based on evidence strength?
- Distinctive: line 110
If outline changes, launch 2-3 targeted gap-filling searches (time-box to 2-5 min).
- Distinctive: line 132
If critique finds a critical knowledge gap, return to Phase 3 with targeted delta-queries (time-box 3-5 min).
- Distinctive: line 192
self-healing: If search tools fail, follow retry protocol
“Common” is measured: kept by at least 6 in 10 of the 36 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
Deep Researcher
Deliver citation-backed, verified research through a structured pipeline with source credibility scoring and progressive context management.
Autonomy Principle: Operate independently. Infer assumptions from context. Only stop for critical errors or incomprehensible queries.
Decision Tree
Request Analysis
+-- Simple lookup (1-2 searches)? --> Quick mode
+-- Standard analysis needed? --> Standard mode [DEFAULT]
+-- Critical decision / comprehensive? --> Deep mode
+-- Full review / "deep research"? --> UltraDeep modePipeline Overview
| Phase | Name | Quick | Standard | Deep | UltraDeep |
| 1 | SCOPE | Y | Y | Y | Y |
| 2 | PLAN | - | Y | Y | Y |
| 3 | RETRIEVE | Y | Y | Y | Y |
| 4 | TRIANGULATE | - | Y | Y | Y |
| 4.5 | OUTLINE REFINE | - | Y | Y | Y |
| 5 | SYNTHESIZE | - | Y | Y | Y |
| 6 | CRITIQUE | - | - | Y | Y |
| 7 | REFINE | - | - | Y | Y |
| 8 | PACKAGE | Y | Y | Y | Y |
Phase 1: SCOPE — Research Framing
- Core question — What exactly are we trying to answer?
- Sub-questions — Break into 2-5 searchable queries
- Constraints — Time period, geography, domain, credibility requirements
- Output format — Brief answer, structured report, comparison table, or recommendation
- Assumptions — List and validate
Phase 2: PLAN — Strategy Formulation
- Identify primary and secondary source types
- Map knowledge dependencies (what must be understood first)
- Create search query strategy with variants
- Plan triangulation approach
- Define quality gates for this specific topic
Phase 3: RETRIEVE — Parallel Information Gathering
CRITICAL: Execute ALL searches in parallel using a single message with multiple tool calls.
Query Decomposition (5-10 independent angles)
- Core topic (semantic) — Main concept exploration
- Technical details (keyword) — Specific terms, implementations
- Recent developments (date-filtered) — Last 12-18 months
- Academic/expert sources — Papers, formal analysis
- Alternative perspectives — Competing approaches, criticisms
- Statistical/data — Quantitative evidence, benchmarks
- Industry analysis — Commercial applications, market trends
- Limitations/failures — Known problems, edge cases
Parallel Execution
[Single message with multiple tool calls]
- WebSearch(query="core topic query")
- WebSearch(query="limitations and challenges")
- WebSearch(query="recent developments 2026")
- WebSearch(query="comparison alternatives")
- Agent(description="Academic deep dive", prompt="...")
- Agent(description="Industry analysis", prompt="...")Adaptive Completion (First Finish Search)
Proceed to Phase 4 when threshold reached:
- Quick: 5+ sources OR 2 minutes
- Standard: 10+ sources OR 5 minutes
- Deep: 20+ sources OR 10 minutes
- UltraDeep: 25+ sources OR 15 minutes
Source Credibility Scoring
Rate each source:
- 90-100: Peer-reviewed, official docs, primary data
- 70-89: Reputable publications, expert blogs, established companies
- 50-69: Industry articles, secondary analysis
- Below 50: Use with caution, flag for verification
Phase 4: TRIANGULATE — Cross-Reference
- Identify claims requiring verification
- Cross-reference facts across 3+ independent sources
- Flag contradictions or uncertainties
- Note consensus vs debate areas
- Document verification status per claim
Core claims must have 3+ independent sources. Flag any single-source information.
Phase 4.5: OUTLINE REFINEMENT
After triangulation, compare initial scope with actual findings:
- Did evidence reveal more important angles than originally scoped?
- Are there critical subtopics that weren't in the original plan?
- Should sections be reordered based on evidence strength?
If outline changes, launch 2-3 targeted gap-filling searches (time-box to 2-5 min).
Phase 5: SYNTHESIZE — Deep Analysis
- Identify patterns across sources
- Map relationships between concepts
- Generate insights beyond source material
- Build argument structures with evidence hierarchies
- Distinguish FACTS (from sources) from SYNTHESIS (your analysis)
Phase 6: CRITIQUE — Quality Assurance (Deep/UltraDeep)
Red team the research:
- What's missing? What could be wrong?
- What alternative explanations exist?
- What biases might be present?
Multi-persona critique:
- "Skeptical Practitioner" — Would someone doing this daily trust these findings?
- "Adversarial Reviewer" — What would a peer reviewer reject?
- "Implementation Engineer" — Can these recommendations actually be executed?
If critique finds a critical knowledge gap, return to Phase 3 with targeted delta-queries (time-box 3-5 min).
Phase 7: REFINE — Iterative Improvement (Deep/UltraDeep)
Address gaps from critique. Strengthen weak arguments. Add missing perspectives. Resolve contradictions.
Phase 8: PACKAGE — Report Generation
Brief Answer (Quick mode)
Respond conversationally with inline citations.
Structured Report (Standard/Deep/UltraDeep)
# Research: [Topic]
**Date**: YYYY-MM-DD
**Query**: [Original question]
**Confidence**: High/Medium/Low
**Mode**: Quick/Standard/Deep/UltraDeep
## Executive Summary
[200-400 words — lead with the answer]
## Key Findings
1. [Finding with citation]
2. [Finding with citation]
## Detailed Analysis
[Organized by sub-topic, prose-first (80%+ flowing text), evidence-rich]
## Synthesis & Insights
[Patterns, implications, second-order effects]
## Limitations & Caveats
[What we couldn't verify, potential biases]
## Recommendations
[Actionable next steps]
## Sources
1. [URL] — [description] — Credibility: XX/100
2. [URL] — [description] — Credibility: XX/100Writing Standards
| Principle | Rule |
| Precision | "reduced mortality 23% (p<0.01)" not "significantly improved" |
| Citation | Every factual claim cited in same sentence [N] |
| No vagueness | "5 RCTs (n=1,847) show" not "several studies suggest" |
| Prose-first | 80%+ flowing text, bullets only for distinct lists |
| No placeholders | Zero "TBD", "TODO", "Content continues..." |
| Admit uncertainty | "No sources found for X" not fabricated citations |
Integration Points
- ecommerce-builder: Phase 0.2 competitor research uses this protocol
- polymarket-multi-agent: Resolution-mechanics edge analysis
- visual-prompting: Competitor visual style research
- strategy-preflight: Market reality checks
- self-healing: If search tools fail, follow retry protocol
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.

