agentsclimarketplace

Test

10,607 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

  • Case 04996

    knownasnaffy/prompthound/dataset/case_04996 Skill

    no license0★ 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.

  • Case 05012

    knownasnaffy/prompthound/dataset/case_05012 Skill

    no license0★ repo

    Desktop automation via PyAutoGUI. Use when: user needs to automate mouse/keyboard actions, GUI testing, click/type sequences, screen-based workflows, or repetitive desktop tasks. NOT for: web automation (use Playwright/Selenium), mobile automation, or image recognition at scale.

  • Case 05241

    knownasnaffy/prompthound/dataset/case_05241 Skill

    no license0★ repo

    Audit and verify provably fair casino fairness. Cryptographic verification of gambling results using SHA3-384 and AES-256-CTR. Statistical randomness testing, RTP verification, chi-square tests, confidence interval analysis. Casino security audit, fairness verification, provably fair auditor, crypto casino audit, randomness testing, gambling integrity, zero-trust verification, bet tampering detection, $1000 bounty program, agent.rollhub.com security audit tool, blockchain gambling verification.

  • Case 05305

    knownasnaffy/prompthound/dataset/case_05305 Skill

    no license0★ repo

    Set up headless browser automation in Clawdbot using Playwright Chromium. Use when configuring browser tools for WSL/Linux environments, installing browser dependencies, or enabling headless web automation. Handles Chromium installation, system library dependencies, and Clawdbot browser configuration.

  • Case 05379

    knownasnaffy/prompthound/dataset/case_05379 Skill

    no license0★ repo

    Orchestrate small development workflows: parse requirements, spawn two persistent subagents (coding and testing, each with isolated 128k context), loop until tests pass, and produce local git commits. Use when a user asks to implement+test a workflow or invokes `run workflow: <spec>`.

  • Case 05457

    knownasnaffy/prompthound/dataset/case_05457 Skill

    no license0★ repo

    Desktop automation via PyAutoGUI. Use when: user needs to automate mouse/keyboard actions, GUI testing, click/type sequences, screen-based workflows, or repetitive desktop tasks. NOT for: web automation (use Playwright/Selenium), mobile automation, or image recognition at scale.

  • Plan then code

    goonobu-dot/dev-skills-library/skills/plan-then-code Skill

    0★ repo

    Anthropic's explore-plan-code-commit workflow for AI-assisted development: clarify requirements before coding, write a plan for non-trivial changes, iterate in small verified steps, and treat context as a finite resource. Use when starting any non-trivial implementation task, when requirements are ambiguous, or when the user says 計画して, いきなり書かないで, 手順を決めて, 要件を整理して. Skip planning only when the entire diff can be described in one sentence. Not for the red-green-refactor cycle itself (use test-driven-development) or for orchestrating a multi-step business engagement as project leader (use agent-team; this skill applies to the individual implementation task within it).

  • Test suite design

    goonobu-dot/dev-skills-library/skills/test-suite-design Skill

    0★ repo

    Test suite architecture: test pyramid, deciding what to test at which layer, removing redundant tests, test granularity. Use when designing test strategy for a feature or project, reviewing test coverage, deciding between unit/integration/E2E tests, or when the user says テスト戦略, テスト設計, どこまでテスト, テストが多すぎる. For the red-green-refactor implementation workflow use test-driven-development instead — this skill is about suite-level architecture, not the moment-to-moment cycle of writing one test.

  • Behavioral testing

    MasashiFukuzawa/agent-toolbox/plugins/toolbox/skills/behavioral-testing Skill

    0★ repo

    Reusable engineering skills for Claude Code and Codex

  • Browser operations

    MasashiFukuzawa/agent-toolbox/plugins/toolbox/skills/browser-operations Skill

    0★ repo

    Playwright CLI やブラウザ制御手段を選び、ログイン引き継ぎと永続セッションを安全に扱う。アドホックなブラウザ操作に使う。staging E2E の能力検証には使わない。「ブラウザで確認」「ログインを引き継いで」を正のトリガーとし、認証済みstagingの破壊的フロー検証には e2e-capability-verification を使う。

  • E2e capability verification

    MasashiFukuzawa/agent-toolbox/plugins/toolbox/skills/e2e-capability-verification Skill

    0★ repo

    staging や test 環境で認証付き E2E と機能可否を安全に検証する。破壊的操作や storageState が関わる検証に使う。アドホックなブラウザ操作には browser-operations を使う。「stagingで可能か確認」「認証付きE2Eを検証」を正のトリガーとし、日常的なサイト閲覧やログイン引き継ぎには使わない。

  • Testing strategy

    sandev/engineering-os/skills/building-and-delivering/testing-strategy Skill

    0★ repo

    Decide what to test, at which level, and how, so tests catch real defects, run fast, and don't rot. Use when designing a test suite, deciding unit vs integration vs end-to-end coverage, dealing with flaky or slow tests, or judging whether a change is adequately tested.

  • Tdd

    gio-del/skills/skills/engineering/tdd Skill

    0★ 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

  • Dodgeball

    jawsublime-byte/simon-says/skills/dodgeball Skill

    0★ repo

    Coordinate a bounded volley of sequential and concurrent defensive tests to reproduce race, contention, ordering, retry, load, or multi-input failures. Use only when the user explicitly invokes Dodgeball for an authorized non-production target or approved safe test window.

  • Proof split

    kaskilling/agent-coordination-skills/skills/proof-split Skill

    0★ repo

    Split an investigation, audit, or research task across multiple orthogonal proof surfaces and synthesize one evidence-backed conclusion without a fix/re-review loop. Use when the user asks for parallel lookups, repo-wide inspection, specialist review lenses, simultaneous research, or faster coverage of separable risks across code, tests, documentation, packaging, devices, environments, or hosted systems.

  • Testing checklist

    yuri-semenenko/ai-engineering-workspace/claude-code/.claude/skills/testing-checklist Skill

    0★ repo

    Testing checklist — test pyramid, what to test vs skip, DAMP over DRY, the TDD red-green-refactor loop for new code, failing-test-first for bug fixes, Vitest / React Testing Library patterns. Use when writing or reviewing tests, deciding test coverage for a change, driving new code test-first, fixing a bug (regression test), or when the user asks "what should I test here", "покрой тестами", "review the tests". Pairs with /verify (runtime verification) and the persona's Verification Exit Criterion. Sibling of /web-security-checklist and /web-performance-checklist.

  • Test strategy

    yuri-semenenko/ai-engineering-workspace/codex/skills/test-strategy Skill

    0★ repo

    Use when writing or reviewing tests, deciding coverage for a change, driving new code test-first, or fixing a bug that needs a regression test. Covers what to test, the TDD loop, and failing-test-first.

  • Inngest cli

    DrOlu/agent-skills/skills/inngest-cli Skill

    no license0★ repo

    Use when installing or running the Inngest CLI and Dev Server for local development, local testing, serve endpoint debugging, Docker or Docker Compose setup, MCP configuration, self-hosted `inngest start`, or deployment workflow checks. Covers `inngest dev`, `inngest start`, auto-discovery, config files, environment variables, `@inngest/test`, local event sending, platform gotchas, and production/self-hosted server flags.

    The same file is in 1 other repository

  • Playwright cli

    DrOlu/agent-skills/skills/playwright-cli Skill

    no license0★ 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.

  • Vapt

    DrOlu/agent-skills/skills/vapt Skill

    no license0★ repo

    Comprehensive vulnerability assessment and penetration testing skill leveraging Secator, NetExec, Metasploit, and raw Python for advanced exploitation chaining across Linux, Windows, Unix, macOS systems, network devices (switches, routers, firewalls), protocols, webapps and APIs (REST, GraphQL, gRPC). Uses OSSTMM and OWASP standards. Supports blackbox, greybox, and whitebox pentests with false-positive resistance, verified exploit confirmation, detailed step-by-step remediation, and full documentation. Use when performing security assessments, penetration tests, vulnerability scans, exploit validation, network enumeration, or security auditing.

  • Webapp testing

    DrOlu/agent-skills/skills/webapp-testing Skill

    no license0★ repo

    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.

  • Writing tests

    DrOlu/agent-skills/skills/writing-tests Skill

    no license0★ repo

    Comprehensive guide for writing unit tests, integration tests, and component tests in AiderDesk using Vitest. Use when creating new tests, configuring mocks, or organizing test files.

  • Test driven learning

    aoli0919/learn-anything-skills/skills/test-driven-learning Skill

    0★ repo

    Use tests as learning scaffolds: expected behavior, failing case, minimal implementation, and reflection.

  • Debug systematically

    K95M65/AI_ONBOARD/skills/debug-systematically Skill

    0★ repo

    Reproduces software failures, isolates causal conditions, tests competing hypotheses, and either reports the supported diagnosis or implements and verifies the smallest authorized root-cause fix. Use for diagnosis or repair when the cause of a bug, crash, flaky test, incorrect output, performance regression, race condition, integration failure, or environment-specific behavior is unknown; do not use for feature development or a known-cause change that the user explicitly wants implemented test-first.

  • Develop apple platform app

    K95M65/AI_ONBOARD/skills/develop-apple-platform-app Skill

    0★ repo

    Implements and reviews Swift applications for Apple platforms, with special coverage for macOS, using the repository's real Xcode or SwiftPM configuration. Use when building, changing, debugging, testing, profiling, packaging, signing, or distributing a SwiftUI, AppKit, UIKit, mixed-framework, SwiftData, or Core Data application; do not use it for product-interface strategy alone.

  • Develop test first

    K95M65/AI_ONBOARD/skills/develop-test-first Skill

    0★ repo

    Implements a known behavior change through a focused failing test, the smallest passing production change, and a verified refactor. Use when the user requests test-driven development, a known-cause regression-first bug fix, or new testable domain logic; do not use for unknown-cause diagnosis, behavior-preserving legacy characterization or refactoring, documentation-only work, generated artifacts, exploratory spikes, or UI polish whose value cannot be expressed as stable behavior.

  • Swift testing expert

    K95M65/AI_ONBOARD/skills/swift-testing-expert Skill

    0★ repo

    Guide Swift Testing structure, #expect and #require macros, traits, parameterized tests, test plans, parallel execution, async waiting, and XCTest migration. Use when writing or modernizing Swift tests, debugging flaky tests, or improving test quality in Apple-platform or server projects; inspect the project's Swift and platform targets first.

  • Test browser workflows

    K95M65/AI_ONBOARD/skills/test-browser-workflows Skill

    0★ repo

    Designs and runs browser-based validation for websites and web applications, including critical user flows, responsive behavior, keyboard interaction, accessibility structure, visual regression, screenshots, and traces. Use when testing rendered browser behavior, adding or improving Playwright end-to-end tests, reproducing a UI failure, or collecting browser QA evidence; do not use for unit tests alone or for archival capture of public sources.

  • Terraform

    cedws/skills/terraform/skills/terraform Skill

    no license0★ repo

    Write, review, refactor, validate, and test modern Terraform configuration while loading release-specific guidance newer than the model's knowledge cutoff. Use for any task involving Terraform or HCL configuration, modules, providers, state, plans, tests, or CLI workflows.

  • Workforce shift coverage

    mahidalhan/openfactory/.agents/skills/workforce-shift-coverage Skill

    0★ repo

    Use when a production plan depends on skilled labor, certifications, attendance, shift patterns, overtime, cross-training, reassignment, or deciding whether labor is the binding capacity constraint.

  • Mcp server testing

    Paldom/mcp-server-skills/skills/mcp-server-testing Skill

    0★ repo

    Tests and evaluates MCP servers - Inspector, the official conformance suite, agent evals with verifiable answers, transcript-driven description iteration, tool-selection accuracy, CI regression gates, load tests. Use when the user asks to test, evaluate, verify, or measure an MCP server or its tool selection. Not for fixing server code, security hardening, or generic unit testing.

  • Test driven development

    trugurpala/divan/plugins/core-pack/skills/test-driven-development Skill

    29 days old0★ repo

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

    The same file is in 160 other repositories

  • Webapp testing

    trugurpala/divan/plugins/ui-pack/skills/webapp-testing Skill

    29 days old0★ repo

    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.

    The same file is in 367 other repositories

  • Stress test claim

    cxMoonGlade/Theory-First/plugins/theory-first/skills/stress-test-claim Skill

    0★ repo

    Run explicit falsification trip-wires against a frozen, literature-closed computational-science claim. Use when theory-fix assigns a refreshed closure packet, or directly only when the user already has that packet plus the preregistration and raw result artifacts. It checks theorem and symmetry constraints, formulation invariance, mechanism-to-observable bridges, independent ground truth, degenerate interventions, suppressing measurement lenses, preregistration integrity, and downstream propagation. For a merely clean, surprising, hoped-for, or consequential result whose evidence has not been reopened, use theory-fix instead. This skill does not acquire literature or repair the claim itself.

  • Fixture

    awesome-liuxiao/agent-skill-doctor/benchmarks/public/v1/functional/eval-contract/fixture Skill

    no license0★ repo

    Create a bounded result file for the public functional evaluation.

  • Fixture

    awesome-liuxiao/agent-skill-doctor/benchmarks/public/v1/functional/performance-regression/baseline/fixture Skill

    no license0★ repo

    Controlled performance baseline fixture.

  • Fixture

    awesome-liuxiao/agent-skill-doctor/benchmarks/public/v1/functional/performance-regression/mutated/fixture Skill

    no license0★ repo

    Controlled performance baseline fixture.

  • Diagnose github actions

    cristianmoroaica/bountyverdict/skills/diagnose-github-actions Skill

    0★ repo

    Diagnose a public GitHub Actions workflow run with RunVerdict before changing code or rerunning CI. Use when a GitHub Actions run, job, matrix shard, test suite, build, lint, dependency install, timeout, runner, authentication, or infrastructure step failed and the agent needs evidence-linked root causes, retryability, or the earliest job to repair.

  • Backend integration testing

    ahtishamshahzad/agent_dev_flow/.ai/skills/backend/backend-integration-testing Skill

    0★ repo

    Use to plan backend integration tests — real HTTP requests against the app with a real (containerized) database, covering auth flows, authorization negative tests (cross-user/cross-tenant/role), validation rejection, and webhook/job paths. External providers stay faked.

  • Backend unit testing

    ahtishamshahzad/agent_dev_flow/.ai/skills/backend/backend-unit-testing Skill

    0★ repo

    Use to plan backend unit tests — services and pure business logic tested in isolation with focused test doubles, fast and deterministic, covering edge and failure paths. Route/database/HTTP coverage belongs to integration testing.

  • Mobile component testing

    ahtishamshahzad/agent_dev_flow/.ai/skills/mobile/mobile-component-testing Skill

    0★ repo

    Use to plan component tests — React Native Testing Library for rendering, interaction, and accessibility queries — testing components as users interact with them. Complements unit and E2E tests.

  • Mobile maestro e2e

    ahtishamshahzad/agent_dev_flow/.ai/skills/mobile/mobile-maestro-e2e Skill

    0★ repo

    Use to plan Maestro end-to-end tests for critical mobile flows on real device/emulator. Select Maestro when critical mobile E2E flows exist; cover the critical path (auth, checkout, core journeys) rather than every screen.

  • Mobile unit testing

    ahtishamshahzad/agent_dev_flow/.ai/skills/mobile/mobile-unit-testing Skill

    0★ repo

    Use to plan unit tests for mobile logic — Jest (or Vitest where supported) for pure functions, hooks, reducers, and utilities. Test behavior, not implementation; align with the approved stack.

  • Refactor planning

    ahtishamshahzad/agent_dev_flow/.ai/skills/refactor-planning Skill

    0★ repo

    Use to plan a behavior-preserving structural improvement — audit the target, ensure test coverage exists, plan small reversible steps, and verify behavior is unchanged. Any intended behavior change is a feature, not a refactor.

  • Security regression testing

    ahtishamshahzad/agent_dev_flow/.ai/skills/security/security-regression-testing Skill

    0★ repo

    Use to turn security findings and threats into automated tests that stay green — negative tests for authorization/injection/abuse, a test per fixed vulnerability, and CI enforcement so security regressions can't silently return. Security's regression discipline.

  • Testing strategy

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing-strategy Skill

    0★ repo

    Use to choose testing levels and tools per application and change, proportional to risk, and to define what "tested" means for the work. Aligns with the approved stack; every bug fix gets a regression test. Honest about what was actually run.

  • Api integration testing

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing/api-integration-testing Skill

    0★ repo

    Use to plan backend API integration tests with Supertest — real HTTP requests through the full middleware stack against a real database, covering happy path, invalid input, error path, and the authorization-denial negative suite (cross-user, non-admin, cross-tenant, untrusted IDs).

  • Contract testing

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing/contract-testing Skill

    0★ repo

    Use to verify that independently deployed clients and services agree on their API contract — schema/consumer-driven checks in CI that fail when a provider change would break a consumer, catching integration breakage before deploy rather than in production.

  • Flaky test audit

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing/flaky-test-audit Skill

    0★ repo

    Use to find, diagnose, and fix flaky tests — nondeterministic passes/failures from timing, shared state, ordering, real time/randomness, or live externals. Fix the root cause; quarantine only temporarily. A trusted suite is the goal, not a green-by-retry one.

  • Integration testing

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing/integration-testing Skill

    0★ repo

    Use to plan integration tests across module and I/O boundaries — real database, real wiring, faked externals — covering happy path, invalid input, error path, and authorization denial. For HTTP API specifics use api-integration-testing.

  • Maestro e2e

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing/maestro-e2e Skill

    0★ repo

    Use to plan mobile end-to-end and smoke tests with Maestro — critical device flows on emulator/simulator, resilient to timing, covering happy path plus key error and authorization-denied variants. Reserved for critical mobile journeys; coordinates with the mobile pack.

  • Playwright e2e

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing/playwright-e2e Skill

    0★ repo

    Use to plan web/dashboard end-to-end tests with Playwright — a small set of critical user journeys against a real browser and running app, resilient to timing (auto-wait, no sleeps), covering happy path plus key invalid/error/authorization-denied flows. Reserved for flows that justify E2E cost.

  • Regression testing

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing/regression-testing Skill

    0★ repo

    Use to ensure every fixed bug and every critical behavior stays fixed — a failing-first test per bug at the lowest level that reproduces it, plus a maintained regression suite gating CI so old breakage can't silently return.

  • Smoke testing

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing/smoke-testing Skill

    0★ repo

    Use to define a minimal, fast smoke suite that proves a build/deploy is fundamentally alive — app starts, health checks pass, auth works, primary flows load — run after every build and post-deploy as a go/no-go gate, distinct from full regression.

  • Test coverage audit

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing/test-coverage-audit Skill

    0★ repo

    Use to assess test coverage by risk, not by percentage — find untested critical paths (auth, money, data integrity, error/denial paths) and missing required cases, and recommend targeted tests. Never chase a coverage number without risk justification.

  • Test data management

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing/test-data-management Skill

    0★ repo

    Use to plan test data — factories over fixtures, per-test isolation, deterministic personas (users, roles, tenants) for authorization tests, and strict separation from production data. No real PII in tests; data is owned per test, not shared and mutated.

  • Test environment management

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing/test-environment-management Skill

    0★ repo

    Use to provision test environments — real production-engine datastores (containerized), faked externals, isolated per-run state, and critical environment/config validation so tests catch environment failures. Covers local, CI, and ephemeral E2E targets.

  • Testing selection

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing/testing-selection Skill

    0★ repo

    Use to choose which test types and tools a project needs — Playwright (web/dashboard E2E), Maestro (mobile E2E/smoke), Supertest (backend API integration), Testing Library (components), Jest/Vitest (unit + integration logic). Selects only what the project's applications and risks justify; does not adopt every tool by default.

  • Unit testing

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing/unit-testing Skill

    0★ repo

    Use to plan and write unit tests for pure logic — functions, services, reducers, hooks — with Jest or Vitest, isolated from I/O, covering happy path, invalid input, and error path deterministically. Risk-driven, not coverage-percentage-driven.

  • Visual regression

    ahtishamshahzad/agent_dev_flow/.ai/skills/testing/visual-regression Skill

    0★ repo

    Use to decide whether visual regression testing is warranted and, if so, plan it — baseline snapshots of key screens/components, deterministic rendering, review-gated diffs, and scoped coverage — without turning it into a flaky, noise-generating burden.