evidence-first-research

Produces graded research records and renders them into self-contained HTML reports.

2|Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Arasz/ai-badger --skill evidence-first-research-arasz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evidence-first-research
Source: https://github.com/Arasz/ai-badger/tree/main/features/common/skills/evidence-first-research
Command: npx skills add https://github.com/Arasz/ai-badger --skill evidence-first-research-arasz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Research reports often mix measured facts with guesses that look identical on the page, so unverified numbers get quoted as truth downstream. This Skill forces every finding to carry a provenance grade — MEASURED, READ, INFERRED, or UNVERIFIED — and its renderer refuses to produce a report from a badly graded record. ## Core Features & Use Cases - Graded findings: Every claim is tagged with one of four closed-set grades, with MEASURED and READ requiring an explicit Evidence line citing the command, conditions, or source. - Refusing renderer: A Python script validates the record and generates a self-contained HTML view with inline SVG charts (provenance mix, bars, line, matrix, range), writing only outside the repository. - Use Case: Investigating whether a CI gate is slow, you record each finding with its grade, render the report, and share a page where the reader sees at a glance that three findings were measured and one was never checked. ## Quick Start Ask the agent to research a question using the evidence-first-research skill and produce a dated, graded record with an HTML view.

Frequently Asked Questions about evidence-first-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a research report with evidence grades?

Write the question first, then record each finding under a Findings section with a claim ending in a grade bracket like [MEASURED] or [READ]. MEASURED and READ findings must include an Evidence line citing the command, conditions, or source path.

What are the MEASURED, READ, INFERRED, and UNVERIFIED grades?

They record your relationship to a claim: MEASURED means you ran it, READ means you read an authoritative source, INFERRED means you reasoned from cited inputs, and UNVERIFIED means you did not check. The grade describes provenance, not truth.

How do I render the research record to HTML?

Run python3 scripts/render_report.py on the markdown record. It validates all grades, writes a self-contained HTML page with inline SVG charts to a temp directory, and prints the path.

Why does the renderer refuse to write HTML inside the repository?

The markdown record is the artefact of record; a committed HTML view becomes a second source of truth that nobody can date. The script raises an error for any output target inside the repository tree.

What happens if a finding has no grade or no evidence?

The renderer refuses the record with an error naming the finding. MEASURED and READ findings without an Evidence line are rejected, and unknown grades are refused rather than passed through.

When should I not use evidence-first research?

Do not use it for locating code, tracing a single symptom, or reviewing a diff — those belong to codebase exploration, debugging, and review skills. Use it when the output is a set of findings someone else will rely on.