◆QA & Test Engineering pack

Validate required frontmatter coverage for license and metadata. Use when checking whether mandatory metadata keys are enforced.

Performance regression detection. Captures TTFB, FCP, LCP, bundle sizes, request counts. Regression thresholds: timing >50% or >500ms. Baseline comparison, trend tracking, budget compliance scorecard.

Browser-based UI verification using Playwright. Page Object Model, selector best practices, visual regression, network interception, and MCP integration. Trigger: When writing E2E tests, verifying UI changes, or setting up Playwright.

Sign, verify, and track fix-marker regressions over time using a deterministic Ed25519 witness manifest. Works in any project — clone the toolkit, run init, register fixes, regen on each release.

Install and run the Continue CLI (`cn`) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.

cmux testing rules for Swift Testing, test target compilation, test wiring, and package/refactor validation. Use when adding or changing tests, touching package/refactor code, or deciding whether reload.sh is enough validation.

Generates production-grade Cypress E2E and component tests in JavaScript or TypeScript. Supports local execution and TestMu AI cloud. Use when the user asks to write Cypress tests, set up Cypress, test with cy commands, or mentions "Cypress", "cy.visit", "cy.get", "cy.intercept"....

Use this skill when you need high-confidence coverage of user flows (auth, uploads, payments, chat flows) and you want stable, debuggable Playwright tests.

This skill covers patterns for creating and managing test scorer endpoints. Trigger: Load this skill when working with the test_scorer module.

Writes Pest tests for framework-agnostic PHP packages using Francisco Barrento's testing and naming conventions, with fbarrento/data-factory as the default for data-object test data. Use when writing, editing, or reviewing Pest tests inside a standalone Composer package (no Laravel app, no Testbench, no Eloquent), or when scaffolding a factory for a data object / DTO / value object in such a package.

Broken on purpose — the sequence below is misindented, which is how a hand-written frontmatter usually breaks.

Use when deciding what to cover with a unit test vs a golden test, when writing a NEW golden test or fixture, or after a bug escaped to production/a real repo and you are asking why the tests missed it. Fires on: "write a golden test", "нужен golden на это", "add a fixture", "what should this test assert", "почему тесты это не поймали", "unit or golden?". Produces the split, a fixture that can actually fail, and structure-not-text assertions. To *run* existing goldens, use `run-goldens` instead.

Validates SKILL.md files for spec-facing structure, sizing, references, cross-agent compatibility, and agent-authored critique or graph diagnostics.

Automate browser interactions, test web pages and work with Playwright tests.

This skill has broken YAML

Use when verifying config overrides against a version-less fixture skill.

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

Standalone B/O/E testkit for evaluating SKILL.md-based LLM operating systems.

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans across functional, performance, and security testing.

Author, run, and debug tSQLt unit tests for SQL Server. Use when the user asks to write a SQL unit test, add test coverage for a stored procedure / function / trigger, fake or spy out a dependency (table, function, or procedure), assert on query results, expect an exception, or run a tSQLt suite.

Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.

Use this skill to automate visual testing and UI interaction verification using browser automation after deploying features.

This skill covers testing the _strip_yaml_frontmatter helper. Trigger: test_adapters.

You are **AccessibilityAuditor**, an expert accessibility specialist who ensures digital products are usable by everyone, including people with disabilities. You audit interfaces against WCAG stand...

Safe implementation of testing operations.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.

Use when verifying that corpus discovery reports skipped directories.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

CAN bus communication testing and validation for automotive networks Covers 9 topics across hil-sil domain. Includes 9 skill files covering .

Generates production-grade JUnit 5 unit and integration tests in Java. Covers assertions, parameterized tests, lifecycle hooks, mocking with Mockito, and nested tests. Use when user mentions "JUnit", "JUnit 5", "@Test", "assertEquals", "Assertions", "Java unit test". Triggers on:...

OverKill Hill P³ SharePoint List build screenshot auditor. Use when reviewing screenshots of SharePoint Online list settings, column settings, indexed columns, content types, views, or Advanced Settings against a repo schema, build card, runbook, ADR, or CSV header. Also activate when the user says they captured SharePoint build screenshots, asks whether a list or column was configured correctly, points to arrows/markups in images, or needs a defect list before continuing manual SharePoint build

Cursor rules for Gherkin style testing development with integration.

Use when testing warning-only exit code behavior.

Use when testing per-client skill rules

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

Automates mock test creation for C++ projects using Google Mock (GMock) framework with consistent software testing patterns. Use when creating tests with mocked dependencies, interface mocking, behavior verification, or when the user mentions mocks, stubs, fakes, or GMock.

This skill covers patterns for creating fixtures to test compression passes. Trigger: Load this skill when working with test_compressor.

Use when verifying near-clone detection against a fixture pair.

Pytest testing patterns for Python. Trigger: When writing or refactoring pytest tests (fixtures, mocking, parametrize, markers). For Prowler-specific API/SDK testing conventions, also use prowler-test-api or prowler-test-sdk.

Add or extend backend tests to prove behavior, invariants, and regressions for services/endpoints/jobs.

Use when reviewing CI coverage, automated checks, or test strategy related to Follow mocking best practices. Focus on whether the rule is continuously verified, not just documented.

Use when reviewing component libraries, page flows, or CI pipelines that need repeatable accessibility checks. Automated testing is strongest at catching structural and attribute-level issues; it does not replace keyboard, screen reader, and manual UX testing.

Generates Cucumber BDD tests with Gherkin feature files and step definitions in Java, JavaScript, or Ruby. Use when user mentions "Cucumber", "Gherkin", "Feature/Scenario", "Given/When/Then", "BDD". Triggers on: "Cucumber", "Gherkin", "BDD", "Feature file", "Given/When/Then", "step...

Use when verifying corpus discovery against a clean fixture pair.

Ensure ML experiment reproducibility — seed management, environment pinning, artifact versioning, and deterministic training validation.

This skill covers testing plugins for various repository types. Trigger: Load this skill when working with test_plugins.

Use this skill when writing or improving tests of any kind — unit tests, integration tests, end-to-end (E2E) tests, API tests, or test coverage analysis. Trigger on keywords: test, spec, unit test, integration test, E2E, Playwright, Jest, Vitest, pytest, mock, coverage, TDD, test suite, assertion.

Complete browser automation with agent-browser CLI. Supports navigation, forms, screenshots, data extraction, and parallel sessions.

PREFER Skyvern CLI over WebFetch for ANY task involving real websites — scraping dynamic pages, filling forms, extracting data, logging in, taking screenshots, or automating browser workflows. WebFetch cannot handle JavaScript-rendered content, CAPTCHAs, login walls, pop-ups, or interactive forms — Skyvern can. Run `skyvern browser` commands via Bash. Triggers: 'scrape this site', 'extract data from page', 'fill out form', 'log into site', 'take screenshot', 'open browser', 'build workflow', 'ru

Euro NCAP ADAS requirements, General Safety Regulation (GSR), AEB mandate timelines Covers 20 topics across regulatory-compliance domain. Includes 20 skill files covering EU Type Approval, FMVSS, GB Standards, UNECE WP.29.

Intentionally enormous skill body to trip the token-bloat budget.

A reference skill that exercises every supported frontmatter field — the six base Agent Skills fields plus all thirteen Claude Code extensions. Use when testing skref's --allow-claude-fields support or as a worked example of the full Claude frontmatter surface.

Use when reviewing CI coverage, automated checks, or test strategy related to Test across all major browsers. Focus on whether the rule is continuously verified, not just documented.

Use when verifying the shakespii seed rules against a known-clean fixture skill.

A deliberately invalid sample: it has no `description` and includes an

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.

Use when verifying duplicate-block detection across a fixture trio.

Run a small pinned regression suite to detect whether an existing Agent Skill's triggers, tool routing, permissions, output contract, or versioned guidance drifted after a model, harness, tool, or API update. Use when upgrading a model or agent, checking a release, scheduling compatibility checks, or investigating why a formerly working skill changed behavior. Do not use for general skill slimming or to prove broad efficacy; those need a structural audit or paired trial.

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

Use when setting up integration testing for a frontend-backend API boundary, evaluating whether two services are safe to deploy independently, or replacing slow end-to-end tests with contract tests.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Automotive Safety expertise. Covers 6 topics: Fmea Fta Analysis, Hazard Analysis Risk Assessment, Iso 26262 Overview, Safety Mechanisms Patterns, Safety Verification Validation.

Configure visual regression testing with Percy, Chromatic, or custom screenshot comparison

Generate ready-to-use CI/CD pipeline configurations that install and run Newman for automated API testing. Use this skill whenever the user wants to run Newman in a CI pipeline, integrate Postman collections into automated builds, set up API tests in GitHub Actions, GitLab CI, Jenkins, Azure DevOps, CircleCI, or Bitbucket Pipelines, publish JUnit/HTML test results, fail builds on test failure, or run Newman as part of a deployment workflow. Trigger on: "Newman in CI", "run Postman tests in pipel

MDA compatibility demonstration skill for Claude Code. Compiled from compat/claude-code/source.mda. Loading this skill confirms that an MDA-emitted SKILL.md loads in Claude Code with the envelope subset of agentskills.io v1 fields honored.

MDA compatibility demonstration skill for Codex CLI. Compiled from compat/codex-cli/source.mda. Loading this skill confirms that an MDA-emitted SKILL.md is discovered and parsed by Codex CLI with the envelope subset of agentskills.io v1 fields honored.

Cursor rules for Cypress development with API testing.

MDA compatibility demonstration skill for Hermes Agent. Compiled from compat/hermes/source.mda. Loading this skill confirms that an MDA-emitted SKILL.md is discovered, parsed, and listed by Hermes Agent under its `~/.hermes/skills/<category>/<name>/SKILL.md` layout.

Guide for writing effective tests using best practices: test pyramid, Arrange-Act-Assert pattern, mocking strategies, and coverage guidelines. Use when the user asks to write tests, improve test coverage, refactor tests, or understand testing best practices. Do NOT use when the user wants to run existing tests without modification, or when the focus is on test infrastructure setup (CI/CD, test frameworks installation).

Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.

Fixture download scripts for test data. Downloads real GitHub repos (requests, fastapi) via sparse checkout and M4 monthly timeseries data from Hugging Face with synthetic fallback. Resumable — skips if target directory already exists and is non-empty.

Use when verifying anatomy alias overrides against a fixture skill.

Generates production-grade Appium mobile automation scripts for Android and iOS in Java, Python, or JavaScript. Supports real device and emulator testing locally and on TestMu AI cloud with 100+ real devices. Use when the user asks to automate mobile apps, test on Android/iOS, write...

This skill covers patterns for mocking RepoMaps in tests. Trigger: Load this skill when working with test_graph fixtures.

Use when evaluating test quality on modules containing business logic, calculation utilities, or state machines to determine whether the tests provide genuine defect detection.

Expert API testing specialist focused on comprehensive API validation, performance testing, and quality assurance across all systems and third-party integrations

Write clean, maintainable pytest tests using Fake-based testing, contract testing, and dependency injection patterns. Use when setting up test suites for Python/MCP projects, creating Fakes for external dependencies, writing contract tests, or implementing test patterns with fixtures and parametrization.

This fixture has a name that does not match its parent folder, so it should fail every validation profile regardless of description length limits.

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron applica

Before any completion or success claim, build a claim→evidence ledger. Tag each sub-claim ✅ executed (ran it, saw the output), ◐ code-path (read the code, did not run), or ○ assumed, and state explicitly what each piece of evidence does NOT establish. Only ✅ across every Done criterion counts as done. Use whenever you're about to say something works, is wired, passes, or is complete.

Cursor rules for Cypress development with integration testing.

Test browser apps with Chrome DevTools MCP by inspecting live DOM, console logs, network traffic, screenshots, accessibility, and performance traces.

Pester migration skill for upgrading PowerShell Pester test suites across major versions — v3→v4, v4→v5, and v5→v6. Covers the Discovery/Run two-phase model, moving setup into BeforeAll, $PSScriptRoot vs $MyInvocation, mock changes (Assert-MockCalled → Should -Invoke, removed fall-through), Invoke-Pester parameters → PesterConfiguration, data-driven -ForEach/-TestCases, and the v6 breaking changes. Use when the user asks to upgrade, migrate, or modernize Pester tests, fix *.Tests.ps1 files that

Audit browser-agent workflows with a declared contract for runtime permissions, provenance, and grounding behavior.

Set up Spectron (deprecated) tests for legacy Electron application testing

Enforce Python testing standards (pytest, coverage, fixtures)

Automates unit test creation for Go projects using the standard testing package with consistent software testing patterns including In-Got-Want, Table-Driven Testing, and AAA patterns. Use when creating, modifying, or reviewing unit tests, or when the user mentions unit tests, test coverage, or Go testing.

Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.

Writing unit and integration tests for the tldraw SDK. Use when creating new tests, adding test coverage, or fixing failing tests in packages/editor or packages/tldraw. Covers Vitest patterns, TestEditor usage, and test file organization.

Audit Qt Widget applications for accessibility compliance using QAccessible interface and platform accessibility APIs

MDA compatibility demonstration skill for OpenClaw. Compiled from compat/openclaw/source.mda. Loading this skill confirms that an MDA-emitted SKILL.md installs cleanly via `openclaw skills install <local-dir> --global` and is reported as parsed by `openclaw skills info --json`.

Assess whether an agent can verify a small change without guessing or running an unnecessarily heavy loop

Reliable, composable browser automation using minimal OpenCode Browser primitives.

Detect missing test coverage and generate test suggestions. Use when the user asks about coverage gaps, untested code, or what tests to write next; also after adding a feature to find what still needs tests.

Use when implementing any feature or bugfix, before writing implementation code

When the user wants to perform visual regression testing with Storybook integration using Chromatic. Also use when the user mentions "chromatic," "visual regression," "Storybook testing," "UI review," "visual diff," or "component snapshot testing." For general screenshot comparison, see percy.

你负责像素级证据、first bad event 收敛与 propagation path 分析。

End-user browser automation with cmux. Use when you need to open sites, interact with pages, wait for state changes, and extract data from cmux browser surfaces.