scenario-testing SKILL.md skillA
scenario-testing from aiskillstore/marketplace is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add aiskillstore/marketplace/scenario-testing@git:20260113.222b7dePins git:20260113.222b7de in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- aiskillstore/marketplace
- Path
skills/2389-research/scenario-testing/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260113.222b7de, committed Jan 13, 2026
- Size
- 3,327 bytes
- Repository stars
- 471
- License
- none declared
This skill should be used when writing tests, validating features, or needing to verify code works. Triggers on "write tests", "add test coverage", "validate feature", "integration test", "end-to-end", "e2e test", "mock", "unit test". Enforces scenario-driven testing with real dependencies in .scratch/ directory.
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 As stated in the principle: "A test that uses mocks is not testing your system. It's testing your assumptions about how dependencies behave." ## 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 …
Read the whole file at its exact version.
How to install
mdr add aiskillstore/marketplace/scenario-testing@sha256:bdf79e8405c66abbThe line at the top of this page pins the label git:20260113.222b7de, 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_uw2lydhjucv7vwwk)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jan 13, 2026.
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 (3327 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
aiskillstore/marketplace · 471 stars · license none declared · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uw2lydhjucv7vwwk GET https://markdownregistry.com/api/v1/resolve?ref=aiskillstore/marketplace/scenario-testing GET https://markdownregistry.com/api/v1/blob/bdf79e8405c66abb54984b0bd7f9b63f5b7b713bfa298e13ce972c3be08d9f0a
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 aiskillstore/marketplace
Every file in aiskillstore/marketplace