scenario-testing SKILL.md skillA
scenario-testing from 2389-research/scenario-testing is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add 2389-research/scenario-testing/scenario-testing@git:20260706.af47101Pins git:20260706.af47101 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- 2389-research/scenario-testing
- Path
skills/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260706.af47101, committed Jul 6, 2026
- First version recorded
- Dec 5, 2025
- Size
- 2,909 bytes
- Repository stars
- 3
- License
- MIT
Proves features work through real-dependency scenario tests instead of mocks. Use when writing tests for new features, before declaring any feature complete, after fixing bugs that need verification, or when tempted to reach for mocks or unit tests as the primary validation.
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
# Scenario-Driven Testing for AI Code Generation ## Core Principle **The Iron Law**: "NO FEATURE IS VALIDATED UNTIL A SCENARIO PASSES WITH REAL DEPENDENCIES" Mocks create false confidence. Only scenarios exercising real systems validate that code works. ## The Truth Hierarchy 1. **Scenario tests** (real system, real data) = **truth** 2. **Unit tests** (isolated) = human comfort only 3. **Mocks** = lies hiding bugs ## When to Use This Skill - Validating new functionality - Before declaring work complete - When tempted to use mocks - After fixing bugs requiring verification - Any time you need to prove code works ## Required Practices ### 1. Write Scenarios in `.scratch/` - Use any language appropriate to the task - Exercise the real system end-to-end - Zero mocks allowed - Must be in `.gitignore` (never commit) ### 2. Promote Patterns to `scenarios.jsonl` - Extract recurring scenarios as documented specifications - One JSON line per scenario - Include: name, description, given/when/then, validates - This file IS committed ### 3. Use Real Dependencies External APIs must hit actual services (sandbox/test mode acceptable). Mocking any dependency invalidates the scenario. …
Read the whole file at its exact version.
How to install
mdr add 2389-research/scenario-testing/scenario-testing@sha256:0e3c529d8e96d679The line at the top of this page pins the label git:20260706.af47101, 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_ejtgk26ovgmeqvdx)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Dec 5, 2025 and Jul 6, 2026, about one every 106 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260706.af47101 latest | 2026-07-06 | af47101 | 2,909 B | A | view · diff |
| git:20260108.9680854 | 2026-01-08 | 9680854 | 3,327 B | A | view · diff |
| git:20251205.389da2d | 2025-12-05 | 389da2d | 3,236 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 (2909 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
2389-research/scenario-testing · 3 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ejtgk26ovgmeqvdx GET https://markdownregistry.com/api/v1/resolve?ref=2389-research/scenario-testing/scenario-testing GET https://markdownregistry.com/api/v1/blob/0e3c529d8e96d67987c8c77db00a1c585bc146a1f3fd362a441e3b308febd400
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 2389-research/scenario-testing
Every file in 2389-research/scenario-testing