Loading...
Loading...
Found 301 Skills
AI agents as force multipliers for quality work. Core skill for all 19 QE agents using PACT principles.
Full closed-loop QA combining issue discovery and software testing. Scout -> Strategist -> Generator -> Executor -> Analyst with multi-perspective scanning, progressive test layers, GC loops, and quality scoring. Supports discovery, testing, and full QA modes.
Write a playwright test, make sure it runs, and is not flaky.
Invoke this skill when a user shares test code and questions whether it actually works as intended — not to run or fix the test, but to evaluate whether the test has real value. Triggers on: "is this test any good?", "would this catch a real bug?", "this test always passes — is that normal?", "review these tests before I commit", or "does this test verify anything meaningful?". Also triggers when someone suspects a test is useless, wants a pre-commit quality gate, or is unsure if an auto-generated test is worth keeping. The core question this skill answers: "Would this test fail if the feature broke?" If not, the test gets rejected. Do NOT use for generating new tests, fixing failing tests, or exploring application features.
Ensure code correctness with comprehensive unit and integration tests.
Use when choosing a testing approach for a project — selecting frameworks, defining coverage thresholds, setting up test infrastructure, and establishing testing patterns. Triggers: new project setup, CI/CD pipeline design, coverage audit, test framework migration, quality standard definition.
Execute YAML test plan, stop on first failure, output rich debug prompt
Primary Playwright governance skill for sandbox browser verification and deterministic end-to-end authoring or rewrite work.
Use when the user asks to generate API tests, create integration test suites, test REST endpoints, or build contract tests.
Use when about to submit work, before committing or pushing, to run verification commands and confirm the work actually passes before claiming completion
BrowserStack integration. Manage data, records, and automate workflows. Use when the user wants to interact with BrowserStack data.
Move testing activities earlier in the development lifecycle to catch defects when they're cheapest to fix. Use when implementing TDD, CI/CD, or early quality practices.