research-verification SKILL.md skillA
research-verification from vecnode/vncode is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vecnode/vncode/research-verification@git:20261013.93412afPins git:20261013.93412af in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vecnode/vncode
- Path
packages/dsh-research/skills/research-verification/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261013.93412af, committed Oct 13, 2026
- Size
- 8,989 bytes
- Repository stars
- 10
- License
- AGPL-3.0
Work the verification ladder of a research run with rs_verify — read the ladder report before claiming anything is checked, run the two file rungs (r1-record, r2-locate) that need no reader, record the r3-support verdicts and strength verdicts that only a reader can make, tell a miss from an inconclusive, and know what a clean build will still refuse. Use when a document is written and about to be called checked, when a claim's quote does not match its source, or when a gate or build answers…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Verification is a ladder, not a verdict Five rungs, and each one can say exactly one thing. Knowing which rung said something is the whole skill; an agent that reports "checked" without naming the rung has told the user nothing. | rung | what it can say | who runs it | |---|---|---| | `r0-structure` | the document and its ledger agree | it runs by itself — the panel shows it and a build refuses on its errors | | `r1-record` | the stored bytes still hash to what was ingested; the record has the fields a reference needs; every field names its origin; the title it claims is in the text that was ingested | `rs_verify action=record` — a FILE check, no reader | | `r2-locate` | every claim's quoted passage really is in its source's stored text | `rs_verify action=record` — a FILE check, no reader | | `r3-support` | a located passage supports the sentence **at the strength it is written** | a READER — you — and this tool only records what you decided | | `r4-audit` | the same passages argued the other way | a READER, after an `r3-support` verdict exists | `action=support` and `action=audit` will not judge anything for you, and they are …
Read the whole file at its exact version.
How to install
mdr add vecnode/vncode/research-verification@sha256:d3d32c79909f7019The line at the top of this page pins the label git:20261013.93412af, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_4qqpk5bf3sp77j65)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 13, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8989 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
vecnode/vncode · 10 stars · license AGPL-3.0 · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4qqpk5bf3sp77j65 GET https://markdownregistry.com/api/v1/resolve?ref=vecnode/vncode/research-verification GET https://markdownregistry.com/api/v1/blob/d3d32c79909f7019dca08b21befa183423a212fe11b1469ee37e844d084e525b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.