verify SKILL.md skillA
verify from talismansociety/talisman-web is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add talismansociety/talisman-web/verify@git:20261106.fbd93f4Pins git:20261106.fbd93f4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- talismansociety/talisman-web
- Path
.claude/skills/verify/SKILL.md- Versions recorded
- 17
- Latest version
- git:20261106.fbd93f4, committed Nov 6, 2026
- First version recorded
- Oct 15, 2026
- Size
- 56,570 bytes
- Repository stars
- 87
- License
- GPL-3.0
Drive the Talisman Portal (apps/portal, staking dashboard) the way a user does, in Docker containers of this worktree's own, which run the app server beside a browser with the Chrome Web Store Talisman wallet and the developer's test accounts, and prove that a change renders every portal route pixel-identical to the parity baseline and builds the same staking transactions. Use to verify a UI or flow change, reproduce a bug, connect a wallet, run the visual parity gate, the staking smoke lane…
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
# Verify the Talisman Portal The user surface is the Vite SPA in `apps/portal`. A connected visitor lands on `/staking/providers`; a visitor with no account stays on `/staking` behind the "Welcome to the Talisman Portal" guard. With Talisman installed, the portal asks the wallet for its Substrate accounts on every load, and the visitor connects an Ethereum account from the wallet side sheet. There is no sign-in, and the only backend is the Worker's Bittensor server functions. Each worktree, the main checkout included, verifies in containers of its own, and nothing it verifies runs on the host. An instance is one container `talisman-web-verify-<worktree>-<instance>` from the image `talisman-web-verify:<hash of docker/ and the backup>`. It holds Chromium with the production Talisman from the Chrome Web Store, the developer's wallet backup already restored and auto-lock off, agent-browser, and the app server. The browser loads the app server as `http://localhost:3002` from the container's own loopback, so every browser sees the same origin. …
Read the whole file at its exact version.
How to install
mdr add talismansociety/talisman-web/verify@sha256:d841093540c2d461The line at the top of this page pins the label git:20261106.fbd93f4, 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_cqum75rtf5aae66a)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 17 versions of this file, between Oct 15, 2026 and Nov 6, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261106.fbd93f4 latest | 2026-11-06 | fbd93f4 | 56,570 B | A | view · diff |
| git:20261103.2f6a9e2 | 2026-11-03 | 2f6a9e2 | 54,604 B | A | view · diff |
| git:20261103.e16cc33 | 2026-11-03 | e16cc33 | 54,586 B | A | view · diff |
| git:20261027.e9e267e | 2026-10-27 | e9e267e | 52,161 B | A | view · diff |
| git:20261024.d79c16b | 2026-10-24 | d79c16b | 52,065 B | A | view · diff |
| git:20261022.92c55ea | 2026-10-22 | 92c55ea | 51,818 B | A | view · diff |
| git:20261022.90876aa | 2026-10-22 | 90876aa | 51,818 B | A | view · diff |
| git:20261019.15a080a | 2026-10-19 | 15a080a | 49,757 B | A | view · diff |
| git:20261018.ff40ebe | 2026-10-18 | ff40ebe | 48,858 B | A | view · diff |
| git:20261018.33ce581 | 2026-10-18 | 33ce581 | 48,719 B | A | view · diff |
| git:20261017.5e3555a | 2026-10-17 | 5e3555a | 48,713 B | A | view · diff |
| git:20261017.fc78aed | 2026-10-17 | fc78aed | 48,408 B | A | view · diff |
| git:20261016.2c20f30 | 2026-10-16 | 2c20f30 | 48,005 B | A | view · diff |
| git:20261016.4f67492 | 2026-10-16 | 4f67492 | 45,188 B | A | view · diff |
| git:20261016.f9d9b0e | 2026-10-16 | f9d9b0e | 43,373 B | A | view · diff |
| git:20261015.8a630db | 2026-10-15 | 8a630db | 43,077 B | A | view · diff |
| git:20261015.672275b | 2026-10-15 | 672275b | 40,058 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 (56570 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
talismansociety/talisman-web · 87 stars · license GPL-3.0 · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cqum75rtf5aae66a GET https://markdownregistry.com/api/v1/resolve?ref=talismansociety/talisman-web/verify GET https://markdownregistry.com/api/v1/blob/d841093540c2d46152adb3c0c2cbaf53c2db43766d69150bc96a6d4eca79ed92
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.