verify-app SKILL.md skillA
verify-app from dcouple/pane is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dcouple/pane/verify-app@git:20260924.17234b5Pins git:20260924.17234b5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dcouple/pane
- Path
main/src/services/paneChatBundle/skills/verify-app/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260924.17234b5, committed Sep 24, 2026
- Size
- 3,655 bytes
- Repository stars
- 577
- License
- a license file GitHub does not identify
Use when behaviour must be proven in the running application: journeys, screenshots for visual checks, external effects, or reproducing a bug. Never fixes.
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 app Prove what works with evidence, say what you could not determine, and leave a trail someone else can follow. A check you could not run is `undetermined`. It is never a pass. ## Set up 1. Confirm the target: branch or commit (including any uncommitted changes), worktree, journey numbers or check names, exact URL or route, expected results, and design reference. Use any navigation hints you are given. Report it if the target changes during verification. 2. Check tools and sign-ins before starting anything long: browser automation, the dev server or simulator, test accounts, and any connector needed to read back external effects. If something is missing, stop and report it as the reason. 3. Use test-mode keys, test accounts, local containers, and staging-safe endpoints. Never touch production unless the person explicitly asked. 4. Reuse the running app and authenticated session whenever possible. Start only the missing authorized services, record them, and keep to one server or listener per service. When you are dispatched for a focused check of named journeys, stay on those journeys; if it needs broad setup or repository investigation, report that to the caller. …
Read the whole file at its exact version.
How to install
mdr add dcouple/pane/verify-app@sha256:9087437874786f4bThe line at the top of this page pins the label git:20260924.17234b5, 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_57vsxpj3b4xklumn)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 24, 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 (3655 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
dcouple/pane · 577 stars · license a license file GitHub does not identify · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_57vsxpj3b4xklumn GET https://markdownregistry.com/api/v1/resolve?ref=dcouple/pane/verify-app GET https://markdownregistry.com/api/v1/blob/9087437874786f4bdb668414e401271a957d2d2090575a565702657598f811b9
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.