living-artifact SKILL.md skillA
living-artifact from qodexcli/qodex is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qodexcli/qodex/living-artifact@v0.1.0Pins v0.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qodexcli/qodex
- Path
examples/skills/living-artifact/SKILL.md- Versions recorded
- 1
- Latest version
- v0.1.0, committed Jun 29, 2026
- Size
- 4,346 bytes
- Repository stars
- 33
- License
- Apache-2.0
Build a visual artifact (dashboard, chart, table, page, mini-app) the RIGHT way — generate it, render it, screenshot it, have a vision model review it (LOOKS_GOOD / NEEDS_WORK / BROKEN), fix until it actually looks right, then serve it live with hot-reload. Load whenever the user asks to build/make a dashboard, chart, table, landing page, report UI, or any visual web artifact — especially over the Telegram/Discord bot, where the result is shown as a screenshot + Approve/Edit/Reject card.
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
# Living Artifact — build → review → fix → live You have a deterministic visual-QA loop. **Never** hand the user an unrendered blob of HTML and call it done — drive it through the loop so what they get is verified to actually render. ## The loop (do every step, in order) 1. **Create.** Generate a single self-contained artifact and save it: `artifact_create` with `type` (`html` / `react` / `vue` / `svg`) + the full content. Keep it self-contained (inline styles/scripts, a CDN for charts is fine). For "a sales dashboard with a chart and a table": real-looking sample data, one chart, one table, a clean responsive layout. 2. **Go live early.** `artifact_live id=<id>` — this starts the hot-reload server and returns the URL. Doing it now means every later fix the user sees update in place. 3. **Render + screenshot.** `artifact_preview id=<id>` → `browser_navigate <preview url>` → `browser_screenshot`. Also grab `browser_console` (console + page errors). 4. **Review (vision).** `artifact_review id=<id> screenshot_path=<png> intent="<what it should be>"` with the console/page errors. It returns **LOOKS_GOOD / NEEDS_WORK / BROKEN** + concrete issues. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_o2256xzicektbydb/b22c161ff64d72d17bf598c9f44c8071babee5b6cbd00d3f5a9f3fe98b0531c8.json
Then /plugin install living-artifact@markdownregistry-o2256xzicektbydb in Claude Code. It installs v0.1.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add qodexcli/qodex/living-artifact@sha256:b22c161ff64d72d1The line at the top of this page pins the label v0.1.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_o2256xzicektbydb)
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 qodexcli/qodex/living-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 living-artifact from somewhere else? Ask it: where did my living-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 Jun 29, 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/living-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 (4346 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
qodexcli/qodex · 33 stars · license Apache-2.0 · pushed 2026-11-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_o2256xzicektbydb GET https://markdownregistry.com/api/v1/resolve?ref=qodexcli/qodex/living-artifact GET https://markdownregistry.com/api/v1/blob/b22c161ff64d72d17bf598c9f44c8071babee5b6cbd00d3f5a9f3fe98b0531c8
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.