validate-knowledge SKILL.md skillA
validate-knowledge from llopresto87/cypress is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add llopresto87/cypress/validate-knowledge@git:20260930.dd7591dPins git:20260930.dd7591d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- llopresto87/cypress
- Path
skills/validate-knowledge/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260930.dd7591d, committed Sep 30, 2026
- First version recorded
- Aug 31, 2026
- Size
- 6,233 bytes
- Repository stars
- 121
- License
- MIT
Prove that a knowledge base actually works before trusting it — after building or adopting docs, a knowledge graph, or a wiki, verify it can orient a fresh agent and resist false premises. Use at the end of an adoption, after a large docs change, or before relying on the graph to route work. Two methods: clean-context test agents answering known-answer and adversarial questions, and enforcement tests that plant a violation and confirm the linter catches it. A smoke test proves code runs; this…
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
# validate-knowledge Documentation you wrote is documentation you already believe. That is exactly why you cannot validate it yourself: you fill every gap from memory the reader won't have. A knowledge base is only proven when a context that does *not* share your memory can use it to reach correct answers, and when its own guard rails demonstrably catch violations. This complements the code smoke test. A smoke test proves a snippet runs; this proves the surrounding knowledge is correct, navigable, and honest. For version drift specifically (whether the library wiki's pins still match the resolved dependencies), the complementary check is the lightweight source-reconciliation pass in `research-and-ingest`; this skill tests prose, not pin freshness. ## Method 1: clean-context test agents Spawn agents with **no prior context** on the project and have them answer questions using only the knowledge base. A fork of yourself inherits your assumptions and passes a base a stranger would fail. Grade the answers against ground truth you already know. 1. **Give them the entry point, not the answers.** Tell them to read the kernel and follow it, the same cold start a real session has. …
Read the whole file at its exact version.
How to install
mdr add llopresto87/cypress/validate-knowledge@sha256:94da01b1a9d3abccThe line at the top of this page pins the label git:20260930.dd7591d, 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_x6oaewgl5hhmccbc)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 31, 2026 and Sep 30, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260930.dd7591d latest | 2026-09-30 | dd7591d | 6,233 B | A | view · diff |
| git:20260915.df30567 | 2026-09-15 | df30567 | 6,814 B | A | view · diff |
| git:20260901.c8706d7 | 2026-09-01 | c8706d7 | 6,670 B | A | view · diff |
| git:20260831.6dde434 | 2026-08-31 | 6dde434 | 6,179 B | A | view |
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 (6233 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
llopresto87/cypress · 121 stars · license MIT · pushed 2026-10-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_x6oaewgl5hhmccbc GET https://markdownregistry.com/api/v1/resolve?ref=llopresto87/cypress/validate-knowledge GET https://markdownregistry.com/api/v1/blob/94da01b1a9d3abcc0d5e6094b0065009aa03d9cc854c292b60aaf2992a37e26d
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.