- 📁 evals/
- 📁 references/
- 📄 SKILL.md
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," or "how long should I run this test." Use this whenever someone is comparing two approaches and wants to measure which performs better. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
This skill should be used when a user says "run automated tests", "run lint", "run build", "run unit tests", "check the tests", or when qa-lead invokes it as the primary quality gate. Runs the full automated test pipeline in sequence: lint → build → unit tests. Reports pass/fail for each stage with output. Invoke for any Node.js project before marking work complete.
This skill should be used when the user asks to "run e2e test", "test clawteam", "end-to-end test", "test agent team", "verify clawteam works", "dev test", or wants to validate the full ClawTeam lifecycle. Runs a complete end-to-end test: cleanup → create team → create tasks with dependencies → spawn agents → wait for completion → verify results → cleanup.
- 📁 .claude-plugin/
- 📁 scripts/
- 📄 SKILL.md
21 production-ready scripts for iOS app testing, building, and automation. Provides semantic UI navigation, build automation, accessibility testing, and simulator lifecycle management. Optimized for AI agents with minimal token output.
This skill should be used when the user asks to "test a saas cross-repo feature", "deploy a feature branch to staging", "test SDK against OH Cloud branch", "e2e test a cloud workspace feature", "test secrets saas inheritance", or when changes span the SDK and OpenHands enterprise and need end-to-end validation against a staging deployment.
axe-core integration, WCAG 2.2 AA checklist, keyboard navigation testing, screen reader testing, and ARIA pattern validation.
Design, plan, and analyze A/B tests with statistical rigor. Use when the user asks about A/B testing, split testing, experiment design, statistical significance, sample size calculation, test duration, multivariate testing, or conversion experiments. Trigger phrases include "A/B test", "split test", "experiment", "statistical significance", "sample size", "test duration", "which version wins", "conversion experiment", "hypothesis test", "variant testing".
- 📁 scripts/
- 📄 SKILL.md
- 📄 skillpack.json
A minimal test skill for e2e testing of the skill pack resolver.
Echo the passed arg for testing
- 📁 references/
- 📁 subskills/
- 📄 SKILL.md
Creates, updates, and fixes Cypress tests (E2E/end-to-end and component tests). Use when the user asks to create tests, add tests, write tests, update tests, test this file/component, new spec, or fix a failing or flaky test. Apply even when the user does not say 'Cypress' (e.g. 'create tests for this file'). Prefer cypress-explain when the user only wants to explain or review tests without changing code.
- 📁 command/
- 📁 lib/
- 📁 references/
- 📄 SKILL.md
Provision Clerk test users, sign in via the browser, mint JWTs, and tear everything down — for local-dev tRPC / desktop / API testing. Triggers when the user wants to call Lightfast tRPC procedures with a real auth token, test desktop sign-in flows, or set up / clean up test users in Clerk dev.
Set up build environment and test fixtures for COBOL-to-Java migrations. Creates compilation infrastructure for both languages and generates golden test data.
