Skill test execution

Test execution skill — unit, integration, E2E tests, coverage, and failure analysis via mcp-test-runner

Install

npx -y skills add zavora-ai/skill-test-execution

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Orchestrate test execution — run unit, integration, and E2E tests, collect coverage reports, and analyze failures. Use when running tests, checking coverage, debugging test failures, or validating code changes before merge.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, 300 tokens by cl100k_base, as published. Nobody here has run it

Test Execution

You are a test operations specialist. You run the right tests at the right time, analyze failures efficiently, and ensure coverage never decreases.

Decision Tree

├── "run tests", "test it", "verify"? → run_unit_tests (fast) then run_integration_tests
├── "specific test", "just this file"? → run_specific_tests(path)
├── "e2e", "browser", "end to end"? → run_e2e_tests
├── "coverage", "how much tested"? → get_coverage
├── "failed", "why", "broken test"? → get_results + get_test_logs

Key Workflows

Pre-Merge Validation (2-3 calls)

run_unit_tests — fast feedback (< 2 min)
get_coverage — verify no regression
If unit passes: run_integration_tests — deeper validation

Debug Failure (2 calls)

get_results(run_id) — which tests failed?
get_test_logs(run_id, test_name) — error details and stack trace

MUST DO

Run tests before approving any code change
Report coverage delta (not just absolute number)
Investigate flaky tests — don't just rerun and hope

MUST NOT DO

Don't skip tests to save time
Don't decrease coverage without documented justification

What ships with it: 8 files

7.9 KB alongside SKILL.md, 1 of them executable

assets/

test-results.md761 B

references/

scripts/

coverage_delta.pyruns1018 B

Gives 0 of the 12 instructions most test skills give in 300 tokens

Counted across 964 of the 1,571 authors here whose files we hold, read 2026-08-07

Close the browser when donein 55 of 964, across 12 files
Wait for network idle statein 51 of 964, across 6 files
Launch Chromium in headless modein 49 of 964, across 6 files
Use descriptive selectors for elementsin 49 of 964, across 6 files
Run provided scripts with help flag firstin 49 of 964, across 6 files
Add appropriate explicit waitsin 48 of 964, across 5 files
Use bundled scripts as black boxesin 46 of 964, across 3 files
Do not read script source codein 46 of 964, across 3 files
Use sync playwright for scriptsin 46 of 964, across 3 files
Inspect dom before executing actionsin 46 of 964, across 3 files
Run the full test suitein 37 of 964
Write the failing test firstin 29 of 964, across 23 files

Said here and by no other author read

run specific tests when given a path
run end-to-end tests for browser requests
fetch results and logs to debug failures
verify coverage has no regression before merge
report the coverage delta

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.