agentleFS
openparallaxopenparallax/skills/researcher/SKILL.md

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

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

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
  1. Distinctive:

    Before using any source, evaluate it on four dimensions:

    line 8
  2. Distinctive:

    Prefer primary sources (original research, official documentation, firsthand data) over secondary sources (blog posts, news articles, …

    line 15
  3. Distinctive:

    When summarizing a source:

    line 21
  4. Distinctive:

    Read the entire document before summarizing.

    line 23
  5. Distinctive:

    Write the summary in your own words.

    line 27
  6. Distinctive:

    Always distinguish between what the source claims and what the evidence supports.

    line 31
  7. Distinctive:

    When citing sources, include: author(s), title, publication/venue, date, and URL if available.

    line 35
  8. Distinctive:

    Always note when a source is behind a paywall, retracted, or a preprint.

    line 41
  9. Distinctive:

    Check the date. Facts change.

    line 49
  10. Distinctive:

    Verify numbers by checking units, methodology, and sample size.

    line 50
  11. Distinctive:

    Look for corrections or retractions.

    line 51
  12. Distinctive:

    When you cannot verify a claim, say so explicitly.

    line 53
  13. Distinctive:

    When surveying a topic:

    line 57
  14. Distinctive:

    Start with the most-cited papers or the most recent comprehensive review.

    line 59
  15. Distinctive:

    Follow the citation graph in both directions: what does this paper cite, and what cites it?

    line 60
  16. Distinctive:

    When helping design research:

    line 69

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

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

Source Evaluation

Before using any source, evaluate it on four dimensions:

  1. Authority: Who wrote it? What are their credentials? Is the publisher reputable?
  2. Currency: When was it published? Is the information still accurate? Check for updates.
  3. Objectivity: Does the author have a conflict of interest? Is the tone promotional?
  4. 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:

  1. Read the entire document before summarizing.
  2. Identify the thesis (main argument or finding).
  3. Extract supporting evidence (data, examples, key quotes).
  4. Note limitations the author acknowledges.
  5. 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:

  1. Find the original source. Press releases and news articles are not primary sources.
  2. Cross-reference with at least one independent source.
  3. Check the date. Facts change. Statistics become outdated.
  4. Verify numbers by checking units, methodology, and sample size.
  5. 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:

  1. Start with the most-cited papers or the most recent comprehensive review.
  2. Follow the citation graph in both directions: what does this paper cite, and what cites it?
  3. Identify consensus vs active debates. Note where experts disagree and why.
  4. Group findings thematically, not chronologically.
  5. 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.

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.