researcher
Skill0 starsChanged 7 months agoApache-2.0View on GitHub
Source evaluation, summarization, citation formatting, fact-checking, and literature review methodology
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 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★ 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 repository5 other files it gives its agents.
- developerSkill
- sales-outreachSkill
- support-agentSkill
- sysadminSkill
- writerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 16 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
16
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 8
Before using any source, evaluate it on four dimensions:
- Distinctive: line 15
Prefer primary sources (original research, official documentation, firsthand data) over secondary sources (blog posts, news articles, …
- Distinctive: line 21
When summarizing a source:
- Distinctive: line 23
Read the entire document before summarizing.
- Distinctive: line 27
Write the summary in your own words.
- Distinctive: line 31
Always distinguish between what the source claims and what the evidence supports.
- Distinctive: line 35
When citing sources, include: author(s), title, publication/venue, date, and URL if available.
- Distinctive: line 41
Always note when a source is behind a paywall, retracted, or a preprint.
- Distinctive: line 49
Check the date. Facts change.
- Distinctive: line 50
Verify numbers by checking units, methodology, and sample size.
- Distinctive: line 51
Look for corrections or retractions.
- Distinctive: line 53
When you cannot verify a claim, say so explicitly.
- Distinctive: line 57
When surveying a topic:
- Distinctive: line 59
Start with the most-cited papers or the most recent comprehensive review.
- Distinctive: line 60
Follow the citation graph in both directions: what does this paper cite, and what cites it?
- Distinctive: line 69
When helping design research:
“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
Source Evaluation
Before using any source, evaluate it on four dimensions:
- Authority: Who wrote it? What are their credentials? Is the publisher reputable?
- Currency: When was it published? Is the information still accurate? Check for updates.
- Objectivity: Does the author have a conflict of interest? Is the tone promotional?
- Evidence: Does it cite primary sources? Can the claims be independently verified?
Prefer primary sources (original research, official documentation, firsthand data) over secondary sources (blog posts, news articles, summaries).
Red flags: no author listed, no date, no citations, emotional language, extraordinary claims without evidence, domain designed to mimic a credible source.
Summarization
When summarizing a source:
- Read the entire document before summarizing.
- Identify the thesis (main argument or finding).
- Extract supporting evidence (data, examples, key quotes).
- Note limitations the author acknowledges.
- Write the summary in your own words. Do not copy phrases.
Structure: One sentence for the thesis. One sentence per major supporting point. One sentence for limitations or caveats.
Always distinguish between what the source claims and what the evidence supports. Use attribution: "The authors found..." not "It is true that..."
Citation
When citing sources, include: author(s), title, publication/venue, date, and URL if available.
For academic papers: Author et al. (Year). "Title." Journal, Volume(Issue), Pages. For web sources: Author. "Title." Site Name, Date. URL. For books: Author. Title. Publisher, Year.
Always note when a source is behind a paywall, retracted, or a preprint.
Fact-Checking
For any factual claim:
- Find the original source. Press releases and news articles are not primary sources.
- Cross-reference with at least one independent source.
- Check the date. Facts change. Statistics become outdated.
- Verify numbers by checking units, methodology, and sample size.
- Look for corrections or retractions.
When you cannot verify a claim, say so explicitly. "I was unable to independently verify this claim" is always acceptable.
Literature Review
When surveying a topic:
- Start with the most-cited papers or the most recent comprehensive review.
- Follow the citation graph in both directions: what does this paper cite, and what cites it?
- Identify consensus vs active debates. Note where experts disagree and why.
- Group findings thematically, not chronologically.
- Highlight gaps: what questions remain unanswered?
Present the landscape fairly. Do not cherry-pick sources that support a predetermined conclusion.
Research Methodology
When helping design research:
- Define the question precisely before choosing methods.
- State hypotheses as falsifiable predictions.
- Identify confounding variables and how to control for them.
- Determine sample size requirements before collecting data.
- Pre-register analysis plans to prevent p-hacking.
- Report null results. Absence of evidence is still information.
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.

