agentleFS
LukehleLukehle/claude-quorum/skills/research-quorum/SKILL.md

research-quorum

Skill0 starsChanged 3 months agoMITView on GitHub

Verified research - delegating the mining to a research capability, then running verification and judging over its output rather than duplicating the search. Covers source verification, the citation-resolves check, distinguishing consensus from repetition, and reporting confidence honestly. Trigger on "research", "what's the landscape", "find out about", "is this claim true", "verify these sources", "literature review", "market scan", "check this research".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Do not report a research finding at a single confidence level.

    line 92

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 quorum

Research has a property most quorum subjects lack: checkable ground truth. A citation either resolves or it does not. A number either appears in the cited source or it does not.

That changes the shape. Per the corpus, generation with checkable ground truth is Mine → Verify, often with no judge panel at all — a panel over an uncontested check adds cost and no information.

It also changes who mines:

Route the mining to a research capability. Do not run five agents doing overlapping web searches. Judges score its verified output.


The shape

1. Delegate mining     -> a research skill/agent that searches broadly and cites
2. Extract claims      -> in code: pull every factual claim + its citation
3. Verify per claim    -> refuters resolve the citation and check the claim against it
4. Judge (optional)    -> only where the verified claims are contested or a decision hangs on them
5. Synthesize          -> report with per-claim confidence, and what could not be verified

Step 2 is the one people skip. A research report is not a finding; each claim inside it is. The unit of verification is the claim, not the document.


Extracting claims

Turn prose into a checkable list before verifying:

[
  {"claim": "NRR median compressed to ~101% in 2026",
   "citation": "data-mania.com/b2b-saas-benchmarks-2026",
   "type": "statistic"},
  {"claim": "Expansion drives 40-50% of new ARR at scale",
   "citation": "abacum.ai/rule-of-40-redefined",
   "type": "statistic"},
  {"claim": "Rule of 40 above 60% correlates with 2-3x higher valuations",
   "citation": "abacum.ai/rule-of-40-redefined",
   "type": "causal-ish"}
]

Type the claims, because they need different verification:

TypeVerified by
StatisticThe number appears in the source, with the same definition and period
FactThe source states it
CausalThe source actually establishes causation, not correlation
ConsensusMultiple independent sources, not one source repeated
ProjectionSource, vintage, and stated assumptions

Verification

The refuter resolves the citation and checks. Refute when:

  • The citation does not resolve — dead link, paywalled beyond the claim, or the page does not contain it
  • The source does not say it — the most common failure. The claim is a paraphrase that drifted
  • The definition differs — "NRR" in the source excludes a segment the claim includes
  • The period differs — a 2024 figure cited as current
  • Correlation restated as causation
  • The source is itself citing someone else — follow it. A blog citing a report citing a survey is one source, not three
  • The number is right but the context inverts it — a median presented as a target

Circular citation is the trap that matters

Five sources saying the same thing is not five sources when four of them cite the first. Trace every statistic to its origin. The verifier's question is not "do sources agree" but "how many independent measurements exist?"

Often the answer is one, and that changes how the claim should be reported.


Confidence, reported per claim

Do not report a research finding at a single confidence level. Grade each claim:

GradeMeans
VERIFIEDCitation resolves, source states it, definition and period match
PARTIALSource supports a weaker version — report the weaker version
SINGLE-SOURCEResolves and checks out, but only one independent origin
UNVERIFIEDCould not resolve or could not check
REFUTEDSource contradicts, or does not contain, the claim

PARTIAL is the most useful and most often skipped. "Rule of 40 above 60% correlates with 2-3× valuations" verifying down to "one 2026 analysis observed higher multiples among high scorers, without controlling for size" is a real result and a much weaker claim — and the weaker claim is the one to report.


When judges are worth seating

Skip them when the question is factual and the claims verified cleanly. Seat 2-3 when:

  • A decision hangs on the research, and the constraints differ (cost, risk, time-to-value)
  • Verified claims conflict — two credible sources disagree, which is a finding needing a ruling
  • The question is a recommendation ("which should we use"), not a fact

For a recommendations question, judge by signal quality, not mention count. Practitioner testimony with specifics, an expert publicly switching, and a measured benchmark all outrank volume — popularity in sources measures what is already popular, which is rarely what is best.


Synthesis

## What is established
- [VERIFIED] NRR median ~101% in 2026 — data-mania, from the SaaS Capital survey (n=1,000+)

## What is weaker than commonly stated
- [PARTIAL] Rule of 40 above 60% correlates with higher multiples — one 2026
  analysis, no size control. Directionally supported; the "2-3x" figure did not
  reproduce in the source.

## Single-source claims (treat with caution)
- [SINGLE-SOURCE] Expansion drives 40-50% of new ARR at scale — one origin,
  repeated by three downstream posts.

## Could not verify
- [UNVERIFIED] "Most finance teams plan to adopt AI agents by 2027" — the cited
  survey is paywalled; the claim does not appear in the public summary.

## Contradictions found
- Two sources give CAC payback benchmarks that differ by 6 months. They use
  different definitions (gross vs net margin). Both are right; the definitions
  are not interchangeable.

That last section is often the most valuable output. Contradictions in research are usually definitional, and surfacing the definitional split is worth more than picking a winner.


Related skills

  • quorum, quorum-verification, quorum-judging
  • decision-quorum — when the research feeds a call

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.