agentleFS
robertbradley-ossrobertbradley-oss/skills/research-brief/SKILL.md

research-brief

Skill2 starsChanged 2 months agoMITView on GitHub

Turn a research need into a self-contained assignment with scope, evidence requirements, comparisons, stopping conditions, and a useful deliverable. Use for planning or commissioning research, not automatically performing the investigation.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use weekly-review.

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.
  • QuixiAISkill

    weekly-review

    Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 1

    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:

    Write an assignment another researcher can execute without inheriting the conversation.

    line 8

“Common” is measured: kept by at least 6 in 10 of the 18 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

Research brief

Write an assignment another researcher can execute without inheriting the conversation. Match its depth to the question rather than forcing a paragraph, fixed subquestion count, or exhaustive research process.

Establish the job

Identify the question and end use: a decision, explanation, landscape, verification, or learning objective. Use known context and constraints. Ask when a missing end use or boundary would materially change the research; otherwise state reasonable assumptions and proceed.

Include only context the researcher needs. Specify relevant scope, exclusions, timeframe, geography, population, resource limits, and audience. Do not invent deadlines, budgets, or acceptance thresholds. Mark unresolved preferences explicitly when the brief can still be useful.

Define evidence and comparisons

Break the question into the subquestions needed to answer it. Choose source standards appropriate to each claim: primary documentation for capabilities, applicable records for historical facts, and actual participant accounts for experience. Treat vendor claims as claims until supported; source prestige does not compensate for the wrong population or time period.

For comparisons, define the common criteria, units, conditions, and relevant alternatives. Require material differences in coverage to be visible rather than forcing a ranking from incomparable evidence. Include contrary evidence and realistic alternatives to a favored hypothesis.

Require source pointers for consequential claims and distinguish facts, inferences, assumptions, and unresolved questions. Ask the researcher to trace repeated claims to their originating evidence where independence matters. Specify how to handle disagreement: compare definitions, dates, methods, and directness rather than resolving it by majority vote.

Make completion observable

Define sufficient coverage for the actual question. For a decision brief, each decisive criterion should have supported evidence or an explicit gap and its effect on the decision. For an exploratory landscape, state the search scope and coverage limits; do not promise exhaustive discovery without a bounded universe.

Require a final gap check focused on claims that could change the answer. Stop when the agreed scope and evidence requirements are met, further searching is unlikely to materially change the result, or the stated resource limit is reached. A time limit does not turn an unresolved claim into a finding. Negative searches should describe where and how the researcher looked, not imply that no evidence exists anywhere.

Deliver a runnable assignment

Return the brief in a format suited to its complexity, with the expected deliverable and what the final answer must make clear. Keep supported recommendations distinct from factual findings and request usable source links or locations. Do not perform the full investigation, dispatch another agent, or contact a researcher unless execution is also requested. If research is already authorized, use the brief as working context and continue rather than adding an approval gate.

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.