Individual skill
build-scenario-tests
Inspect an unfamiliar repository, turn a focused Markdown behavior scenario into a deterministic test in the repository's native test stack, run it, and preserve traceability between intent and code. Use when asked to add scenario tests, compile acceptance criteria or Given/When/Then Markdown into executable tests, reproduce a user-visible regression, or convert a narrow workflow specification into stable web, API, CLI, desktop, or mobile interaction coverage. Do not use for broad exploratory journeys or agent-judged smoke tests.
skills/build-scenario-tests/SKILL.md
Source commit 1be9984bdafbb68eaff400bdd82773a1d41ee7ec
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 227
- Repository last updated
- Aug 16, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- ai Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- claude-code-plugin Repository topic
- claude-skills Repository topic
- codex Repository topic
- codex-skill Repository topic
- hermes-agent Repository topic
- openclaw Repository topic
- operations Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 660 bytesSKILL.mdcore · 6,754 bytesagents/openai.yamlasset · 261 bytesexamples/cli-expired-session.scenario.mddoc · 1,378 bytesexamples/test_cli_expired_session.pyruns · 934 bytesexamples/web-workspace-invite.scenario.mddoc · 1,434 bytesexamples/web-workspace-invite.spec.tsruns · 1,611 bytesreferences/scenario-format.mddoc · 2,039 bytes
Read excerpt
# Build Scenario Tests
Compile one small behavior contract into deterministic, repository-native test
code. Understand the host project before choosing a harness, command, fixture,
selector, or assertion.
## Operating contract
- Treat repository instructions and existing tests as authoritative.
- Keep each scenario focused on one behavior and one reason to fail.
- Compile into the test stack the repository already uses. Add a dependency only
when no suitable harness exists and the user accepts the tradeoff.
- Make setup, inputs, actions, and expected results deterministic.
- Prefer public behavior over implementation details. Assert what a user or