qa-test SKILL.md skillA
qa-test from teambrilliant/dev-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add teambrilliant/dev-skills/qa-test@git:20260927.b9558d0Pins git:20260927.b9558d0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- teambrilliant/dev-skills
- Path
skills/qa-test/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260927.b9558d0, committed Sep 27, 2026
- First version recorded
- Apr 14, 2026
- Size
- 12,836 bytes
- Repository stars
- 5
- License
- none declared
Browser-based QA verification after any implementation. Use when someone says "QA this", "test this in browser", "verify the feature", "qa test", "browser test", or after /dev-skills:execute-plan to verify acceptance criteria in a real browser. Opens Chrome via MCP, exercises each acceptance criterion, verifies via DOM snapshots, and reports pass/fail. The "closer" for every implementation — proof it works, not just that tests pass.
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
# QA Test Verify implemented features in a real browser. Exercise each acceptance criterion, verify via snapshots, report results. **Context-efficient design**: browser testing runs in a sub-agent so snapshot/interaction data stays out of the main thread. Main thread only sees compact pass/fail summaries. **Sub-agent rule:** Always use sub-agents for browser interaction and pre-flight exploration — these are broad, multi-step tasks that generate significant context. Fan out pre-flight and browser testing as separate sub-agents when they're independent. Handle directly only when verifying a single, specific element or reading one file for criteria. ## Modes - **Agent mode** — invoked by `/dev-skills:execute-plan` or any unattended run. No questions to the user. Login and other setup go through the harness bypass the plan names (seeded session, test token, dev auth route). If there is none and the criterion can't be reached, return `BLOCKED: <what's needed>` for that criterion to the caller instead of waiting. - **Human mode** — invoked directly by a user who's at the keyboard. Interactive setup and "fix or expected?" questions are fine. ## Process …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5weue4e4wgls4sow/0fbd0ea33ba01711aa1dabb3bdfb4dbdddad6a20618dc44fdffbbc468f112fd8.json
Then /plugin install qa-test@markdownregistry-5weue4e4wgls4sow in Claude Code. It installs git:20260927.b9558d0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add teambrilliant/dev-skills/qa-test@sha256:0fbd0ea33ba01711The line at the top of this page pins the label git:20260927.b9558d0, 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_5weue4e4wgls4sow)
6 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 teambrilliant/dev-skills/qa-test 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 qa-test from somewhere else? Ask it: where did my qa-test 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 4 versions of this file, between Apr 14, 2026 and Sep 27, 2026, about one every 56 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260927.b9558d0 latest | 2026-09-27 | b9558d0 | 12,836 B | A | view · diff |
| git:20260609.05883da | 2026-06-09 | 05883da | 11,796 B | A | view · diff |
| git:20260419.9e33b7c | 2026-04-19 | 9e33b7c | 12,196 B | A | view · diff |
| git:20260414.7c5f774 | 2026-04-14 | 7c5f774 | 11,444 B | A | view |
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/qa-test/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 (12836 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
teambrilliant/dev-skills · 5 stars · license none declared · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5weue4e4wgls4sow GET https://markdownregistry.com/api/v1/resolve?ref=teambrilliant/dev-skills/qa-test GET https://markdownregistry.com/api/v1/blob/0fbd0ea33ba01711aa1dabb3bdfb4dbdddad6a20618dc44fdffbbc468f112fd8
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.