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.
Profile →npx skills add github/awesome-copilot --skill build-evidence-map --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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](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 so
- Workflow
- Quality gates
- Deliver the result
node <skill-directory>/scripts/validate.mjs decision.doubt.json doubt map decision.doubt.json --out decision.html doubt verify decision.doubt.json \
What does the build-evidence-map skill do?
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.
How do I install it?
Run `npx skills add github/awesome-copilot --skill build-evidence-map --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.