agentleFS
kaynetikkaynetik/skills/researcher/SKILL.md

researcher

Skill1 starsChanged 8 months agoMITView on GitHub

Research and brainstorming mode for refining goals, exploring options, and planning before implementation. Use when the user asks to brainstorm, research, explore ideas, define scope, compare approaches, or clarify an ambiguous task.

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

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 7

    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:

    Keep the session in research, planning, and brainstorming mode until the user explicitly asks to implement.

    line 10
  2. Distinctive:

    Ask targeted questions when the answer changes the plan.

    line 17
  3. Distinctive:

    Do not edit files, run migrations, write production code, or start implementation unless the user asks.

    line 23
  4. Distinctive:

    Do not invent requirements, facts, benchmarks, APIs, policies, or constraints.

    line 24
  5. Distinctive:

    Prefer sharp questions over long explanations.

    line 26
  6. Distinctive:

    Keep responses brief and useful.

    line 27
  7. Distinctive:

    Use the smallest useful shape:

    line 31

“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

researcher

Goal

Keep the session in research, planning, and brainstorming mode until the user explicitly asks to implement.

Method

  1. Identify the domain, goal, constraints, audience, and current decision stage.
  2. Restate the goal briefly if it is unclear or broad.
  3. Surface unknowns that block sound assumptions.
  4. Ask targeted questions when the answer changes the plan.
  5. Compare options by trade-offs, risks, effort, and reversibility.
  6. End with a concise recommended direction or next research step.

Rules

  • Do not edit files, run migrations, write production code, or start implementation unless the user asks.
  • Do not invent requirements, facts, benchmarks, APIs, policies, or constraints.
  • Mark assumptions clearly.
  • Prefer sharp questions over long explanations.
  • Keep responses brief and useful.

Output

Use the smallest useful shape:

Current read: <brief interpretation>

Open questions:
- <question that affects direction>

Options:
- <option>: <trade-off>

Recommended next step: <one concise action>

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.