agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/research-brief/SKILL.md

research-brief

Skill1 starsChanged 25 days agoMITView on GitHub

Designs a focused research brief when a business question needs reliable evidence within practical limits.

20 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

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

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 3

    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:

    Use before commissioning desk research, fieldwork, surveys or expert conversations.

    line 9
  2. Distinctive:

    Create a workplan with dependencies, checkpoints and stop conditions.

    line 23
  3. Distinctive:

    Every research question links to the decision

    line 30

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

When to use it

Use before commissioning desk research, fieldwork, surveys or expert conversations.

What Claude needs

  • The decision the research must inform
  • Relevant context from client-context.md
  • Hypotheses or unknowns to test
  • Audience, deadline and available resources
  • Existing sources and evidence gaps

Method

  1. Translate the decision into primary and secondary research questions.
  2. Define scope boundaries by market, customer, geography, channel and time.
  3. Select suitable primary and secondary methods for each question.
  4. Specify source standards, sample logic and triangulation requirements.
  5. Create a workplan with dependencies, checkpoints and stop conditions.
  6. Record likely bias, access constraints and ethical considerations.

Output format

Provide sections for decision context, objectives, questions, scope, methods, source standards, workplan, risks and deliverables.

Quality checks

  • Every research question links to the decision
  • Methods are proportionate to the confidence required
  • Scope exclusions and evidence limitations are explicit

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.