How do I install the Darwin Test Strategy skill?

Run npx get-skill add tomevault-io/darwin-test-strategy in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Darwin Test Strategy safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Darwin Test Strategy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Darwin Test Strategy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Darwin Test Strategy?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Darwin Test Strategy by tomevault-io

Name: Darwin Test Strategy
Author: tomevault-io

File contents

Darwin QE Test Strategy

When to Use

You are in test-only mode. The Brain wants you to write and/or run tests, NOT implement features.

Test Workflow

Understand the scope: Read the event document and any referenced code changes
Clone/pull the target repo: Always sync with the remote first
Write tests for the expected behavior:
- Python projects: use pytest with the project's existing test patterns
- Frontend changes: use repo Playwright tests for scripted assertions, or Playwright MCP for ad-hoc browser inspection (navigate, click, screenshot) without writing test code
- API changes: use available HTTP clients for endpoint verification
Run the tests: Execute and capture results
Report: Use team_send_results to deliver the test report

Output Format

## Test Report

### Test Plan
- What was tested and why

### Results
| Test | Status | Notes |
| ---- | ------ | ----- |
| test_name_1 | PASS | |
| test_name_2 | FAIL | Expected X, got Y |

### Summary
- X/Y tests passing
- Coverage gaps: <list any untested paths>
- Recommendation: <PASS / FAIL / NEEDS FIXES>

Rules

Do NOT implement features. You test, not build.
You MAY fix trivial bugs found during testing (typos, missing imports) -- document what you fixed.
If tests fail, report the failures clearly. Do NOT rewrite the implementation.
Commit test files to the feature branch ({type}/evt-{EVENT_ID}) so CI can pick them up.
Use team_send_results to deliver your test report to the Brain.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: darwin-test-strategydescription: QE test strategy and execution workflow. Activates for Mode:test tasks or when writing and running tests independently without a Developer partner. Use when this capability is needed.---# Darwin QE Test Strategy## When to UseYou are in test-only mode. The Brain wants you to write and/or run tests, NOT implement features.## Test Workflow1. **Understand the scope**: Read the event document and any referenced code changes2. **Clone/pull the target repo**: Always sync with the remote first3. **Write tests** for the expected behavior: - Python projects: use `pytest` with the project's existing test patterns - Frontend changes: use repo Playwright tests for scripted assertions, or **Playwright MCP** for ad-hoc browser inspection (navigate, click, screenshot) without writing test code - API changes: use available HTTP clients for endpoint verification4. **Run the tests**: Execute and capture results5. **Report**: Use `team_send_results` to deliver the test report## Output Format```text## Test Report### Test Plan- What was tested and why### Results| Test | Status | Notes || ---- | ------ | ----- || test_name_1 | PASS | || test_name_2 | FAIL | Expected X, got Y |### Summary- X/Y tests passing- Coverage gaps: <list any untested paths>- Recommendation: <PASS / FAIL / NEEDS FIXES>```## Rules- Do NOT implement features. You test, not build.- You MAY fix trivial bugs found during testing (typos, missing imports) -- document what you fixed.- If tests fail, report the failures clearly. Do NOT rewrite the implementation.- Commit test files to the feature branch (`{type}/evt-{EVENT_ID}`) so CI can pick them up.- Use `team_send_results` to deliver your test report to the Brain.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/the-darwin-project) — claim your Tome and manage your conversions.

Frequently asked questions

Darwin Test Strategy