agentleFS
Hash-7777Hash-7777/Hash-Medical-Reasearch-Agent-Skills/skills/evidence-coverage/SKILL.md

evidence-coverage

Skill1 starsChanged 4 months agoMITView on GitHub

Check whether the retrieved evidence actually covers every concept in the question before answering — score the coverage, name the gaps, and re-retrieve when a core concept is missing instead of answering around it. Use after retrieval and before writing the answer.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    After retrieval, before composing the answer.

    line 14
  2. Distinctive:

    State the gap in the answer: If you answer with partial coverage (because re-retrieval found nothing), tell the reader which concept is …

    line 30

≈ “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

Evidence Coverage

An AI will happily answer a three-part question using evidence that covers only one part — and the reader can't tell. The gap is invisible in a fluent paragraph. This skill makes the agent check its own retrieval: does the evidence in hand actually touch every concept the question asked about? If a core concept has no supporting chunk, the honest move is to go back and search, not to improvise.

When to use

After retrieval, before composing the answer. Pairs naturally with query-planning: the concepts the planner produced are exactly what coverage checks against.

The rule

Before answering, map the question's concepts against the retrieved evidence. Score the coverage, list what's missing, and re-retrieve when a core concept has no support.

  1. List the concepts the question requires — the same concept groups from planning (drug, outcome, population, comparator), each expanded with its synonyms so a match counts even when the paper uses a different word.
  2. Mark each concept covered or missing — covered if at least one retrieved chunk genuinely addresses it (synonym match counts), missing otherwise.
  3. Score coverage — the fraction of concepts with support (0 to 1). A high-level number the reader and the agent can act on.
  4. Decide: answer or re-retrieve — re-retrieve when coverage is poor or when any core concept (not a peripheral qualifier) is missing. A missing core concept means the answer would be built on a hole.

Doing it well

  • Core vs peripheral. A missing comparator may be tolerable; a missing drug or outcome is not. Weight core concepts harder — losing one of them triggers re-retrieval on its own, even if the overall score looks fine.
  • Count synonym matches. Coverage that only matches exact words undercounts real support and forces needless re-retrieval. Expand each concept before checking.
  • Ignore filler. Generic academic words ("study", "effect", "results") are not concepts and must not count toward coverage.
  • State the gap in the answer. If you answer with partial coverage (because re-retrieval found nothing), tell the reader which concept is unsupported. An honest gap beats a confident guess.

Output

Question concepts:  metformin · all-cause mortality · heart failure · type 2 diabetes

  metformin            covered   (3 chunks)
  all-cause mortality  covered   (2 chunks)
  type 2 diabetes      covered   (2 chunks)
  heart failure        MISSING   (0 chunks)   ← core concept

Coverage: 0.75  →  re-retrieve for "metformin AND heart failure AND mortality"

The value is not the score. It is that the agent notices the hole before it writes a confident paragraph that pretends the hole isn't there.

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.