qa SKILL.md skillA
qa from lamngockhuong/aiteamkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lamngockhuong/aiteamkit/qa@git:20261106.96eea03Pins git:20261106.96eea03 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lamngockhuong/aiteamkit
- Path
plugins/atk/skills/qa/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261106.96eea03, committed Nov 6, 2026
- First version recorded
- Oct 1, 2026
- Size
- 15,067 bytes
- Repository stars
- 12
- License
- MIT
Plan and write the team's testing: the project's master test plan, a plan per feature with scope and exit criteria, test cases traced to acceptance criteria, a regression matrix, and the handoff a developer owes QA. Afterwards, records a test run, raises its failures as bugs, and records a fixed bug's retest, and brings existing cases level with a changed spec. Use when a project starts testing, a feature reaches QA or has no written cases, a release needs a regression pass, the spec changed…
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 Planning and Test Cases (`atk:qa`) Produces test artifacts a QA engineer can execute without asking the developer what the feature was supposed to do. Every case traces back to an acceptance criterion, so untested criteria and untraced cases both become visible. ## Scope Handles: writing the project's master test plan and each feature's test plan, deriving test cases from acceptance criteria, adding negative and boundary cases, building the regression matrix from change impact, listing test data and environment needs, defining the QA entry and exit criteria, and afterwards recording what the team's own test execution found: the run record, its defects raised on the tracker, and the retest of a fixed bug. Does NOT handle: writing automated test code, which belongs to `atk:implement`; running the suite or executing the cases, which the testers do, or `atk:run-cases` where an agent executes them on a deployed environment and writes a run record this skill's `--bug` and `--retest` read like any other; deciding a result on the tester's behalf; or signing off a release (`atk:release`). ## Roles …
Read the whole file at its exact version.
How to install
mdr add lamngockhuong/aiteamkit/qa@sha256:39b400157cbcf281The line at the top of this page pins the label git:20261106.96eea03, 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_uvn7vl5noz7an2p4)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Oct 1, 2026 and Nov 6, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261106.96eea03 latest | 2026-11-06 | 96eea03 | 15,067 B | A | view · diff |
| git:20261022.a5e6ec1 | 2026-10-22 | a5e6ec1 | 15,412 B | A | view · diff |
| git:20261016.1a28b84 | 2026-10-16 | 1a28b84 | 13,623 B | A | view · diff |
| git:20261014.03c655e | 2026-10-14 | 03c655e | 13,555 B | A | view · diff |
| git:20261002.22b4c08 | 2026-10-02 | 22b4c08 | 13,351 B | A | view · diff |
| git:20261001.ed02384 | 2026-10-01 | ed02384 | 13,461 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 (15067 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
lamngockhuong/aiteamkit · 12 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uvn7vl5noz7an2p4 GET https://markdownregistry.com/api/v1/resolve?ref=lamngockhuong/aiteamkit/qa GET https://markdownregistry.com/api/v1/blob/39b400157cbcf2817973b4d01fe5aacb66a06a6541b4fc4d441122632ab93ca5
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.
More from lamngockhuong/aiteamkit
Every file in lamngockhuong/aiteamkit