Agent skill

Test Runner

Execute the appropriate test suite (unit, Gherkin, e2e, smoke) and return structured results.

MITAuto-check passedTesting & QA

Install Test Runner

skills CLI

$ npx skills add EmeaAppGbb/spec2cloud --skill test-runner -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install EmeaAppGbb/spec2cloud test-runner --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/test-runner .claude/skills/test-runner && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "test-runner" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/test-runner into .claude/skills/test-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-runner", 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

$skill-installer install https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/test-runner

Type 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.

skills CLI

$ npx skills add EmeaAppGbb/spec2cloud --skill test-runner -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install EmeaAppGbb/spec2cloud test-runner --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/test-runner .agents/skills/test-runner && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "test-runner" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/test-runner into .agents/skills/test-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-runner", 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.

skills CLI

$ npx skills add EmeaAppGbb/spec2cloud --skill test-runner -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install EmeaAppGbb/spec2cloud test-runner --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/test-runner .cursor/skills/test-runner && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "test-runner" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/test-runner into .cursor/skills/test-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-runner", 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

$ gemini skills install https://github.com/EmeaAppGbb/spec2cloud.git --path .github/skills/test-runner

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add EmeaAppGbb/spec2cloud --skill test-runner -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install EmeaAppGbb/spec2cloud test-runner --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/test-runner .gemini/skills/test-runner && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "test-runner" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/test-runner into .gemini/skills/test-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-runner", 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.

GitHub CLI

$ gh skill install EmeaAppGbb/spec2cloud test-runner

Installs 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).

skills CLI

$ npx skills add EmeaAppGbb/spec2cloud --skill test-runner -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/test-runner .github/skills/test-runner && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "test-runner" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/test-runner into .github/skills/test-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-runner", 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.

skills CLI

$ npx skills add EmeaAppGbb/spec2cloud --skill test-runner -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install EmeaAppGbb/spec2cloud test-runner --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/test-runner .opencode/skills/test-runner && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "test-runner" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/test-runner into .opencode/skills/test-runner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-runner", 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: test-runner
GitHub stars: 100
Token cost: ~910 tokens
SKILL.md length: 348 words
Files: 1
Skills in repo: 38
Repo updated: Apr 16, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Execute the appropriate test suite (unit, Gherkin, e2e, smoke) and return structured results.

Works in 7 steps: Verify Aspire environment (for… → Determine test type — Select the test… → Run tests — Execute the command, capture… → …
Checking test status
SKILL.md covers Test Commands, Steps, Output Format and Aspire MCP Debugging Workflow, plus 2 more sections
Calls npx and npm

What it does

Test Runner is an agent skill from EmeaAppGbb/spec2cloud. Execute the appropriate test suite (unit, Gherkin, e2e, smoke) and return structured results. Use during Phase 3 (e2e test verification), Phase 4 (red baseline verification), Phase 5 (contract type compilation), Phase 6 (API/Web/integration slices), Phase 7 (smoke tests against deployment), and on resume (re-validate test state). Trigger when running tests, checking test status, or verifying test baselines.

Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering End-to-end testing, Test generation and QA and bug reports. It works with Model Context Protocol and Playwright. The licence is MIT.

When your agent uses it

Checking test status
Verifying test baselines

Example prompts

“/test-runner”

Requirements

Node.js

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

Verify Aspire environment (for Gherkin/e2e/smoke/all) — Before running integration tests, ensure the Aspire environment is running
Determine test type — Select the test suite based on current phase and task
Run tests — Execute the command, capture stdout and stderr
Parse results — Extract pass/fail counts, failure details, and test names
Detect flaky tests — If a test failed, re-run it once; if it passes on retry, flag as flaky
Diagnose failures with Aspire MCP — On test failure, use Aspire observability
Structure output — Format results for the orchestrator

What it can do on your machine

Read from SKILL.md and the folder at commit 8e76618. 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
Shell commands in SKILL.md call:
- npx
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx and npm, which can reach the network depending on how they are called.
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

Test Runner loads about 910 tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 348 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~106
When it runs · the whole SKILL.md, loaded when a task matches: ~910

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

The full file from EmeaAppGbb/spec2cloud at commit 8e76618, republished under its MIT licence (© EmeaAppGbb). 348 words, ~910 tokens.

Download SKILL.mdSave it as .claude/skills/test-runner/SKILL.md (or your agent's skills folder).

name: test-runner
description: Execute the appropriate test suite (unit, Gherkin, e2e, smoke) and return structured results. Use during Phase 3 (e2e test verification), Phase 4 (red baseline verification), Phase 5 (contract type compilation), Phase 6 (API/Web/integration slices), Phase 7 (smoke tests against deployment), and on resume (re-validate test state). Trigger when running tests, checking test status, or verifying test baselines.

Test Runner

Execute tests and return structured results for the orchestrator.

Test Commands

Type	Command
Unit (TypeScript)	`cd src/api && npm test`
Gherkin	`npx cucumber-js`
E2E	`npx playwright test --config=e2e/playwright.config.ts`
Smoke	`npx playwright test --grep @smoke`
All	`npm run test:all`

Steps

Verify Aspire environment (for Gherkin/e2e/smoke/all) — Before running integration tests, ensure the Aspire environment is running:
- Use aspire describe --format Json (or the Aspire MCP list_resources tool) to check resource status
- If resources are not healthy, run aspire start + aspire wait api --status healthy + aspire wait web --status healthy
- If resources show errors, use aspire logs <resource> (or list_console_logs) to diagnose
Determine test type — Select the test suite based on current phase and task
Run tests — Execute the command, capture stdout and stderr
Parse results — Extract pass/fail counts, failure details, and test names
Detect flaky tests — If a test failed, re-run it once; if it passes on retry, flag as flaky
Diagnose failures with Aspire MCP — On test failure, use Aspire observability:
- list_console_logs for resource stdout/stderr around failure time
- list_structured_logs for OpenTelemetry log entries
- list_traces to find the failing request's distributed trace
- list_trace_structured_logs with the trace ID for full request lifecycle
Structure output — Format results for the orchestrator

Output Format

Type: unit | gherkin | e2e | smoke | all
Pass: <count>
Fail: <count>
Flaky: <count>
Verdict: GREEN | RED | FLAKY

Failed tests:
- <test name>: <error message>

Aspire MCP Debugging Workflow

When tests fail against the Aspire environment:

1. list_resources              → Are all resources Running + Healthy?
2. list_console_logs(resource) → Any errors in stdout/stderr?
3. list_traces(resource)       → Find the trace for the failing request
4. list_trace_structured_logs  → Full trace lifecycle with all spans
5. execute_resource_command    → Restart a resource if stuck

Edge Cases

Test runner itself fails (not assertions) → report as infrastructure failure
Aspire resources unhealthy → restart via aspire start (auto-stops previous)
Tests exceed 5 minutes → check for hung processes
Always capture both stdout and stderr

Mandatory Completion Checklist

The orchestrator MUST verify ALL of the following before marking test-runner as complete:

All test suites were executed (unit, integration, e2e, Cucumber) — none skipped
Results include: total tests, passed, failed, skipped counts per suite
Any failures include file path, test name, and error message
Aspire environment was healthy during test execution (resources Running + Healthy)
If any tests failed, the failure is reported as a blocking issue — not silently ignored

BLOCKING: If the test runner itself fails (infrastructure failure, timeout, partial execution), this must be reported as "run incomplete" — not as "all tests passed".

Files

Just SKILL.md in .github/skills/test-runner of EmeaAppGbb/spec2cloud.

Open the folder on GitHubat commit 8e76618

Compare with similar skills

Test Runner 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.

Test Runner compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Test Runner this skillEmeaAppGbb/spec2cloud	100	—	~910	Automated safety check: Pass	MIT	5 mo ago
Glance TestDebugBase/glance	156	—	~827	Automated safety check: Pass	MIT	5 mo ago
Agentic Browser Testingpetrkindlmann/qa-skills	165	—	~4.5k	Automated safety check: Pass	MIT	3 mo ago
Record E2E Giflablup/backend.ai-webui	133	—	~907	Automated safety check: Notes	LGPL-3.0	today
Replica TestJakeschincariol/replica-skill	908	—	~819	Automated safety check: Pass	MIT	5 days ago
Frontmcp Testingagentfront/frontmcp	146	—	~10k	Automated safety check: Notes	Apache-2.0	yesterday

Similar skills

Glance Test
DebugBase/glance
Run E2E browser tests on any web application using Glance MCP.
156 GitHub stars~827 tokensUpdated 5 mo ago
Testing & QAAuto-check passed
Agentic Browser Testing
petrkindlmann/qa-skills
Goal-driven E2E testing where a browser agent (Playwright MCP / computer-use) reads a natural-language goal and explores the app via the accessibility tree to assert outcomes — no pre-written script.
165 GitHub stars~4.5k tokensUpdated 3 mo ago
Testing & QAAuto-check passed
Record E2E Gif
lablup/backend.ai-webui
Record Playwright e2e tests as one GIF per test case (video → ffmpeg palette GIF) and return a markdown table for a PR description.
133 GitHub stars~907 tokensUpdated today
Testing & QAAuto-check: notes
Replica Test
Jakeschincariol/replica-skill
Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser…
908 GitHub stars~819 tokensUpdated 5 days ago
Testing & QAAuto-check passed
Frontmcp Testing
agentfront/frontmcp
A skill your agent uses for anything about testing FrontMCP servers: writing or running unit, integration, and E2E tests and reaching the 95%+ coverage bar.
146 GitHub stars~10k tokensUpdated yesterday
Testing & QAAuto-check: notes
Specialist Integration Test Generator
HoangNguyen0403/agent-skills-standard
Generates one integration/E2E test from an approved test case spec using existing project patterns.
571 GitHub stars~548 tokensUpdated yesterday
Testing & QAAuto-check passed

Questions about Test Runner

What does Test Runner do?

Execute the appropriate test suite (unit, Gherkin, e2e, smoke) and return structured results. Test Runner is an agent skill from EmeaAppGbb/spec2cloud. Execute the appropriate test suite (unit, Gherkin, e2e, smoke) and return structured results.

When should I use Test Runner?

Test Runner fits situations like: checking test status; verifying test baselines.

How do I install Test Runner in Claude Code?

Run `npx skills add EmeaAppGbb/spec2cloud --skill test-runner -a claude-code`. Or copy the skill folder (.github/skills/test-runner in EmeaAppGbb/spec2cloud) into .claude/skills/test-runner in your project. Claude Code loads it when a task matches its description.

How do I install Test Runner in Codex?

Run `npx skills add EmeaAppGbb/spec2cloud --skill test-runner -a codex`. Or copy the skill folder (.github/skills/test-runner in EmeaAppGbb/spec2cloud) into .agents/skills/test-runner in your project. Codex loads it when a task matches its description.

Can I use Test Runner 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 EmeaAppGbb/spec2cloud --skill test-runner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-runner, .gemini/skills/test-runner, .github/skills/test-runner and .opencode/skills/test-runner in your project.

What does Test Runner need to run?

Going by SKILL.md and its folder, Test Runner needs the command-line tools its instructions call (npx and npm). Our summary lists: Node.js.

Does Test Runner access the network?

SKILL.md contains no URLs. Its commands use npx and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Test Runner 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 Test Runner use?

Test Runner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Runner use?

About 910 tokens (SKILL.md is roughly 3.6k 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 Test Runner?

Skills that share tags, products or a category with Test Runner: Glance Test (DebugBase/glance, 156 stars), Agentic Browser Testing (petrkindlmann/qa-skills, 165 stars), Record E2E Gif (lablup/backend.ai-webui, 133 stars) and Replica Test (Jakeschincariol/replica-skill, 908 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Runner?

EmeaAppGbb (a GitHub organization) maintains it in EmeaAppGbb/spec2cloud, which has 100 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on April 16, 2026.

Source: EmeaAppGbb/spec2cloud on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Test Runner

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Test Runner

Test Commands

Steps

Output Format

Aspire MCP Debugging Workflow

Edge Cases

Mandatory Completion Checklist

Files

Compare with similar skills

Similar skills

More from EmeaAppGbb/spec2cloud

Related

Questions about Test Runner