Test Automation
revfactory/harness-100
A full test automation pipeline. An agent skill from revfactory/harness-100.
This skill should be used when writing tests, validating features, or needing to verify code works.
Install Scenario Testing
$ npx skills add aiskillstore/marketplace --skill scenario-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aiskillstore/marketplace scenario-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/2389-research/scenario-testing .claude/skills/scenario-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "scenario-testing" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/2389-research/scenario-testing into .claude/skills/scenario-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aiskillstore/marketplace/tree/main/skills/2389-research/scenario-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aiskillstore/marketplace --skill scenario-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aiskillstore/marketplace scenario-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/2389-research/scenario-testing .agents/skills/scenario-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "scenario-testing" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/2389-research/scenario-testing into .agents/skills/scenario-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aiskillstore/marketplace --skill scenario-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aiskillstore/marketplace scenario-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/2389-research/scenario-testing .cursor/skills/scenario-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "scenario-testing" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/2389-research/scenario-testing into .cursor/skills/scenario-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aiskillstore/marketplace.git --path skills/2389-research/scenario-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aiskillstore/marketplace --skill scenario-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aiskillstore/marketplace scenario-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/2389-research/scenario-testing .gemini/skills/scenario-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "scenario-testing" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/2389-research/scenario-testing into .gemini/skills/scenario-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aiskillstore/marketplace scenario-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aiskillstore/marketplace --skill scenario-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/2389-research/scenario-testing .github/skills/scenario-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "scenario-testing" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/2389-research/scenario-testing into .github/skills/scenario-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aiskillstore/marketplace --skill scenario-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aiskillstore/marketplace scenario-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/2389-research/scenario-testing .opencode/skills/scenario-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "scenario-testing" agent skill from https://github.com/aiskillstore/marketplace/tree/main/skills/2389-research/scenario-testing into .opencode/skills/scenario-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
scenario-testing- GitHub stars
- 430
- Used in
- 1 other repo
- Token cost
- ~830 tokens
- SKILL.md length
- 396 words
- Files
- 2
- Skills in repo
- 1,085
- Repo updated
- First seen
- Licence
- None found
At a glance
This skill should be used when writing tests, validating features, or needing to verify code works.
- Works in 4 steps: Write Scenarios in .scratch/ → Promote Patterns to scenarios.jsonl → Use Real Dependencies → …
- Add test coverage
- SKILL.md covers Core Principle, The Truth Hierarchy, When to Use This Skill and Required Practices, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Scenario Testing is an agent skill from aiskillstore/marketplace. 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.
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill-report.json`).
It sits in Testing & QA, covering End-to-end testing, Unit testing and Integration testing. The repository describes itself as: Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified.
When your agent uses it
- Add test coverage
- Validate feature
- Integration test
Example prompts
- “write tests”
- “add test coverage”
- “validate feature”
- “/scenario-testing”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Write Scenarios in .scratch/
- Promote Patterns to scenarios.jsonl
- Use Real Dependencies
- Independence Requirement
What it can do on your machine
Read from SKILL.md and the folder at commit 4ac52da. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Scenario Testing loads about 830 tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 396 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 396 words (~830 tokens).
“The Iron Law: "NO FEATURE IS VALIDATED UNTIL A SCENARIO PASSES WITH REAL DEPENDENCIES"”
- name
- scenario-testing
Files
SKILL.md and 1 other file in skills/2389-research/scenario-testing of aiskillstore/marketplace.
- SKILL.md
- skill-report.json
Open the folder on GitHubat commit 4ac52da
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in aiskillstore/marketplace, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Scenario Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Scenario Testing this skillaiskillstore/marketplace | 430 | 1 repos | ~830 | Automated safety check: Pass | None | |
| Test Automationrevfactory/harness-100 | 1.3k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Memstack Development Test Writercwinvestments/memstack | 423 | — | ~3.7k | Automated safety check: Pass | Proprietary | |
| Test Experteinverne/dotfiles | 121 | — | ~2.3k | Automated safety check: Pass | GPL-3.0 | |
| Recommending Test Layersbitwarden/ai-plugins | 154 | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| OpenROAD Module Test AdderThe-OpenROAD-Project/OpenROAD | 3.2k | — | ~1.8k | Automated safety check: Pass | BSD-3-Clause |
Similar skills
Memstack Development Test Writer
cwinvestments/memstack
A skill your agent uses when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with…
Test Expert
einverne/dotfiles
Testing methodologies, test-driven development (TDD), unit and integration testing, and testing best practices across multiple frameworks.
- Official
Recommending Test Layers
bitwarden/ai-plugins
A skill your agent uses when deciding WHICH new tests a change needs and at WHICH layer each belongs, working from a Jira key, a Testmo CSV, an assessing-test-coverage report, a PR, or a feature…
OpenROAD Module Test Adder
The-OpenROAD-Project/OpenROAD
Adds integration or unit tests to an OpenROAD module: writes the Tcl test, generates golden files and registers it in both CMake and Bazel.
- Official
Write Tests
grafana/synthetic-monitoring-app
Write Jest integration and unit tests for the Grafana Synthetic Monitoring app using React Testing Library, MSW, and src/test helpers.
More from aiskillstore/marketplace
All 1,085 skills in this repoCode Stats
aiskillstore/marketplace
Analyze codebase with tokei (fast line counts by language) and difft (semantic AST-aware diffs).
Data Processing
aiskillstore/marketplace
Process JSON with jq and YAML/TOML with yq. An agent skill from aiskillstore/marketplace.
Doc Scanner
aiskillstore/marketplace
Scans for project documentation files (AGENTS.md, CLAUDE.md, GEMINI.md, COPILOT.md, CURSOR.md, WARP.md, and 15+ other formats) and synthesizes guidance.
File Search
aiskillstore/marketplace
Modern file and content search using fd, ripgrep (rg), and fzf.
Find Replace
aiskillstore/marketplace
Modern find-and-replace using sd (simpler than sed) and batch replacement patterns.
Investigating Codebases
aiskillstore/marketplace
Automatically activated when user asks how something works, wants to understand unfamiliar code, needs to explore a new codebase, or asks questions like "where is X implemented?", "how does Y…
Related
Categories
Questions about Scenario Testing
What does Scenario Testing do?
This skill should be used when writing tests, validating features, or needing to verify code works. Scenario Testing is an agent skill from aiskillstore/marketplace. This skill should be used when writing tests, validating features, or needing to verify code works.
When should I use Scenario Testing?
Scenario Testing fits situations like: add test coverage; validate feature; integration test.
How do I install Scenario Testing in Claude Code?
Run `npx skills add aiskillstore/marketplace --skill scenario-testing -a claude-code`. Or copy the skill folder (skills/2389-research/scenario-testing in aiskillstore/marketplace) into .claude/skills/scenario-testing in your project. Claude Code loads it when a task matches its description.
How do I install Scenario Testing in Codex?
Run `npx skills add aiskillstore/marketplace --skill scenario-testing -a codex`. Or copy the skill folder (skills/2389-research/scenario-testing in aiskillstore/marketplace) into .agents/skills/scenario-testing in your project. Codex loads it when a task matches its description.
Can I use Scenario Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aiskillstore/marketplace --skill scenario-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scenario-testing, .gemini/skills/scenario-testing, .github/skills/scenario-testing and .opencode/skills/scenario-testing in your project.
What does Scenario Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Scenario Testing is instructions for the agent only.
Does Scenario Testing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Scenario Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Scenario Testing use?
No licence was found for Scenario Testing or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Scenario Testing use?
About 830 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Scenario Testing?
Skills that share tags, products or a category with Scenario Testing: Test Automation (revfactory/harness-100, 1.3k stars), Memstack Development Test Writer (cwinvestments/memstack, 423 stars), Test Expert (einverne/dotfiles, 121 stars) and Recommending Test Layers (bitwarden/ai-plugins, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Scenario Testing?
aiskillstore (a GitHub organization) maintains it in aiskillstore/marketplace, which has 430 GitHub stars. The repository holds 1,085 skills in this directory. The repository was last updated on October 7, 2026.
Source: aiskillstore/marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.