principle-real-artifact SKILL.md skillA
principle-real-artifact from vraj-ai/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vraj-ai/skills/principle-real-artifact@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vraj-ai/skills
- Path
principles/principle-real-artifact/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 14, 2026
- Size
- 2,228 bytes
- Repository stars
- 3
- License
- MIT
Verify every claimed outcome against the real artifact — run the feature, read the actual value, inspect the diff — never against a proxy, a self-report, or a build pass. Apply after completing any task, before declaring done, and whenever reading evidence produced by a worker, a ticket, or a pipeline state.
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
# Principle: the real artifact Check the thing itself, not a proxy for it. "It compiles" is not behavior. "The worker said done" is a report. "State says green" is a claim. Only the running artifact answers the question. ## The rule | Claim | Proxy that proves nothing | The real check | |---|---|---| | The feature works | Build pass, typecheck, HTTP 200 on a health endpoint | Run the feature the way a user would; observe the output | | The fix landed | Worker's summary, ticket moved to done | `git log`, the diff at the head SHA, the gate run fresh | | The value is correct | A cached field, a derived metric, a screenshot of old state | Read the actual value from the live system | | The process is healthy | A status file, an uptime counter | Direct liveness evidence on the process itself | A model verdict is still a verdict. An agent's "I verified it" without an attached artifact is the same class of claim as a ticket's green state — treat both as unverified until the check has been re-run or its output read. ## Script the check when you can The strongest proof is a deterministic command that re-runs the same …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_7cxx6ofiada5kzaq/8b4407f778fb6133e2efeeffc4d2d6681768b6b3b1fbfc73a6cca4cd80aee39b.json
Then /plugin install principle-real-artifact@markdownregistry-7cxx6ofiada5kzaq in Claude Code. It installs v1.0.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add vraj-ai/skills/principle-real-artifact@sha256:8b4407f778fb6133The line at the top of this page pins the label v1.0.0, 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_7cxx6ofiada5kzaq)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in vraj-ai/skills/principle-real-artifact since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of principle-real-artifact from somewhere else? Ask it: where did my principle-real-artifact come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Oct 14, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/principle-real-artifact/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (2228 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
vraj-ai/skills · 3 stars · license MIT · pushed 2026-11-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7cxx6ofiada5kzaq GET https://markdownregistry.com/api/v1/resolve?ref=vraj-ai/skills/principle-real-artifact GET https://markdownregistry.com/api/v1/blob/8b4407f778fb6133e2efeeffc4d2d6681768b6b3b1fbfc73a6cca4cd80aee39b
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.