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

  • Snapshot testing

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

    2★ repo

    Use when reasoning about snapshot testing as a tactical technique: capture-and-compare against a reviewed baseline, data snapshots, DOM snapshots, text/file snapshots, visual snapshots, approval-cycle discipline, snapshot churn, unstable inputs, large unreadable diffs, golden files, characterization tests, and visual regression review with tools such as Jest, Vitest, Playwright screenshots, Storybook/Chromatic, and Percy. Do NOT use for the overall test-level mix (use `testing-strategy`), universal property claims (use `property-based-testing`), test double construction (use `test-doubles-design`), strict test-first workflow design (use `test-driven-development`), or end-to-end user journey design (use `e2e-test-design`).

  • Test coverage strategy

    jacob-balslev/skills/skills/quality-assurance/test-coverage-strategy Skill

    2★ repo

    Use when reasoning about code coverage as a strategic measurement rather than a quality target: structural reach versus behavioral verification (covered vs tested), the coverage-criterion hierarchy (function, line, branch, decision, condition, MC/DC, path) and matching the criterion to where a module's failure modes hide, Marick's floor-vs-ceiling distinction, Goodhart's Law applied to coverage and Goodhart-resistant policy (diagnostic use, diff/patch floors, risk-weighting, behavioral panels), denominator hygiene and cross-tool counter semantics, safety-critical MC/DC (DO-178C Level A required; ISO 26262 ASIL-D highly recommended) as requirements-based evidence, and interpreting coverage from AI-generated tests. Do NOT use for choosing test levels (use testing-strategy), mutation testing as a behavioral signal (use mutation-testing), test-double construction (use test-doubles-design), LLM eval iteration (use eval-driven-development), or specific coverage-tooling configuration (tool docs).

  • Test doubles design

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

    2★ repo

    Use when designing or reviewing test doubles — the stand-in objects that replace real collaborators in a test: the five-kind taxonomy (dummy, stub, spy, fake, mock) from Meszaros's xUnit Test Patterns, the difference between state verification (Detroit-school, classicist) and interaction verification (London-school, mockist) and how it determines which doubles fit, the cost of doubles (fragility, false confidence, divergence from real behavior), the role of fakes as the under-used middle ground, the verify_with relationship to test-driven-development, and the heuristics for when to use a real collaborator instead of any double. Do NOT use for choosing test levels or what to test (use testing-strategy), the design discipline of writing tests first (use test-driven-development), specific mocking-library API choice (library docs), or general production stubs and feature flags (use feature-gating or domain-specific skills).

  • Test driven development

    jacob-balslev/skills/skills/quality-assurance/test-driven-development Skill

    2★ repo

    Use when reasoning about Test-Driven Development as a design discipline rather than a workflow: the red-green-refactor cycle as a feedback loop, the difference between London-school (outside-in, interaction-heavy, mock-driven) and Detroit-school (inside-out, state-heavy, classicist) TDD, the role of TDD as a design tool (how tests pressure code into more decomposable shapes), the connection between TDD and emergent design, the boundary between TDD and prior-test-suites, why TDD's failure mode is not 'no tests' but 'tests that mirror implementation', and the empirical record of TDD's effects on defect density, design quality, and development velocity. Do NOT use for the strategy of what to test at which level (use testing-strategy), the construction of test doubles (use test-doubles-design), the discipline of LLM eval iteration (use eval-driven-development), or general-software process workflow (use the obra/superpowers test-driven-development workflow skill — this skill is the concept-shape complement).

  • Testing strategy

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

    2★ repo

    Use when planning tests for a bug fix, feature, or refactor — deciding what deserves a test, at which level, with what evidence. Covers test-scope decisions, test-level selection (unit / integration / contract / e2e), effort-to-risk matching, regression targeting, evidence quality, and failure-case coverage. Do NOT use for chasing a known failure (that is `debugging`), for pure doc writing (that is `documentation`), or for conceptual architecture discussion with no verification target (no dedicated skill — treat as strategy, not testing).

  • Experimentation

    jacob-balslev/skills/skills/software-engineering-method/experimentation Skill

    2★ repo

    Designing, running, and interpreting controlled experiments to decide whether a change is genuinely better — online A/B tests, randomized controlled trials, and offline hypothesis tests. Covers hypothesis framing, randomization and unit-of-assignment, sample-size and statistical-power calculation, metric design (primary, guardrail, invariant, and the overall evaluation criterion), variance reduction (CUPED/CUPAC) for sensitivity, significance testing and confidence intervals, sequential and anytime-valid testing for the peeking problem, multiple-comparison correction, the trust checklist led by sample-ratio-mismatch, interference-aware designs (cluster and switchback), long-term holdouts and reverse experiments, bandit/adaptive-allocation boundaries, experiment ethics and blast-radius limits, quasi-experimental fallbacks when randomization is infeasible, and the validity threats that quietly invalidate results (novelty and primacy effects, interference/SUTVA violations, Simpson's paradox, and survivorship).

  • Methodology

    jacob-balslev/skills/skills/software-engineering-method/methodology Skill

    2★ repo

    Use when planning multi-step implementations, designing quality gates, establishing verification protocols, or building agent checklists calibrated to known failure modes. Covers methodology/method/process distinctions, Cleanroom, PSP/TSP, hypothesis-driven development, DMAIC, checklist design, V&V frameworks, EDDOps, quality gates, and PDCA. Do NOT use for code-review verdicts (use `code-review`), behavior-preserving implementation work (use `refactor`), or test strategy (use `testing-strategy`).

  • Spec driven development

    jacob-balslev/skills/skills/software-engineering-method/spec-driven-development Skill

    2★ repo

    Use when starting a non-trivial feature, refactor, or agent implementation that needs a written spec, plan, task breakdown, and verification path before code changes. Covers Spec Kit-style SDD phases, requirements-vs-plan separation, task traceability, review gates, and spec-compliance verification. Do NOT use for one-line edits, README-only fixes, post-implementation code review (use `code-review`), or test-level decisions (use `testing-strategy`).

  • Starting point

    srinitude/skills/skills/starting-point Skill

    2★ repo

    Use when a request prescribes a method, tool, metric, or artifact that may not reach the result the user described, or when doing the request as written would leave that result unproved: "A/B test the signup button color" for a conversion problem, "add a cache" for a slow page, "the focused tests passed, announce the release". Also use when a stated constraint contradicts itself, when an unknown fact would have to be invented to finish, or when an external or irreversible step needs an authorization decision. Keywords: right approach, wrong metric, root cause, outcome versus output, what counts as done, proof, is this worth doing. Not for a literal edit, format, translation, or lookup whose method is the deliverable. Not a replacement for the design, debugging, research, or writing method that performs the work. Use the reify skill instead when the request is still too vague to have any method or outcome yet.

  • Diagnose

    makigjuro/cloudstack-ai-plugins/plugins/dev-workflow/skills/diagnose Skill

    2★ repo

    Investigate and diagnose problems using structured evidence gathering and hypothesis testing. Use whenever something is broken, failing, or behaving unexpectedly -- build errors, test failures, runtime exceptions, deployment issues, or performance problems.

  • Run tests

    makigjuro/cloudstack-ai-plugins/plugins/dev-workflow/skills/run-tests Skill

    2★ repo

    Run .NET tests with smart change detection -- auto-detects changed files via git diff and runs only affected test projects. Use whenever the user wants to run tests, verify changes, check if tests pass, run unit tests, integration tests, or test a specific service.

  • Generate tests

    makigjuro/cloudstack-ai-plugins/plugins/dotnet-architect/skills/generate-tests Skill

    2★ repo

    Generate unit and integration tests for commands, queries, entities, and event handlers. Use when the user wants to add tests, increase coverage, write specs, or test a handler they just created.

  • Smoke test

    makigjuro/cloudstack-ai-plugins/plugins/react-developer/skills/smoke-test Skill

    2★ repo

    Smoke test the running frontend and API by navigating key routes with Playwright, checking for console errors and broken pages. Use after starting the dev server or to verify the app works before creating a PR.

  • Test and fix

    yu-iskw/skill-inspector/.claude/skills/test-and-fix Skill

    2★ repo

    Run unit tests and automatically fix code failures, regression bugs, or test mismatches. Use when tests are failing, after implementing new features, or to repair "broken" tests.

    The same file is in 1 other repository

  • Python testing

    aps08/fullstack-clean-architecture/.agents/skills/python_testing Skill

    2★ repo

    Guidelines for Python testing using pytest and pytest-asyncio. Use when writing or debugging backend tests.

  • React testing

    aps08/fullstack-clean-architecture/.agents/skills/react_testing Skill

    2★ repo

    Frontend testing standards using Vitest, React Testing Library, and Playwright. Use when writing UI tests.

  • Test driven development

    bryanwhl/skill-graph/.agents/skills/test-driven-development Skill

    2★ repo

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

    The same file is in 33 other repositories

  • Playwright e2e

    5dive-ai/skills/playwright-e2e Skill

    2★ repo

    End-to-end testing and click-verification of web apps with Playwright — install, write specs, drive authenticated pages, take screenshots, and run in CI. Use when verifying a web change actually works in a real browser, testing user flows, debugging a UI bug live, or confirming an authed/gated page before shipping. Keywords Playwright, e2e, browser test, click test, screenshot, headless.

  • Test driven development

    allanbian1017/skills/skills/development/test-driven-development Skill

    2★ repo

    Drives development by enforcing a strict Red-Green-Refactor pipeline for features and a Prove-It pattern for bug fixes, completely language and framework agnostic.

  • Agent browser

    allanbian1017/skills/skills/personal/agent-browser Skill

    2★ 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.

  • Improve

    tommylower/cortex/agent-workflows/improve Skill

    2★ 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.

  • Tdd

    tommylower/cortex/engineering/tdd Skill

    2★ repo

    Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

  • Use a novel cli

    a-novel-kit/stack/.agents/skills/use-a-novel-cli Skill

    2★ repo

    Canonical reference for the `a-novel` CLI. ALWAYS load alongside any skill that runs tests, builds artifacts, releases, or starts/stops local services. Covers the groups `test`, `build`, `publish`, `repo` (repository config, rulesets, required checks), `run` (daemon-backed `start`/`kill`/`logs`/`env`/`volume`/`ui`) and `core` (daemon lifecycle). Prefer `a-novel <verb>` over raw commands; lint/format/generate live in pnpm scripts (`pnpm lint:go`, `pnpm format:go`), never in Makefiles — deleted from every repo.

  • Write go kit

    a-novel-kit/stack/.agents/skills/write-go-kit Skill

    2★ repo

    Go conventions for the a-novel-kit shared-library repos under `kit/` (`golib`, `jwt`, …) — the golib-stays-minimal bar, the stricter kit dependency policy, graduating a sub-package into its own community package, and kit test conventions. Load it to write or review Go there, or to decide whether something belongs in `golib` at all. ALWAYS load `write-go` alongside it; a-novel services use `write-go-service`. Pairs with `write-go-tests`, `document-code`, `manage-versions`. Not JS/TS, `kit/nodelib`, or `kit/workflows`.

  • Write go tests

    a-novel-kit/stack/.agents/skills/write-go-tests Skill

    2★ repo

    Test conventions for ALL Go code in the a-novel and a-novel-kit organizations — file/function naming, table-driven structure, mockery, assertions, parallelism, cross-package fixtures, helpers, coverage. Load it whenever writing or modifying a Go test file in a backend service OR a shared library. Pairs with `write-go`; layer-specific patterns live in `write-go-service`. Does NOT apply to JS/TS tests.

  • Write js package

    a-novel-kit/stack/.agents/skills/write-js-package Skill

    2★ repo

    Write, review, and maintain any Agora service's JavaScript/TypeScript REST client package. Use whenever creating or editing files under pkg/js/ — the published client library (pkg/js/rest/), its integration tests (pkg/js/test/rest/), or the package and build config. Covers API methods, type definitions, exports, and test cases.

  • Visual regression

    almasumdev/awesome-mobile-design-system-agent-skills/.github/skills/docs_and_tooling/visual-regression Skill

    no license2★ repo

    Visual regression testing for mobile design systems using Chromatic, Loki, Percy, Paparazzi, Roborazzi, swift-snapshot-testing, and flutter golden tests. Use this when setting up or auditing visual tests.

  • Moonbit

    morning-start/agent-skills/lang/moonbit Skill

    no license2★ repo

    Use when the user asks about MoonBit project setup, writing or refactoring code, debugging compiler errors, tests, publishing, optimization, FFI, or architecture decisions. Keywords: MoonBit, .mbt, .pkg, moon new, moon build, moon test, moon check.

  • 4 write tests

    morning-start/agent-skills/lang/moonbit/skills/4-write-tests Skill

    no license2★ repo

    编写 MoonBit 单元测试和集成测试。expect test、assert、覆盖率。 Use when writing tests, adding test cases, verifying correctness, or setting up test infrastructure for MoonBit projects.

  • Rust testing doc

    morning-start/agent-skills/lang/rust/rust-testing-doc Skill

    no license2★ repo

    Rust 测试与文档技能,掌握单元测试、集成测试、文档测试、文档注释和 rustdoc 使用

  • Coding unit test

    morning-start/agent-skills/process/project-management/coding-unit-test Skill

    no license2★ repo

    编码与单元测试工具。指导前后端并行开发、代码编写规范、单元测试撰写。适用于研发执行阶段的核心生产环节。

  • Testing acceptance

    morning-start/agent-skills/process/project-management/testing-acceptance Skill

    no license2★ repo

    测试与验收工具。指导提测、系统测试、用户验收测试、Bug管理全流程。适用于开发完成后的质量把控阶段。

  • Testing

    nevitonsantana/adaptive-skills/skills/testing Skill

    no license2★ repo

    Choose the minimum reliable proof for a change based on risk, reversibility, and impact.

  • Speed tests

    kip-claw/skills/speed-tests Skill

    no license2★ repo

    Runs an internet speed test and logs the results for the public stats page.

  • Ab test setup

    newmindsgroup/ai-agent-skills-library/dist/skills/ab-test-setup Skill

    2★ repo

    Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.

  • Agent browser

    newmindsgroup/ai-agent-skills-library/dist/skills/agent-browser Skill

    2★ 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.

  • Api fuzzing bug bounty

    newmindsgroup/ai-agent-skills-library/dist/skills/api-fuzzing-bug-bounty Skill

    2★ repo

    Provide comprehensive techniques for testing REST, SOAP, and GraphQL APIs during bug bounty hunting and penetration testing engagements. Covers vulnerability discovery, authentication bypass, IDOR exploitation, and API-specific attack vectors.

  • Api security testing

    newmindsgroup/ai-agent-skills-library/dist/skills/api-security-testing Skill

    2★ repo

    API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices.

  • Api testing observability api mock

    newmindsgroup/ai-agent-skills-library/dist/skills/api-testing-observability-api-mock Skill

    2★ repo

    You are an API mocking expert specializing in realistic mock services for development, testing, and demos. Design mocks that simulate real API behavior and enable parallel development.

  • Aws penetration testing

    newmindsgroup/ai-agent-skills-library/dist/skills/aws-penetration-testing Skill

    2★ repo

    Provide comprehensive techniques for penetration testing AWS cloud environments. Covers IAM enumeration, privilege escalation, SSRF to metadata endpoint, S3 bucket exploitation, Lambda code extraction, and persistence techniques for red team operations.

  • Awt e2e testing

    newmindsgroup/ai-agent-skills-library/dist/skills/awt-e2e-testing Skill

    2★ repo

    AI-powered E2E web testing — eyes and hands for AI coding tools. Declarative YAML scenarios, Playwright execution, visual matching (OpenCV + OCR), platform auto-detection (Flutter/React/Vue), learning DB. Install: npx skills add ksgisang/awt-skill --skill awt -g

  • Azure microsoft playwright testing ts

    newmindsgroup/ai-agent-skills-library/dist/skills/azure-microsoft-playwright-testing-ts Skill

    2★ repo

    Run Playwright tests at scale with cloud-hosted browsers and integrated Azure portal reporting.

  • Azure resource manager playwright dotnet

    newmindsgroup/ai-agent-skills-library/dist/skills/azure-resource-manager-playwright-dotnet Skill

    2★ repo

    Azure Resource Manager SDK for Microsoft Playwright Testing in .NET.

  • Bats testing patterns

    newmindsgroup/ai-agent-skills-library/dist/skills/bats-testing-patterns Skill

    2★ repo

    Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.

  • Burp suite testing

    newmindsgroup/ai-agent-skills-library/dist/skills/burp-suite-testing Skill

    2★ repo

    Execute comprehensive web application security testing using Burp Suite's integrated toolset, including HTTP traffic interception and modification, request analysis and replay, automated vulnerability scanning, and manual testing workflows.

  • Cloud penetration testing

    newmindsgroup/ai-agent-skills-library/dist/skills/cloud-penetration-testing Skill

    2★ repo

    Conduct comprehensive security assessments of cloud infrastructure across Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP).

  • Comprehensive review pr enhance

    newmindsgroup/ai-agent-skills-library/dist/skills/comprehensive-review-pr-enhance Skill

    2★ repo

    Generate structured PR descriptions from diffs, add review checklists, risk assessments, and test coverage summaries. Use when the user says "write a PR description", "improve this PR", "summarize my changes", "PR review", "pull request", or asks to document a diff for reviewers.

  • E2e testing patterns

    newmindsgroup/ai-agent-skills-library/dist/skills/e2e-testing-patterns Skill

    2★ repo

    Build reliable, fast, and maintainable end-to-end test suites that provide confidence to ship code quickly and catch regressions before users do.

  • E2e testing

    newmindsgroup/ai-agent-skills-library/dist/skills/e2e-testing Skill

    2★ repo

    End-to-end testing workflow with Playwright for browser automation, visual regression, cross-browser testing, and CI/CD integration.

  • Ffuf web fuzzing

    newmindsgroup/ai-agent-skills-library/dist/skills/ffuf-web-fuzzing Skill

    2★ repo

    Expert guidance for ffuf web fuzzing during penetration testing, including authenticated fuzzing with raw requests, auto-calibration, and result analysis

  • Go playwright

    newmindsgroup/ai-agent-skills-library/dist/skills/go-playwright Skill

    2★ repo

    Expert capability for robust, stealthy, and efficient browser automation using Playwright Go.

  • Html injection testing

    newmindsgroup/ai-agent-skills-library/dist/skills/html-injection-testing Skill

    2★ repo

    Identify and exploit HTML injection vulnerabilities that allow attackers to inject malicious HTML content into web applications. This vulnerability enables attackers to modify page appearance, create phishing pages, and steal user credentials through injected forms.

  • Idor testing

    newmindsgroup/ai-agent-skills-library/dist/skills/idor-testing Skill

    2★ repo

    Provide systematic methodologies for identifying and exploiting Insecure Direct Object Reference (IDOR) vulnerabilities in web applications.

  • Javascript testing patterns

    newmindsgroup/ai-agent-skills-library/dist/skills/javascript-testing-patterns Skill

    2★ repo

    Comprehensive guide for implementing robust testing strategies in JavaScript/TypeScript applications using modern testing frameworks and best practices.

  • K6 load testing

    newmindsgroup/ai-agent-skills-library/dist/skills/k6-load-testing Skill

    2★ repo

    Comprehensive k6 load testing skill for API, browser, and scalability testing. Write realistic load scenarios, analyze results, and integrate with CI/CD.

  • Lambdatest agent skills

    newmindsgroup/ai-agent-skills-library/dist/skills/lambdatest-agent-skills Skill

    2★ repo

    Production-grade test automation skills for 46 frameworks across E2E, unit, mobile, BDD, visual, and cloud testing in 15+ languages.

  • Network 101

    newmindsgroup/ai-agent-skills-library/dist/skills/network-101 Skill

    2★ repo

    Configure and test common network services (HTTP, HTTPS, SNMP, SMB) for penetration testing lab environments. Enable hands-on practice with service enumeration, log analysis, and security testing against properly configured target systems.

  • Odoo automated tests

    newmindsgroup/ai-agent-skills-library/dist/skills/odoo-automated-tests Skill

    2★ repo

    Write and run Odoo automated tests using TransactionCase, HttpCase, and browser tour tests. Covers test data setup, mocking, and CI integration.

  • Performance testing review ai review

    newmindsgroup/ai-agent-skills-library/dist/skills/performance-testing-review-ai-review Skill

    2★ repo

    You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C

  • Performance testing review multi agent review

    newmindsgroup/ai-agent-skills-library/dist/skills/performance-testing-review-multi-agent-review Skill

    2★ repo

    Reviews performance test results and system bottlenecks with multiple analytical perspectives before recommending optimization work.