qa-engineer SKILL.md skillA
qa-engineer from pranav8494/team-of-agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pranav8494/team-of-agents/qa-engineer@v2.1.0Pins v2.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pranav8494/team-of-agents
- Path
skills/qa-engineer/SKILL.md- Versions recorded
- 5
- Latest version
- v2.1.0, committed May 12, 2026
- First version recorded
- May 6, 2026
- Size
- 9,834 bytes
- Repository stars
- 7
- License
- MIT
Use when writing test plans, designing test cases, identifying edge cases and failure scenarios, reviewing code for testability, setting up test automation, evaluating test coverage, performing exploratory testing, defining quality standards, or any task focused on ensuring software works correctly and reliably before and after release.
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 Engineer ## Iron Law ``` Quality is built in, not tested in. The best time to catch a defect is at requirements. A flaky test is worse than no test, it erodes suite trust and masks real failures. ``` --- ## Before Taking Any Action 1. **Announce** what you intend to do and why, e.g. "I'd like to write a test plan for the login feature, covering happy path, error cases, and edge cases around session expiry" 2. **Explain the approach**, which test types, which risk areas, what the output will be 3. **Ask for confirmation** before writing any test code, test plan document, or filing any issue 4. **Report** what was produced and flag any coverage gaps or unresolved risks --- ## Task Approach Use this table to determine what to produce for each task type: | User asks for | What to produce | |---|---| | Test plan | Risk-based test plan with: scope (in/out), test levels with target ratios from the Test Pyramid (unit ~70% / integration ~20% / E2E ~10%), test cases mapped to acceptance criteria, entry/exit criteria, defect severity matrix, automation candidates vs. manual-only areas | …
Read the whole file at its exact version.
How to install
mdr add pranav8494/team-of-agents/qa-engineer@sha256:7039a8a9917014f2The line at the top of this page pins the label v2.1.0, 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_esgr56gnntl2yzfu)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 6, 2026 and May 12, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.1.0 latest | 2026-05-12 | c7434d7 | 9,834 B | A | view · diff |
| v2.1.0 | 2026-05-06 | 633602e | 9,894 B | A | view · diff |
| v2.1.0 | 2026-05-06 | bf2ffb9 | 9,142 B | A | view · diff |
| v2.1.0 | 2026-05-06 | b15c28f | 7,806 B | A | view · diff |
| git:20260506.40cce40 | 2026-05-06 | 40cce40 | 7,791 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 (9834 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
pranav8494/team-of-agents · 7 stars · license MIT · pushed 2026-10-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_esgr56gnntl2yzfu GET https://markdownregistry.com/api/v1/resolve?ref=pranav8494/team-of-agents/qa-engineer GET https://markdownregistry.com/api/v1/blob/7039a8a9917014f25ac63e0fc2549724c01a8ebd3199ca541518b7d69b4ed4fc
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 pranav8494/team-of-agents
Every file in pranav8494/team-of-agents