evidence
Skill0 starsChanged 37 days agoMITView on GitHub
Calibrate every claim before it leaves the session: tag each factual clause Verified, Measured, Inferred or Planned, verify behaviour at the production sha, treat agent and bot output as a lead rather than evidence, read sources in full, compute a headline number twice, sweep every surface after one defect, and record what a source taught in a dated document. Triggers on: "verify", "is this true", "check the source", "what is the evidence", "at which sha", "production data", "sweep", a number about to be reported, a finding about to be filed, a summary or digest offered in place of a source, "confirmed", "resolved", "live", "100%", "on track".
8 other projects use a version of this.
Adopted by
Most recently taken up by
- magnusrodseth/dotfilestheir own version, first seen Nov 16, 2026
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
- jacksnxly/keryxtheir own version, first seen Nov 8, 2026
- pahlevikun/levistacktheir own version, first seen Nov 1, 2026
- adiutama/skillstheir own version, first seen Nov 1, 2026
- hoophq/hooptheir own version, first seen Oct 17, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- hoophq/hoop★ 861same name
- quickchatai/quickreview★ 9same name
- magnusrodseth/dotfiles★ 3same name
- ltlongtma/solo-sdlc★ 2same name
- SoFarSoGoodya/mathmodel-weave★ 2same name
- adiutama/skills★ 1same name
- jacksnxly/keryx★ 0same name
- pahlevikun/levistack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cut-ticketsSkill
- decision-recordsSkill
- deep-modulesSkill
- grill-planSkill
- plain-voiceSkill
- plan-projectSkill
- review-changeSkill
- setup-conventionsSkill
- test-firstSkill
- thin-slicesSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
4
Distinctive
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
- Distinctive: line 53
Never upgrade a level. Merged is not deployed.
- Distinctive: line 80
Before answering on a topic, open what is already established (the topic's memory or dated documents), lead with that, then add what is new.
- Distinctive: line 84
Before showing a deliverable, run the self-review in review-change (REVIEW-7).
- Distinctive: line 85
After a research task, write the dated document (EVID-10) before moving on.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Evidence
A claim is worth exactly what was done to check it. This skill fixes the vocabulary for how much
was done, and the handful of checks that turn a plausible sentence into a verified one. The other
skills cite these rules by id where they make a claim; the ids are stable and live in
rules/registry.json. The decider named across this set is the role that approves and gives
go-aheads: a role, not a person.
When to use
| Situation | Rule |
| A sentence states a fact about code, data, a system or a person's work | EVID-1 |
| The fact is about running behaviour | EVID-2 |
| The fact came from an agent, a retrieval system or a review bot | EVID-3 |
| A summary, digest or excerpt is on offer instead of the source | EVID-4 |
| A number is about to lead a message or a document | EVID-5 |
| One defect was just found | EVID-6 |
| A finding is about to be filed against someone else's code | EVID-7 |
| A file is about to be asserted or edited | EVID-8 |
| Custom code is about to be written | EVID-9 |
| A research task read a source that taught something | EVID-10 |
The tags
| Tag | Meaning | What earns it |
| Verified | the source was opened in this session | the file, log, record or page, read at the cited location |
| Measured | a number with the query that produced it | the command or query, repeatable |
| Inferred | reasoning from evidence, not the evidence itself | the premises named |
| Planned | intended, not done | a step in a plan |
Never upgrade a level. Merged is not deployed. Deployed is not verified in data. "Live", "100%", "PASS", "confirmed", "resolved" and "on track" need matching evidence; "green" is never a status. Give the sha, the date and the lane, or the gate.
The rules
| Id | Rule | What it means in practice |
| EVID-1 | Tag every claim | Each factual clause carries a tag; a reader treats an untagged clause as Inferred, which is rarely what was meant. Calibration is labelled honestly: "unverified", never blank. |
| EVID-2 | Verify at the production sha | file:line at the sha found from the live artifact or the deployment record, never a branch head or the latest tag. Behaviour comes from production data; dates from the deployment record. Code alone is a hypothesis; an absence claim needs data. |
| EVID-3 | Agent output is a lead | A sub-agent's quote, a retrieval hit or a bot's finding points at a line; the author opens that line before it is used. A quote is verbatim only after the author compared it. |
| EVID-4 | Read sources in full | A summary is a pointer to the source. Slice a large source rather than skip it. Say which sources were read in full and which were not. |
| EVID-5 | Compute a headline number twice | Second method, different path. Never divide counts from two systems with different identity models without the join. A number that moves between identical runs is a harness artefact (TEST-6). |
| EVID-6 | Sweep after one defect | Name the pattern, list every surface, report each as confirmed, not affected, or not checked. "Not checked" is a valid, honest row. |
| EVID-7 | Refute before filing | The second pass argues the other side. If the finding survives, file it with both passes shown. |
| EVID-8 | Re-read before asserting | Especially after checkout, stash or rebase, and before updating a change request whose state may have moved. |
| EVID-9 | Survey before building | Tool, data source, maintenance, fit: record it, name the pick. Custom code covers only the gap. A vendor's or partner's definition of a mechanism wins over a new mode. |
| EVID-10 | Record what a source taught | A dated document in the topic folder: question, sources (full or partial), method, findings with evidence, open questions, exact commands. Never overwrite the earlier one. |
Weighting evidence
Weight evidence by what it cost to produce: shipped code, then a written design, then a documented observation, then an opinion. A claim resting on the cheapest kind is Inferred until the costlier kind is opened.
How to apply in a session
- Before answering on a topic, open what is already established (the topic's memory or dated documents), lead with that, then add what is new.
- While working, tag as you write. An untagged clause reads as Inferred, which is rarely what was meant.
- Before showing a deliverable, run the self-review in review-change (REVIEW-7).
- After a research task, write the dated document (EVID-10) before moving on.
What a tagged paragraph looks like
The retry loop re-sends non-idempotent requests (Verified:
src/client/send.py:142at the production sha3f9c2ab, from the deployment record of 2026-10-08). It produced 17 duplicate orders last week (Measured:SELECT count(*) … WHERE created_at > '2026-10-01'on the production replica, re-computed from the payment provider's export: 17). The cause is the timeout after the server accepted the write (Inferred from the request logs; no direct evidence of the accept). A fix with an idempotency key is in review (Planned).
Four clauses, four tags, one number computed twice (EVID-5), the inference marked as an inference rather than upgraded to a finding (EVID-1).
Companion skills
| Need | Skill |
| The adversarial read before showing work | review-change |
| The words that need evidence, and the form of a verdict-first message | plain-voice |
| Where decision records and glossaries live | decision-records |
| Plans with assumptions tied to tests | plan-project |
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
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.

