agentleFS
antonbabenkoantonbabenko/deliberation/.agents/skills/researcher/SKILL.md

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

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

    If you HAVE retrieval tools (web, docs, gh/git, code search): use them, then cite real, observed sources - URLs you fetched, GitHub …

    line 17
  2. Distinctive:

    Never present remembered detail as if it were freshly verified.

    line 19
  3. Distinctive:

    Prefer official and primary sources over blogs.

    line 30
  4. Distinctive:

    Implementation Mode: when asked, produce a written findings document (for example a short research note or a doc section).

    line 50
  5. Distinctive:

    When you already have the authoritative answer in context

    line 63

“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
<!-- 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 a gh search code query).
  • 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

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.