exploratory-test SKILL.md skillA
exploratory-test from tobihagemann/turbo is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tobihagemann/turbo/exploratory-test@git:20260927.fa1ba5aPins git:20260927.fa1ba5a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tobihagemann/turbo
- Path
codex/skills/exploratory-test/SKILL.md- Versions recorded
- 7
- Latest version
- git:20260927.fa1ba5a, committed Sep 27, 2026
- First version recorded
- Aug 21, 2026
- Size
- 7,977 bytes
- Repository stars
- 418
- License
- MIT
Execute multi-level exploratory testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios, plus usability observations through a UX lens reported separately from defects. Deeper than $smoke-test. Use when the user asks to "exploratory test", "test thoroughly", "test all scenarios", "deep test", "test edge cases", "test everything", "break it", "find bugs by testing", "test usability", or "check the UX while testing".
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
# Exploratory Test Execute multi-level exploratory testing that goes beyond smoke testing to actively find bugs through escalating test scenarios. ## Task Tracking At the start, use `update_plan` to track each step, restating any remaining steps of a parent workflow alongside them: 1. Load or create test plan 2. Determine testing approach 3. Run `$user-experience` skill (when user-facing) 4. Run `$test-run-rules` skill 5. Execute tests by level 6. Report ## Step 1: Load or Create Test Plan Resolve the test plan using these rules in order: 1. **Explicit path** — If a file path was passed, use it 2. **Explicit slug** — resolve to `.turbo/test-plans/<slug>.md` 3. **Anchoring artifact** — If the work under test is anchored to a plan, resolve to `.turbo/test-plans/<that-slug>.md` when that file exists 4. **Single file** — Glob `.turbo/test-plans/*.md`. If exactly one file exists, use it 5. **Most recent** — If multiple files exist, use the most recently modified 6. **Legacy fallback** — `.turbo/test-plan.md` if `.turbo/test-plans/` does not exist 7. **Nothing found** — run the `$create-test-plan` skill first, then use the plan it writes …
Read the whole file at its exact version.
How to install
mdr add tobihagemann/turbo/exploratory-test@sha256:73a79123d12b1226The line at the top of this page pins the label git:20260927.fa1ba5a, 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_mvxgpa4w6wgtzlqq)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Aug 21, 2026 and Sep 27, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260927.fa1ba5a latest | 2026-09-27 | fa1ba5a | 7,977 B | A | view · diff |
| git:20260924.de4f0f5 | 2026-09-24 | de4f0f5 | 16,082 B | A | view · diff |
| git:20260902.1c68e25 | 2026-09-02 | 1c68e25 | 11,442 B | A | view · diff |
| git:20260901.5deee81 | 2026-09-01 | 5deee81 | 11,106 B | A | view · diff |
| git:20260824.356a5a4 | 2026-08-24 | 356a5a4 | 10,443 B | A | view · diff |
| git:20260822.852fa9e | 2026-08-22 | 852fa9e | 10,035 B | A | view · diff |
| git:20260821.158606c | 2026-08-21 | 158606c | 9,633 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 (7977 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
tobihagemann/turbo · 418 stars · license MIT · pushed 2026-10-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mvxgpa4w6wgtzlqq GET https://markdownregistry.com/api/v1/resolve?ref=tobihagemann/turbo/exploratory-test GET https://markdownregistry.com/api/v1/blob/73a79123d12b122615ca3fc8197c55ead26653ef5754410354531906ad2a85a6
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 tobihagemann/turbo
Every file in tobihagemann/turbo