verify
Skill0 starsChanged 14 days agoApache-2.0View on GitHub
Check an existing answer claim by claim against source passages, recording reading depth and what can be verified. Use when a user wants to audit an answer against its sources.
189 other projects use a version of this.
Adopted by
Most recently taken up by
- abe238/hotinaitheir own version, first seen Nov 16, 2026
- SmartStudio/baize-bottheir own version, first seen Nov 15, 2026
- YuBan834/vrma-labtheir own version, first seen Nov 15, 2026
- Ju571nK/lodelinetheir own version, first seen Nov 15, 2026
- ericbust/namedroptheir own version, first seen Nov 15, 2026
- automagik-si/genietheir own version, first seen Nov 15, 2026
Used with
Projects with it also use instinct-export, instinct-import and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
TheKREATORSSkillinstinct-export
Export instincts from project/global scope to a file
Also in 3 projects that use this
TheKREATORSSkillinstinct-import
Import instincts from file or URL into project/global scope
Also in 3 projects that use this
AviadPSkillrisk-assess
Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).
Also in 3 projects that use this
diego-tobalinaSkillbuild-fix
Fix build and compilation errors systematically. Run when build fails.
Also in 6 projects that use this
AaravChadhaSkillsecure
Security review with a confidence gate - a finding exists only with a concrete exploit scenario and a high/medium/low confidence rating; everything else goes to a worth-hardening list, never inflated. Sweeps five surfaces: auth gates, secrets hygiene, injection and unsafe sinks, unsafe deserialization/crypto/transport, and LLM tool-use trust boundaries. Reports only, never fixes. Use when the user asks for a security review or to check vulnerabilities, secrets, or auth.
Also in 3 projects that use this
ArvorCoSkillspecify
Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.
Also in 10 projects that use this
- +1 more from TheKREATORS
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 189
- facebook/react★ 253ksame name
- react/react★ 252ksame name
- garrytan/gstack★ 142ksame name
- oven-sh/bun★ 97ksame name
- anthropics/financial-services-plugins★ 41ksame name
- anthropics/financial-services★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- anthropics/claude-quickstarts★ 19ksame name
- NVIDIA-NeMo/NeMo★ 19ksame name
179 more not listed
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 repositoryOne other file it gives its agents.
- searchSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Call the diotima status tool first and state the version in one line.
- Very specific: line 13
Quote, don't paraphrase: when calling find_passage.
“Common” is measured: kept by at least 6 in 10 of the 167 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
Verify an answer claim by claim
Call the diotima status tool first and state the version in one line.
Rules
- Propose, never decide. A claim is
supportsonly iffind_passagereturnedfound: truefor the verbatim quote it rests on. Otherwise it isnot verifiable. - Quote, don't paraphrase when calling
find_passage. - Two separate checks: the passage exists; the passage supports the claim (direction, effect size, CI, n, population, subgroup, timepoint, protocol vs. results).
- Declare reading depth (
full_text/abstract_only); quantitative claims resting only on an abstract arenot verifiable. - A CI that includes the null (1 for ratios, 0 for differences) is never "no difference".
- Missing access is reported, never hidden; disagreeing sources stay visible.
Verdicts: supports · partial · contradicts · insufficient · not verifiable
Steps
- Segment the answer into atomic claims C1, C2, ... keeping numbers, population, outcome and timepoint with the claim they belong to.
- Resolve each claim's source (DOI, PMID, URL, reference number). No source →
not verifiable: no source. - Obtain the source text (provided by the user or open access) and record reading depth.
- For each claim call
find_passagewith the verbatim sentence(s) from the source. - Compare claim and passage and assign a verdict with a one-line reason.
- Report per claim: claim → source → quote →
find_passageresult (found, offsets, SHA-256) → reading depth → verdict → reason. Then list numeric conflicts, and end with What is not verified.
To decide how many verdicts a human should re-check, use plan_recheck_sample and report
whether the plan is adequate. Diotima is not clinical decision support.
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.

