wicked-garden-qe-acceptance-test-executor SKILL.md skillA
wicked-garden-qe-acceptance-test-executor from mikeparcewski/wicked-garden is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mikeparcewski/wicked-garden/wicked-garden-qe-acceptance-test-executor@git:20261012.d9976bbPins git:20261012.d9976bb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mikeparcewski/wicked-garden
- Path
skills/qe-acceptance-test-executor/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261012.d9976bb, committed Oct 12, 2026
- First version recorded
- Sep 11, 2026
- Size
- 7,929 bytes
- Repository stars
- 9
- License
- MIT
Follows structured qe test plans step-by-step, collecting evidence artifacts. Executes and captures only — does not judge or grade pass/fail. Writes evidence files to .wicked-qe/evidence/{run-id}/. Use when: acceptance test execution, evidence collection, test plan execution <example> Context: Test plan is ready and needs to be executed step by step. user: "Execute the acceptance test plan for the file upload feature." <commentary>Use acceptance-test-executor for mechanical step execution and…
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
# Acceptance Test Executor You follow structured test plans and collect evidence. You are deliberately simple: 1. **Execute each step** exactly as written 2. **Capture every artifact** specified in the evidence requirements 3. **Write evidence files** to the evidence directory 4. **Move to the next step** You do NOT judge whether results are correct. You do NOT decide pass/fail. You produce an evidence collection that a reviewer will evaluate independently. **Opened from `qe accept`**: you normally run as that pipeline's separate worker. Your evidence report goes back to `qe accept`, which saves it and continues to the isolated reviewer. It is an intermediate artifact, never the end of the caller's turn; when you run inline in the caller's turn, carry on with `qe accept`'s next step. ## Why You Don't Grade Self-grading creates false positives. When the same agent executes and evaluates, it pattern-matches "something happened" as success. By separating execution from evaluation, the system catches cases where: - Commands ran but produced wrong output - Files were created but contain incorrect content - Operations succeeded but had unintended side effects ## Process …
Read the whole file at its exact version.
How to install
mdr add mikeparcewski/wicked-garden/wicked-garden-qe-acceptance-test-executor@sha256:e068843adf5d3fd0The line at the top of this page pins the label git:20261012.d9976bb, 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_ifmtleou2xnxlmr3)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 11, 2026 and Oct 12, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.d9976bb latest | 2026-10-12 | d9976bb | 7,929 B | A | view · diff |
| git:20261011.ce0f7d9 | 2026-10-11 | ce0f7d9 | 7,595 B | A | view · diff |
| git:20261011.ffc4374 | 2026-10-11 | ffc4374 | 7,927 B | A | view · diff |
| git:20260911.3beb111 | 2026-09-11 | 3beb111 | 7,920 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 (7929 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
mikeparcewski/wicked-garden · 9 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ifmtleou2xnxlmr3 GET https://markdownregistry.com/api/v1/resolve?ref=mikeparcewski/wicked-garden/wicked-garden-qe-acceptance-test-executor GET https://markdownregistry.com/api/v1/blob/e068843adf5d3fd0619ebb7986637609d6618f5c93975b63609aa89c08f30724
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.