quick-verify SKILL.md skillA
quick-verify 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/quick-verify@git:20261105.60e9622Pins git:20261105.60e9622 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/quick-verify/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261105.60e9622, committed Nov 5, 2026
- First version recorded
- Sep 24, 2026
- Size
- 2,924 bytes
- Repository stars
- 603
- License
- a license file GitHub does not identify
Use while working to confirm a change does what you meant before moving on. Observe its real effect the way a user or caller would, compare that with your intent, fix what is off, and observe again.
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
# Quick verify Code that compiles, and tests that pass, can still do the wrong thing. The only proof is the real effect, seen from where it matters. Run this loop yourself, between edits, in minutes. It is not a full QA pass; use `qa-and-verify` for that on a finished pull request. ## The loop 1. **Say what "working" looks like.** One or two sentences, in terms someone could see: "the settings page shows the new toggle, off by default", "`export --csv` writes a header row". If you cannot say it, you are not ready to check it. 2. **Pick the most faithful cheap way to observe it.** Look from where the effect lands: the screen a user sees, the response a caller gets, the file or row that gets written, the log a job emits. Prefer the tool the repository already uses. Find how to run things in `AGENTS.md`, the README, or the package scripts, and never invent a launch command. 3. **Produce the state.** Run the app, command, or job with realistic input. Reuse what is already running; stop only what you start. …
Read the whole file at its exact version.
How to install
mdr add dcouple/pane/quick-verify@sha256:f1a6912e6188654dThe line at the top of this page pins the label git:20261105.60e9622, 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_fsmcfh3rqdksoarf)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 24, 2026 and Nov 5, 2026, about one every 43 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261105.60e9622 latest | 2026-11-05 | 60e9622 | 2,924 B | A | view · diff |
| git:20260924.17234b5 | 2026-09-24 | 17234b5 | 2,691 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 (2924 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 · 603 stars · license a license file GitHub does not identify · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fsmcfh3rqdksoarf GET https://markdownregistry.com/api/v1/resolve?ref=dcouple/pane/quick-verify GET https://markdownregistry.com/api/v1/blob/f1a6912e6188654d456f50018a5b99ce0afbd8000bcbec895621ff62696b645a
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.