Agent skill · research science · github
build-evidence-map
Build an auditable evidence map for a contested technical choice, research synthesis, proposal review, or consequential decision. Use when Copilot must preserve supporting, contradicting, qualifying, and missing evidence with exact source regions instead of collapsing disagreement into prose.
Why this skill is useful
Provides a structured approach to evidence mapping that includes specific commands and validation processes not commonly known to AI.
What it needs
Requires doubt-ai installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Build Evidence Map Turn one contested question into a portable decision artifact that shows what supports the current position, what pushes against it, and what remains unknown. Do not use a graph to decorate an answer that has not been sourced. For a simple factual claim or a general fact-checking request, use a verification workflow such as doublecheck instead. Use this skill when the relationships between evidence, intermediate claims, trade-offs, and missing facts matter. Workflow 1. Frame one decision. Write one falsifiable question and one provisional position. Narrow the question until a reader can identify what action or belief the map is testing. 2. Collect bounded source regions. Prefer direct observations and primary sources. Record the URL or absolute local path, publisher, publication date, retrieval date, section/page/line/timestamp locator, and a short checkable excerpt. Read references/evidence-ladder.md when source quality is disputed. 3. Atomize the reasoning. Create only four node types: position: the single current verdict; claim: an intermediate proposition; evidence: a faithful statement of one source region; unknown: a specific missing fact that could change the verdict. 4. Type every edge. Use supports, contradicts, qualifies, or missing. Add a plain-language note explaining why the source node bears on the target. Topical similarity is not support. Different scope, date, or population is not automatically a contradiction. 5. Preserve counterevidence. Do not delete contrary evidence because the provisional verdict survives it. Represent scope differences with qualifies edges. 6. Express uncertainty structurally. Do not invent confidence percentages. Add an unknown, narrow the position, or qualify a claim. 7. Write UTF-8 JSON with a .doubt.json suffix. Follow references/map-schema.md. Keep IDs short, stable, and semantic. 8. Validate fail-closed. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/build-evidence-map