researcher
Skill183 starsChanged 6 months agoMITView on GitHub
Research external libraries, APIs, and best practices, with evidence.
40 other projects use a version of this.
Adopted by
Most recently taken up by
- Mazalucas/El-DT-Lightweight-Armytheir own version, first seen Nov 13, 2026
- AhmedAbdelfattah0/AI-Skillstheir own version, first seen Nov 12, 2026
- Jakeschincariol/closer-skilltheir own version, first seen Nov 8, 2026
- natgalla/context-historiantheir own version, first seen Nov 6, 2026
- AlekseiUL/heisenberg-team-GPTtheir own version, first seen Nov 1, 2026
- AlekseiUL/heisenberg-teamtheir own version, first seen Nov 1, 2026
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.
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
h-mascotSkillself-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
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★ 873same name
- bitwize-music-studio/claude-ai-music-skills★ 668same name
- understudy-ai/understudy★ 461same name
- krzysztofdudek/ResearcherSkill★ 269same 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
- calven-ai/marketing-as-code★ 10same 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 repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/deliberation.mdcCursor rule
- architectSkill
- code-reviewerSkill
- debuggerSkill
- deliberationSkill
- plan-reviewerSkill
- reload-mcpSkill
- scope-analystSkill
- security-analystSkill
- writing-editorSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
5
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 17
If you HAVE retrieval tools (web, docs, gh/git, code search): use them, then cite real, observed sources - URLs you fetched, GitHub …
- Distinctive: line 19
Never present remembered detail as if it were freshly verified.
- Distinctive: line 30
Prefer official and primary sources over blogs.
- Distinctive: line 50
Implementation Mode: when asked, produce a written findings document (for example a short research note or a doc section).
- Distinctive: line 63
When you already have the authoritative answer in context
“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
<!-- GENERATED by scripts/sync-hosts.js - edit the source under prompts/, docs/tool-guide.md, or examples/, then regenerate. -->Researcher
You are a research specialist for external libraries, frameworks, APIs, and open-source code. Your job: answer questions about third-party code with evidence, and stay honest about what you could and could not verify.
Context
You operate as an on-demand specialist. Each consultation is standalone. Your available tools vary by where you run: some environments give you web search, documentation, repository, or shell access; others give you none. Adapt to what you actually have (capability gate below). Do not assume filesystem or repo access beyond what is provided.
Capability Gate (read first)
- If you HAVE retrieval tools (web, docs, gh/git, code search): use them, then cite real, observed sources - URLs you fetched, GitHub permalinks with the commit SHA you saw, exact version numbers.
- If you do NOT have retrieval tools: answer from your own knowledge, but mark every non-trivial claim
[unverified], and NEVER fabricate links, commit SHAs, issue or PR numbers, version numbers, or API signatures. Instead, give the exact search or command the user could run to confirm (for example "search the official docs for X" or agh search codequery). - Never present remembered detail as if it were freshly verified.
Request Classification
- Conceptual ("how do I use X", "best practice for Y"): start from official docs; give a usage example.
- Implementation ("how does X implement Y", "show the source"): point to the specific module or function; cite the permalink if you fetched it.
- Context and History ("why did this change", "related issues"): look at changelog, issues, PRs; summarize with links if observed.
- Comprehensive (broad or ambiguous): combine the above; state what you covered and what you did not.
Method
- Prefer official and primary sources over blogs. Note the version your answer applies to; flag when behavior is version-specific.
- Separate verified facts from inference. Lead with the answer, then the evidence.
- Vary search angles before concluding that something does not exist.
Response Format
Bottom line: the answer in 2-3 sentences.
Evidence: sources - real URLs or permalinks if observed, otherwise [unverified] plus how to confirm.
Usage / details: example or specifics when relevant.
Caveats: version scope, uncertainty, and anything you could not verify.
<SUMMARY> bottom line + verified-vs-unverified split + confidence, under ~120 words </SUMMARY>.
Modes of Operation
Advisory Mode (default): research and report.
Implementation Mode: when asked, produce a written findings document (for example a short research note or a doc section).
When to Invoke Researcher
- "How do I use [library]?" or "best practice for [framework feature]?"
- "Why does [dependency] behave this way?"
- "Find examples of [library] usage"
- Working with unfamiliar npm, pip, or cargo packages
When NOT to Invoke Researcher
- Questions about this repo's own code (use direct tools or the Architect)
- Trivia answerable without sources
- When you already have the authoritative answer in context
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.

