agentsclimarketplace

Test

10,621 rows, by stacks then stars

1,559 of these skill files have been read, by 1,201 distinct authors, and what they tell an agent counted. What Test authors agree on, and what they forbid

  • Bun test coverage

    VRIL-LABS/skill-jam/skills/ai-ml/claude-skills-main/claude-skills-main/plugins/bun/skills/bun-test-coverage Skill

    no license2★ repo

    Use for test coverage with Bun, --coverage flag, lcov reports, thresholds, and CI integration.

  • Bun test lifecycle

    VRIL-LABS/skill-jam/skills/ai-ml/claude-skills-main/claude-skills-main/plugins/bun/skills/bun-test-lifecycle Skill

    no license2★ repo

    Use for test lifecycle hooks: beforeAll, afterAll, beforeEach, afterEach, fixtures, preload.

  • Bun test mocking

    VRIL-LABS/skill-jam/skills/ai-ml/claude-skills-main/claude-skills-main/plugins/bun/skills/bun-test-mocking Skill

    no license2★ repo

    Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.

  • Cloudflare workers testing

    VRIL-LABS/skill-jam/skills/ai-ml/claude-skills-main/claude-skills-main/plugins/cloudflare-workers/skills/cloudflare-workers-testing Skill

    no license2★ repo

    Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.

  • Jest generator

    VRIL-LABS/skill-jam/skills/ai-ml/claude-skills-main/claude-skills-main/plugins/jest-generator/skills/jest-generator Skill

    no license2★ repo

    Generate Jest unit tests for JavaScript/TypeScript with mocking, coverage. Use for JS/TS modules, React components, test generation, or encountering missing coverage, improper mocking, test structure errors.

  • Mobile app testing

    VRIL-LABS/skill-jam/skills/ai-ml/claude-skills-main/claude-skills-main/plugins/mobile-app-testing/skills/mobile-app-testing Skill

    no license2★ repo

    Mobile app testing with unit tests, UI automation, performance testing. Use for test infrastructure, E2E tests, testing standards, or encountering test framework setup, device farms, flaky tests, platform-specific test errors.

  • Mutation testing

    VRIL-LABS/skill-jam/skills/ai-ml/claude-skills-main/claude-skills-main/plugins/mutation-testing/skills/mutation-testing Skill

    no license2★ repo

    Validate test effectiveness with mutation testing using Stryker (TypeScript/JavaScript with Vitest or bun test via @hughescr/stryker-bun-runner) and mutmut (Python). Find weak tests that pass despite code mutations. Use to improve test quality.

    The same file is in 1 other repository

  • Nuxt production

    VRIL-LABS/skill-jam/skills/ai-ml/claude-skills-main/claude-skills-main/plugins/nuxt-v4/skills/nuxt-production Skill

    no license2★ repo

    Nuxt 4 production optimization: hydration, performance, testing with Vitest, deployment to Cloudflare/Vercel/Netlify, and v4 migration. Use when: debugging hydration mismatches, optimizing performance and Core Web Vitals, writing tests with Vitest, deploying to Cloudflare Pages/Workers/Vercel/Netlify, or migrating from Nuxt 3 to Nuxt 4. Keywords: hydration, hydration mismatch, ClientOnly, SSR, performance, lazy loading, lazy hydration, Vitest, testing, deployment, Cloudflare Pages, Cloudflare Workers, Vercel, Netlify, NuxtHub, migration, Nuxt 3 to Nuxt 4

  • Playwright

    VRIL-LABS/skill-jam/skills/ai-ml/claude-skills-main/claude-skills-main/plugins/playwright/skills/playwright Skill

    no license2★ repo

    Browser automation and E2E testing with Playwright. Auto-detects dev servers, writes clean test scripts. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use for cross-browser testing, visual regression, API testing, component testing in TypeScript/JavaScript and Python projects.

  • Test quality analysis

    VRIL-LABS/skill-jam/skills/ai-ml/claude-skills-main/claude-skills-main/plugins/test-quality-analysis/skills/test-quality-analysis Skill

    no license2★ repo

    Detect test smells, overmocking, flaky tests, and coverage issues. Analyze test effectiveness, maintainability, and reliability. Use when reviewing tests or improving test quality.

  • Vitest testing

    VRIL-LABS/skill-jam/skills/ai-ml/claude-skills-main/claude-skills-main/plugins/vitest-testing/skills/vitest-testing Skill

    no license2★ repo

    Modern TypeScript/JavaScript testing with Vitest. Fast unit and integration tests, native ESM support, Vite-powered HMR, and comprehensive mocking. Use for testing TS/JS projects.

  • Initiating coverage

    VRIL-LABS/skill-jam/skills/ai-ml/financial-services-plugins-main/financial-services-plugins-main/equity-research/skills/initiating-coverage Skill

    no license2★ repo

    Create institutional-quality equity research initiation reports through a 5-task workflow. Tasks must be executed individually with verified prerequisites - (1) company research, (2) financial modeling, (3) valuation analysis, (4) chart generation, (5) final report assembly. Each task produces specific deliverables (markdown docs, Excel models, charts, or DOCX reports). Tasks 3-5 have dependencies on earlier tasks.

    The same file is in 2 other repositories

  • Testing strategy

    VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/engineering/skills/testing-strategy Skill

    no license2★ repo

    Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.

    The same file is in 5 other repositories

  • Sox testing

    VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/finance/skills/sox-testing Skill

    no license2★ repo

    Generate SOX sample selections, testing workpapers, and control assessments. Use when planning quarterly or annual SOX 404 testing, pulling a sample for a control (revenue, P2P, ITGC, close), building a testing workpaper template, or evaluating and classifying a control deficiency.

    The same file is in 1 other repository

  • Cypress

    VRIL-LABS/skill-jam/skills/ai-ml/skills-main-2/skills-main/cypress Skill

    no license2★ repo

    Cypress end-to-end testing best practices for web applications, covering test structure, commands, and reliability patterns.

  • Jest

    VRIL-LABS/skill-jam/skills/ai-ml/skills-main-2/skills-main/jest Skill

    no license2★ repo

    Jest testing best practices for JavaScript and TypeScript applications, covering test structure, mocking, and assertion patterns.

    The same file is in 1 other repository

  • Playwright cursor rules

    VRIL-LABS/skill-jam/skills/ai-ml/skills-main-2/skills-main/playwright-cursor-rules Skill

    no license2★ repo

    Expert guidance for Playwright end-to-end testing with TypeScript and JavaScript best practices

    The same file is in 1 other repository

  • Playwright

    VRIL-LABS/skill-jam/skills/ai-ml/skills-main-2/skills-main/playwright Skill

    no license2★ repo

    Playwright end-to-end testing best practices for web applications, covering test design, locator strategies, and assertion patterns.

  • Python testing

    VRIL-LABS/skill-jam/skills/ai-ml/skills-main-2/skills-main/python-testing Skill

    no license2★ repo

    Expert in Python testing with pytest and test-driven development

    The same file is in 1 other repository

  • Rspec

    VRIL-LABS/skill-jam/skills/ai-ml/skills-main-2/skills-main/rspec Skill

    no license2★ repo

    RSpec testing best practices for Ruby and Rails applications, covering test organization, data management, and isolation patterns.

    The same file is in 1 other repository

  • Selenium automation

    VRIL-LABS/skill-jam/skills/ai-ml/skills-main-2/skills-main/selenium-automation Skill

    no license2★ repo

    Expert guidance for browser automation and web testing using Selenium WebDriver with best practices for element location, waits, and test organization.

    The same file is in 1 other repository

  • Testing

    VRIL-LABS/skill-jam/skills/ai-ml/skills-main-2/skills-main/testing Skill

    no license2★ repo

    General testing best practices and guidelines for writing comprehensive, maintainable tests across different testing frameworks and languages.

  • Python executor

    VRIL-LABS/skill-jam/skills/ai-ml/skills-main/skills-main/tools/utilities/python-executor Skill

    no license2★ repo

    Execute Python code in a safe sandboxed environment via [inference.sh](https://inference.sh). Pre-installed: NumPy, Pandas, Matplotlib, requests, BeautifulSoup, Selenium, Playwright, MoviePy, Pillow, OpenCV, trimesh, and 100+ more libraries. Use for: data processing, web scraping, image manipulation, video creation, 3D model processing, PDF generation, API calls, automation scripts. Triggers: python, execute code, run script, web scraping, data analysis, image processing, video editing, 3D models, automation, pandas, matplotlib

    The same file is in 3 other repositories

  • Microsoft playwright cli playwright cli 1.0.2

    VRIL-LABS/skill-jam/skills/browser-automation/microsoft-playwright-cli-playwright-cli-1.0.2 Skill

    no license2★ repo

    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.

    The same file is in 6 other repositories

  • Openai skills playwright 1.0.1

    VRIL-LABS/skill-jam/skills/browser-automation/openai-skills-playwright-1.0.1 Skill

    no license2★ repo

    Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.

    The same file is in 7 other repositories

  • Vercel labs agent browser agent browser 1.0.3

    VRIL-LABS/skill-jam/skills/browser-automation/vercel-labs-agent-browser-agent-browser-1.0.3 Skill

    no license2★ repo

    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.

    The same file is in 1 other repository

  • Accessibility tester

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/testing-qa/accessibility-tester Skill

    no license2★ repo

    Test accessibility — WCAG compliance and a11y validation. Use when ensuring accessibility, testing screen readers, or meeting compliance requirements.

  • Api fuzz tester

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/testing-qa/api-fuzz-tester Skill

    no license2★ repo

    Fuzz test APIs — security testing and input validation. Use when finding API vulnerabilities, testing input handling, or security testing.

  • Contract test validator

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/testing-qa/contract-test-validator Skill

    no license2★ repo

    Validate API contracts with Pact or Spring Cloud Contract. Use when testing microservice interactions, preventing breaking changes, or implementing consumer-driven contracts.

  • Cross browser tester

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/testing-qa/cross-browser-tester Skill

    no license2★ repo

    Test across browsers — compatibility testing and automation. Use when ensuring browser compatibility, testing legacy browsers, or validating responsive design.

  • E2e test generator

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/testing-qa/e2e-test-generator Skill

    no license2★ repo

    Generate end-to-end tests with Playwright, Cypress, or Selenium — user journey testing, cross-browser validation, and automated testing. Use when testing complete user workflows, validating features across browsers, creating regression test suites, implementing CI/CD testing, or ensuring application quality before releases.

  • Integration test builder

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/testing-qa/integration-test-builder Skill

    no license2★ repo

    Build integration tests — API testing, database testing, and service integration. Use when testing integrations, validating APIs, or testing data flows.

  • Load generator

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/testing-qa/load-generator Skill

    no license2★ repo

    Generate load tests — JMeter, Locust, or k6 scenarios. Use when performance testing, capacity planning, or stress testing.

  • Mobile app tester

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/testing-qa/mobile-app-tester Skill

    no license2★ repo

    Test mobile applications — Appium, Detox, or Espresso tests. Use when testing iOS/Android apps, automating mobile tests, or validating mobile UX.

  • Mutation tester

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/testing-qa/mutation-tester Skill

    no license2★ repo

    Perform mutation testing — test quality assessment. Use when improving test coverage, finding weak tests, or validating test effectiveness.

  • Property based tester

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/testing-qa/property-based-tester Skill

    no license2★ repo

    Create property-based tests with QuickCheck or Hypothesis. Use when testing edge cases, generating test data, or finding subtle bugs.

  • Smoke test runner

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/testing-qa/smoke-test-runner Skill

    no license2★ repo

    Run smoke tests — quick validation after deployment. Use when validating deployments, testing critical paths, or pre-production checks.

  • Test data factory

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/testing-qa/test-data-factory Skill

    no license2★ repo

    Generate test data — fixtures, factories, and data builders. Use when creating test data, seeding databases, or generating realistic data.

  • Visual regression tester

    VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/testing-qa/visual-regression-tester Skill

    no license2★ repo

    Test visual regressions — screenshot comparison and UI testing. Use when preventing UI bugs, testing across browsers, or validating designs.

  • Qa

    VRIL-LABS/skill-jam/skills/core-collections/spellbook-master/spellbook-master/skills/qa Skill

    no license2★ repo

    Browser-based QA, exploratory testing, evidence capture, and bug reporting. Drive running applications and verify they work — not just that tests pass. Use when: "run QA", "test this", "verify the feature", "exploratory test", "check the app", "QA this PR", "capture evidence", "manual testing". Trigger: /qa.

  • Udecode plate test xcode 1.0.1

    VRIL-LABS/skill-jam/skills/ios-mobile/udecode-plate-test-xcode-1.0.1 Skill

    no license2★ repo

    Build and test iOS apps on simulator using XcodeBuildMCP

  • Load test script generator

    VRIL-LABS/skill-jam/skills/load-test-script-generator Skill

    no license2★ repo

    Generates load testing scripts for k6, Locust, or JMeter from an OpenAPI spec or recorded traffic, including ramp-up scenarios. Invoke when asked to create load tests, write performance tests, generate k6 scripts, simulate traffic, or test API capacity.

  • Test generator

    VRIL-LABS/skill-jam/skills/test-generator Skill

    no license2★ repo

    Reads source code and generates unit tests, integration tests, or snapshot tests with appropriate mocking. Invoke when asked to write tests, add test coverage, generate specs, or create test suites for functions, classes, or API endpoints.

  • Agent browser

    t4sh/dotfiles/agents/skills/agent-browser Skill

    no license2★ repo

    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. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

    The same file is in 2 other repositories

  • Improve

    t4sh/dotfiles/agents/skills/improve Skill

    no license2★ repo

    Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

    The same file is in 5 other repositories

  • Migrate to shoehorn

    t4sh/dotfiles/agents/skills/migrate-to-shoehorn Skill

    no license2★ repo

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    The same file is in 15 other repositories

  • Playwright

    t4sh/dotfiles/agents/skills/playwright Skill

    no license2★ repo

    Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.

    The same file is in 7 other repositories

  • Tdd

    t4sh/dotfiles/agents/skills/tdd Skill

    no license2★ repo

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

    The same file is in 9 other repositories

  • E2e tests

    GlamgarOnDiscord/claude-saas-blueprint/.claude/skills/e2e-tests Skill

    2★ repo

    Tests E2E Playwright pour SaaS Next.js : setup, Page Object Model, auth state, flows critiques (login, billing, onboarding), CI GitHub Actions.

  • Eval driven development

    jacob-balslev/skills/skills/ai-engineering/eval-driven-development Skill

    2★ repo

    Use when reasoning about building language-model-integrated systems by writing evaluations before and alongside the system: the statistical (not binary) nature of LLM evals, the five primitives (dataset, evaluation function, aggregation, iteration loop, regression budget), the judgment-mechanism taxonomy (programmatic, model-graded, human-graded, preference comparison, trace/hybrid), the eval-surface stack (final response, trajectory/tool-use, retrieval/RAG, safety, side effects, cost/latency), continuous evals and model-upgrade gates, the statistical-significance discipline (paired tests, McNemar's test, bootstrap CI on the delta, minimum-detectable-effect, clustered standard errors), trajectory-vs-final-output evaluation for multi-step agents, judge calibration and bias, Goodhart's Law and suite saturation, benchmark contamination and eval-awareness, cost-aware regression budgets, the difference between system-specific evals and canonical benchmarks (MMLU, HumanEval, BIG-bench, GAIA), and the offline-eval-vs-production-telemetry distinction with its graded rollout spectrum. Do NOT use for deterministic unit testing (use testing-strategy), production monitoring (use evaluation or error-tracking), general-software TDD (use testing-strategy), or the construction of individual eval rubrics and task sets (outside this skill; construction belongs in task-specific eval artifacts, while this skill owns the iteration discipline).

  • Evaluation

    jacob-balslev/skills/skills/ai-engineering/evaluation Skill

    2★ repo

    Use when scoring a completed agent task, implementation, document, skill upgrade, or other deliverable against the original request, acceptance criteria, verification evidence, quality rubric, and residual risks before calling it done. Covers skeptical critic review, 1-5 scoring, score ceilings, evidence sufficiency, finding/action capture, and the evaluation-revision loop. Do NOT use for designing eval datasets or graders (use eval-driven-development), line-by-line diff review (use code-review), choosing test levels (use testing-strategy), or designing the overall process and gates before work starts (use methodology).

  • Usability testing

    jacob-balslev/skills/skills/design/usability-testing Skill

    2★ repo

    Use when observing representative real users attempting realistic tasks on a prototype or live product to surface usability issues: moderated or unmoderated, remote or in-person, concurrent or retrospective think-aloud, task scenarios, participant screening, tree/first-click testing for IA findability questions, pilot runs, severity rating, sample sizing by claim type, and ethical recording/consent. Do NOT use for automated test suites, code coverage, CI pipelines, unit/integration testing, load testing, or replacing participants with AI/synthetic users; those are engineering verification or synthetic-analysis concerns, not human-behavior observation.

  • Middleware patterns

    jacob-balslev/skills/skills/frontend-engineering/middleware-patterns Skill

    2★ repo

    Use when designing or reviewing the Next.js request-preprocessing layer — the single root file that runs cross-cutting request/response transforms before route resolution. As of Next.js 16 this file is `proxy.ts` (function `proxy`, Node.js runtime, default export or named); `middleware.ts` (function `middleware`, Edge Runtime by default — Node.js opt-in since 15.5) is deprecated but retained for Edge use cases. Covers: the runtime split (proxy = Node.js, runtime config throws; middleware.ts = Edge by default with its capability ceiling, Node.js opt-in since 15.5), the `matcher` config that decides which paths it runs on, the `NextRequest`/`NextResponse` API for cookies/headers (and `geolocation()`/`ipAddress()` from `@vercel/functions` since `request.geo`/`request.ip` were removed in Next.js 15), the four response shapes (`next`/`rewrite`/`redirect`/direct response), `waitUntil` for background work, the official `next/experimental/testing/server` test utilities, the canonical patterns (auth gate, locale routing, A/B testing, header injection, geo-routing, bot blocking), the per-matched-request performance discipline, the CVE-2025-29927 lesson that this layer is NOT a security boundary, and the design rule that it is for cross-cutting concerns across many routes — never per-route business logic. Do NOT use for per-route HTTP endpoint logic (use route-handler-design), the Server Action mutation surface (use server-actions-design), abstract HTTP method/status/header semantics (use http-semantics), Content Security Policy and broader hardening (use security-fundamentals), or the cross-cutting streaming model (use streaming-architecture).

  • Code review

    jacob-balslev/skills/skills/quality-assurance/code-review Skill

    2★ repo

    Use when reviewing a pull request, diff, or proposed code change for correctness, clarity, security, performance, maintainability, test evidence, and conformance to project conventions — whether the author is a human, an AI agent, or a peer. Covers pre-review fact-gathering (including verifying an AI-written PR summary against the diff), the read-order strategy (tests first, then implementation, then call sites and blast radius), the size/attention budget, the severity-grading rubric mapped to the Conventional Comments standard, comment-phrasing discipline, reviewer qualification, the rule that diff content is evidence not instructions, the no-rubber-stamp rule for AI-generated diffs, and the explicit approve/request-changes/close merge decision. Do NOT use for AUTHORING the code (use `refactor` for behaviour-preserving changes or `skill-scaffold` for new skills), for chasing a known bug after merge (use `debugging`), for security-only audits (use `owasp-security`), or for explaining a patch without a merge verdict (use `diff-analysis`).

  • Contract testing

    jacob-balslev/skills/skills/quality-assurance/contract-testing Skill

    2★ repo

    Contract testing: interface verification between consumers and providers via shared contract artifacts and independent two-phase verification.

  • E2e test design

    jacob-balslev/skills/skills/quality-assurance/e2e-test-design Skill

    2★ repo

    Use when designing end-to-end tests that exercise a user-visible path through the whole system, including the UI layer: the user-journey unit-of-test that distinguishes e2e from integration testing, the five-primitive structure (user journey, environment, test data, observable assertion, recovery), why e2e tests are expensive and how to keep them few-and-load-bearing, the wait/synchronization discipline that makes them not-flaky, the page-object and trace-test patterns, the role of e2e tests in the test pyramid/trophy (the top tier — fewest in count but highest in coverage of user-observable behavior), and the modern e2e tool landscape (Playwright, Cypress, Selenium). Do NOT use for testing internal seams of the system (use integration-test-design), single-unit isolated tests (use testing-strategy + test-doubles-design), consumer-driven contract verification (use contract-testing), or visual regression of specific components (use snapshot-testing).

  • Integration test design

    jacob-balslev/skills/skills/quality-assurance/integration-test-design Skill

    2★ repo

    Use when designing tests that verify the interaction between two or more units of a system — modules, services, layers, processes: the scope-and-boundary primitives that distinguish integration from unit and e2e tests, the test-pyramid (Cohn 2009) and test-trophy (Dodds) frameworks for how much integration testing belongs in the suite, the real-vs-faked-collaborator decision per dependency, the test-data lifecycle (per-test setup, transaction rollback, container reset), the difference between sociable-unit tests, integration tests, and contract tests, and the failure modes (over-broad scope that mimics e2e, over-narrow scope that mimics unit, shared mutable state that produces flakes). Do NOT use for testing one unit in isolation (use testing-strategy + test-doubles-design), full user-journey testing (use e2e-test-design), consumer-driven contract verification (use contract-testing), or test-suite quality measurement (use mutation-testing).

  • Mutation testing

    jacob-balslev/skills/skills/quality-assurance/mutation-testing Skill

    2★ repo

    Use when reasoning about mutation testing as a behavioral signal of test-suite quality: the mutant-operator vocabulary (replace operator, negate condition, flip Boolean, remove statement, alter constant), the mutation-score metric (killed mutants / total non-equivalent mutants), why mutation testing is a stronger signal than code coverage (coverage measures execution; mutation measures whether the tests would catch a defect), the equivalent-mutant problem (mutants that produce no observable behavior change despite syntactic difference), selective and incremental mutation strategies that make the technique practical for large codebases (PIT, Stryker), and the relationship between mutation testing and TDD. Do NOT use for the structural signal of how much code tests reach (use test-coverage-strategy), the construction of test doubles (use test-doubles-design), the strategic question of what to test at which level (use testing-strategy), or generic fault injection at runtime (use chaos-engineering).

  • Performance testing

    jacob-balslev/skills/skills/quality-assurance/performance-testing Skill

    2★ repo

    Use when measuring a system's non-functional properties — latency, throughput, error rate, resource utilization, saturation — by running it under controlled load and verifying against explicit SLO thresholds. Covers the five primitives (load profile, workload, latency metric, throughput metric, SLO target), load-shape taxonomy (smoke, load, stress, spike, soak, breakpoint), latency-percentile vocabulary (p50, p95, p99, p99.9), why average latency and coordinated omission mislead, tool selection (k6, JMeter, Locust, Gatling, Vegeta), and offline controlled measurement versus production observability. Do NOT use for optimization itself (use `performance-engineering`), threshold contracts (use `performance-budgets`), production runtime measurement (use `observability-modeling` or `error-tracking`), single-function microbenchmarks, fault injection, or test-suite quality measurement (use `mutation-testing`).

  • Property based testing

    jacob-balslev/skills/skills/quality-assurance/property-based-testing Skill

    2★ repo

    Use when reasoning about tests that specify universal properties of code rather than specific input-output pairs: the forall(input) → property quantification, the generator/shrinker primitives that produce inputs and minimize failing cases, the four-rules-of-simple-design analog (commutativity, associativity, idempotence, round-trip, oracle, invariant), the difference between example-based tests (one input, one assertion) and property-based tests (many generated inputs, one universal claim), why property tests find bugs example tests don't, the shrinking discipline that produces minimal failing cases, and the trade-off between generator complexity and bug-finding capacity. Do NOT use for specifying one concrete behavior with one input (use example-based tests under testing-strategy), for fuzz-testing focused on crashes (use fuzz-testing), for mutation testing as a test-suite quality signal (use mutation-testing), or for model-based testing of state machines (use state-machine-modeling).