agentsclimarketplace

Test

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

  • Fixture node skill

    AElfProject/aelf-skills/testdata/skills/fixture-node-skill Skill

    no license184★ repo

    Fixture node skill depending on fixture core.

  • Blue team

    gaasher/Agent-Loop-Skills/loops/blue-team Skill

    183★ repo

    Use when the user has concrete failing cases in code or a guardrail/classifier/filter/prompt/API they own — a red-team failure catalogue OR a CI/CD test-failure report (failing pytest/JUnit tests) — and wants the target patched until those failures are closed without breaking what already works. It points straight at the failed cases (normalize any source with tools/ingest.py), fixes one root-cause class per iteration, and re-checks with tools/verify.py — oracle mode against a red-team oracle, or tests mode against the test suite — keeping a patch only if it closes a class while nothing that passed before regresses, else reverting; loops until every class is closed (dry) or the budget runs out, then opens a pull request with the patch set. The defensive fixer half of a find→fix setup. Not for discovering new failures (that is red-team), and not for editing the oracle, tests, or holdout that define ground truth.

  • Claim verify

    gaasher/Agent-Loop-Skills/loops/claim-verify Skill

    183★ repo

    Use when the user has a results draft or a set of data-backed claims and wants each one adversarially verified against the underlying dataset before publishing — a pre-publication red-team of the findings. Extracts the discrete checkable claims from the draft, reproduces each claim's number against the data, stress-tests it against the threats most likely to kill it (outliers, confounds, Simpson's reversals, tiny subgroups, alternative specifications), and marks it verified, fragile, or refuted; fragile and refuted claims are revised — hedged, scoped, or retracted — until every claim is verified or appropriately qualified. The result is a draft where every surviving claim has been reproduced and survived a stress test. Not for open-ended discovery of new findings over a dataset (that is a data-analysis task), and not for diagnosing a single known anomaly or pipeline failure — this is a gate over an existing draft.

  • Optimize loop

    gaasher/Agent-Loop-Skills/loops/optimize-loop Skill

    183★ repo

    Use when the user wants to iteratively improve an artifact under a hard correctness bound while minimizing a measured cost — refactoring a code module to cut complexity while its test suite stays green, OR speeding up a SQL query while it returns the same rows. Each iteration applies one focused change, checks a correctness gate that must pass, measures a metric that must drop, and keeps the change only if both hold, else reverts; loops to a plateau or budget. Not for adding features, fixing bugs, or any change that is allowed to alter behaviour or results.

  • Plan loop

    gaasher/Agent-Loop-Skills/loops/plan-loop Skill

    183★ repo

    Use when the user has a coding or engineering prompt and wants it refined into a detailed, executable plan before any code is written — the planning stage of a prompt → plan → execute → debug pipeline. It decomposes the prompt from first principles (objective, end state, environment, building blocks, tools, packages), breaks the work into PR-sized tasks each tied to a component with its files, tests, and dependencies, orders them topologically, splits each into atomic subtasks, then a separate principal-engineer agent critiques the plan for alignment, coverage, sizing, and executability; it revises until the critique passes, emitting a plan.md layout and a structured tasks.json that a junior engineer or a smaller model can execute correctly. Not for executing, scaffolding, or debugging the plan (those are downstream loops), and not for research proposals or experiment plans.

  • Test quality

    techygarg/lattice/skills/atoms/test-quality Skill

    179★ repo

    Apply test quality principles when generating or reviewing test code. Enforces Arrange-Act-Assert structure, one behavior per test, assertion quality, test isolation, meaningful naming, and test data management. Use when writing tests, reviewing test code, or when the user mentions 'write tests', 'test this', 'test quality', 'test review', 'improve tests', or 'test structure'. This skill governs the craft of writing individual test cases -- not what to test (that is driven by the code being implemented) but how to write tests that are reliable, readable, and maintainable.

    The same file is in 1 other repository

  • Test quality

    techygarg/lattice/plugins/lattice/skills/test-quality Skill

    176★ repo

    Apply test quality principles when generating or reviewing test code. Enforces Arrange-Act-Assert structure, one behavior per test, assertion quality, test isolation, meaningful naming, and test data management. Use when writing tests, reviewing test code, or when the user mentions 'write tests', 'test this', 'test quality', 'test review', 'improve tests', or 'test structure'. This skill governs the craft of writing individual test cases -- not what to test (that is driven by the code being implemented) but how to write tests that are reliable, readable, and maintainable.

  • Spring boot

    sivaprasadreddy/sivalabs-agent-skills/skills/spring-boot Skill

    171★ repo

    Build Spring Boot 4.x applications following the best practices. Use this skill: * When developing Spring Boot applications using Spring MVC, Spring Data JPA, Spring Modulith, Spring Security * To create recommended Spring Boot package structure * To implement REST APIs, entities/repositories, service layer, modular monoliths * To use Thymeleaf view templates for building web applications * To write tests for REST APIs and Web applications * To write ArchUnit tests for testing architecture * To configure the recommended plugins and configurations to improve code quality, and testing while using Maven. * To use Spring Boot's Docker Compose support for local development * To create Taskfile for easier execution of common tasks while working with a Spring Boot application

    The same file is in 1 other repository

  • Qa methodology

    magnus919/agent-skills/qa-methodology Skill

    169★ repo

    Quality assurance methodology — test strategy design, test automation patterns, regression testing, CI quality gates, test data management, and quality metrics. Grounded in practical patterns for teams that want confident shipping.

  • Frappe testing cicd

    Impertio-Studio/Frappe_Claude_Skill_Package/skills/source/testing/frappe-testing-cicd Skill

    no license167★ repo

    Use when setting up CI/CD pipelines for Frappe apps, configuring GitHub Actions test workflows, or adding linting and security scanning. Prevents broken CI from incorrect test matrix configuration, missing MariaDB/Redis services, and uncaught code quality issues. Covers GitHub Actions workflows, test matrix (Python/Node versions), semgrep rules, pre-commit hooks, linting (ruff, eslint), CI test environment setup. Keywords: CI/CD, GitHub Actions, test matrix, semgrep, pre-commit, linting, ruff, eslint, continuous integration, automated tests, GitHub Actions, CI pipeline, pre-commit, code quality check..

  • Frappe testing unit

    Impertio-Studio/Frappe_Claude_Skill_Package/skills/source/testing/frappe-testing-unit Skill

    no license167★ repo

    Use when writing unit tests, integration tests, creating test fixtures, or running tests with bench run-tests. Prevents flaky tests from missing fixtures, incorrect test isolation, and wrong test base classes. Covers frappe.tests.utils, IntegrationTestCase, UnitTestCase, test fixtures, bench run-tests flags, test naming conventions. Keywords: unit test, integration test, IntegrationTestCase, fixtures, bench run-tests, frappe.tests, test_*.py, how to write test, test fixtures, run tests, test fails, bench run-tests example..

  • Initiating coverage

    w95/awesome-claude-corporate-skills/02-finance-accounting/initiating-coverage Skill

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

  • Test driven development

    w95/awesome-claude-corporate-skills/08-it-engineering/test-driven-development Skill

    150★ repo

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

    The same file is in 33 other repositories

  • Testing strategy

    w95/awesome-claude-corporate-skills/08-it-engineering/testing-strategy Skill

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

  • Webapp testing

    w95/awesome-claude-corporate-skills/08-it-engineering/webapp-testing Skill

    150★ 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 45 other repositories

  • Dart test coverage

    kevmoo/dash_skills/skills/dart-test-coverage Skill

    148★ repo

    Understand and improve test coverage in a Dart package. Helps agents run coverage, interpret results, and identify missed lines.

  • Dart test fundamentals

    kevmoo/dash_skills/skills/dart-test-fundamentals Skill

    148★ repo

    Core concepts and best practices for `package:test`. Covers `test`, `group`, lifecycle methods (`setUp`, `tearDown`), and configuration (`dart_test.yaml`).

  • Test skill

    serpro69/claude-toolbox/cmd/generate-kodex/testdata/source-plugin/skills/test-skill Skill

    no license147★ repo

    A test skill

  • Golang testing

    serpro69/claude-toolbox/cmd/vendor-profiles/testdata/skills/golang-testing Skill

    no license147★ repo

    Go testing best practices

  • Go testing

    cxuu/golang-skills/skills/go-testing Skill

    146★ repo

    Use when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff. Also use when a user asks to write a test for a Go function, even if they don't mention specific patterns like table-driven tests or subtests. Does not cover benchmark performance testing (see go-performance).

    The same file is in 3 other repositories

  • Flaky test triage

    apache/magpie/skills/flaky-test-triage Skill

    145★ repo

    Read-only flaky-test detection from GitHub Actions CI run history for one repository. Parses workflow run outcomes over a configurable window, computes per-job failure rates, and distinguishes intermittent failures (flaky) from consistent failures (deterministically broken). Produces a prioritised triage list without modifying any test code, workflow file, or tracker state.

  • Refactor

    arbiterForge/codeArbiter/core/surface/skills/refactor Skill

    141★ repo

    When you can't trust yourself with your code base, trust Arbiter.

  • Secret handling

    arbiterForge/codeArbiter/core/surface/skills/secret-handling Skill

    141★ repo

    When you can't trust yourself with your code base, trust Arbiter.

  • Subagent driven development

    arbiterForge/codeArbiter/core/surface/skills/subagent-driven-development Skill

    141★ repo

    When you can't trust yourself with your code base, trust Arbiter.

  • Tdd

    arbiterForge/codeArbiter/core/surface/skills/tdd Skill

    141★ repo

    When you can't trust yourself with your code base, trust Arbiter.

  • Refactor

    arbiterForge/codeArbiter/plugins/ca-codex/routines/refactor Skill

    141★ repo

    The behavior-preserving restructure gate. Routed to by /refactor for a rename, extract, inline, move, dedup, or internal-implementation swap. Six gated phases prove behavioral parity through unmodified pre-existing tests; any diff that classifies as `feat` is not a refactor and is routed to tdd. A modified pre-existing test is rejected as evidence — it is a behavior change in disguise.

  • Secret handling

    arbiterForge/codeArbiter/plugins/ca-codex/routines/secret-handling Skill

    141★ repo

    The secret-source gate. Routed to when changed code reads, writes, or passes a secret — API key, token, password, connection string, signing key, certificate, or any value that grants access. Validates that every secret comes from the approved store and never lands in source, log, test fixture, error response, image, or LLM prompt. The auth-crypto-reviewer agent is dispatched as the reviewer.

  • Subagent driven development

    arbiterForge/codeArbiter/plugins/ca-codex/routines/subagent-driven-development Skill

    141★ repo

    The implementation engine. Routed to by /sprint (full plan, autonomous) and by executing-plans (scoped batch, checkpoint-gated). One fresh subagent per task — test-first via tdd — followed by spec-compliance review, quality review, and fresh-run verification. No single context accumulates drift, and nothing is accepted on a subagent's word.

  • Tdd

    arbiterForge/codeArbiter/plugins/ca-codex/routines/tdd Skill

    141★ repo

    The test-first gate. Routed to by /feature (after the spec is approved), /fix, and /refactor before any implementation code is written. Six gated phases — obligation scan, red, green, obligation verify, coverage, lint. No feature code exists before Phase 1 clears; nothing reaches commit-gate until all six are green.

  • Ca fix

    arbiterForge/codeArbiter/plugins/ca-codex/skills/ca-fix Skill

    141★ repo

    Fix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates.

  • Refactor

    arbiterForge/codeArbiter/plugins/ca-pi/routines/refactor Skill

    141★ repo

    The behavior-preserving restructure gate. Routed to by /refactor for a rename, extract, inline, move, dedup, or internal-implementation swap. Six gated phases prove behavioral parity through unmodified pre-existing tests; any diff that classifies as `feat` is not a refactor and is routed to tdd. A modified pre-existing test is rejected as evidence — it is a behavior change in disguise.

  • Secret handling

    arbiterForge/codeArbiter/plugins/ca-pi/routines/secret-handling Skill

    141★ repo

    The secret-source gate. Routed to when changed code reads, writes, or passes a secret — API key, token, password, connection string, signing key, certificate, or any value that grants access. Validates that every secret comes from the approved store and never lands in source, log, test fixture, error response, image, or LLM prompt. The auth-crypto-reviewer agent is dispatched as the reviewer.

  • Subagent driven development

    arbiterForge/codeArbiter/plugins/ca-pi/routines/subagent-driven-development Skill

    141★ repo

    The implementation engine. Routed to by /sprint (full plan, autonomous) and by executing-plans (scoped batch, checkpoint-gated). One fresh subagent per task — test-first via tdd — followed by spec-compliance review, quality review, and fresh-run verification. No single context accumulates drift, and nothing is accepted on a subagent's word.

  • Tdd

    arbiterForge/codeArbiter/plugins/ca-pi/routines/tdd Skill

    141★ repo

    The test-first gate. Routed to by /feature (after the spec is approved), /fix, and /refactor before any implementation code is written. Six gated phases — obligation scan, red, green, obligation verify, coverage, lint. No feature code exists before Phase 1 clears; nothing reaches commit-gate until all six are green.

  • Ca doctor

    arbiterForge/codeArbiter/plugins/ca-pi/skills/ca-doctor Skill

    141★ repo

    Verify the active host install, package, command ownership, enforcement, wrapper self-test, and active-dispatch coverage gap. Read-only.

  • Ca fix

    arbiterForge/codeArbiter/plugins/ca-pi/skills/ca-fix Skill

    141★ repo

    Fix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates.

  • Refactor

    arbiterForge/codeArbiter/plugins/ca/skills/refactor Skill

    141★ repo

    The behavior-preserving restructure gate. Routed to by /refactor for a rename, extract, inline, move, dedup, or internal-implementation swap. Six gated phases prove behavioral parity through unmodified pre-existing tests; any diff that classifies as `feat` is not a refactor and is routed to tdd. A modified pre-existing test is rejected as evidence — it is a behavior change in disguise.

  • Secret handling

    arbiterForge/codeArbiter/plugins/ca/skills/secret-handling Skill

    141★ repo

    The secret-source gate. Routed to when changed code reads, writes, or passes a secret — API key, token, password, connection string, signing key, certificate, or any value that grants access. Validates that every secret comes from the approved store and never lands in source, log, test fixture, error response, image, or LLM prompt. The auth-crypto-reviewer agent is dispatched as the reviewer.

  • Subagent driven development

    arbiterForge/codeArbiter/plugins/ca/skills/subagent-driven-development Skill

    141★ repo

    The implementation engine. Routed to by /sprint (full plan, autonomous) and by executing-plans (scoped batch, checkpoint-gated). One fresh subagent per task — test-first via tdd — followed by spec-compliance review, quality review, and fresh-run verification. No single context accumulates drift, and nothing is accepted on a subagent's word.

  • Tdd

    arbiterForge/codeArbiter/plugins/ca/skills/tdd Skill

    141★ repo

    The test-first gate. Routed to by /feature (after the spec is approved), /fix, and /refactor before any implementation code is written. Six gated phases — obligation scan, red, green, obligation verify, coverage, lint. No feature code exists before Phase 1 clears; nothing reaches commit-gate until all six are green.

  • Pare test

    Dave-London/Pare/io.github.Dave-London/pare-test MCP server

    141★ repo

    Pare Test ג€” Auto-detects test framework (pytest, jest, vitest, mocha), returns typed JSON.

  • Test

    Dave-London/Pare/io.github.Dave-London/test MCP server

    141★ repo

    Auto-detects test framework (pytest, jest, vitest) and returns structured results.

  • Test

    popmechanic/VibesOS/skills/test Skill

    135★ repo

    Self-contained test automation — invoke directly, do not decompose. End-to-end integration test that assembles a fixture, deploys to Cloudflare (with auto-provisioned Connect), and presents a live URL for browser verification. Use when testing the plugin, running E2E tests, verifying deployment works, or checking that templates assemble correctly.

  • Test

    popmechanic/VibesOS/vibes-desktop/build/stable-macos-arm64/VibesOS.app/Contents/Resources/vibes-plugin/skills/test Skill

    135★ repo

    Self-contained test automation — invoke directly, do not decompose. End-to-end integration test that assembles a fixture, deploys to Cloudflare (with auto-provisioned Connect), and presents a live URL for browser verification. Use when testing the plugin, running E2E tests, verifying deployment works, or checking that templates assemble correctly.

  • Chaos experiment

    harness/harness-skills/skills/chaos-experiment Skill

    135★ repo

    Create and manage chaos experiments using Harness Chaos Engineering via MCP. Run resilience tests like pod deletion, CPU stress, and network faults. Use when user says "chaos experiment", "chaos engineering", "resilience test", "chaos test", or wants to test system reliability.

  • Optimize pipeline

    harness/harness-skills/skills/optimize-pipeline Skill

    135★ repo

    Optimize Harness CI/CD pipeline performance via MCP. Configure parallel test execution with Test Intelligence, design multi-layer caching strategies, analyze pipeline bottlenecks with stage-level timing breakdowns, optimize cache hit rates, and design monorepo CI pipelines with selective builds. Use when asked to speed up pipelines, improve cache hit rates, set up parallel testing, optimize build times, or configure monorepo builds. Do NOT use for creating new pipelines (use create-pipeline instead) or debugging failures (use debug-pipeline instead). Trigger phrases: pipeline speed, slow pipeline, cache hit rate, parallel tests, test intelligence, build optimization, caching strategy, monorepo pipeline, pipeline bottleneck, build speed.

  • Httpie

    jjmartres/opencode/opencode/skills/httpie Skill

    133★ repo

    Use this skill whenever the user wants to make HTTP requests, test APIs, call REST endpoints, debug web services, or interact with any HTTP/HTTPS API using the HTTPie CLI tool (`http` command). Trigger this skill for any request involving: sending GET/POST/PUT/PATCH/DELETE requests, testing API endpoints, sending JSON or form data, working with authentication (Bearer token, Basic auth), uploading files, downloading responses, managing sessions, inspecting request/response headers, or piping HTTP calls in shell scripts. Use this skill even when the user just says "call the API", "send a request", "hit this endpoint", or "test with httpie" ¿ don't wait for explicit httpie mention.

    The same file is in 1 other repository

  • Bug fix protocol

    CodeAlive-AI/ai-driven-development/skills/bug-fix-protocol Skill

    127★ repo

    8-step disciplined bug-fix protocol that treats every production bug as two failures — the code defect itself and the testing system that allowed it through. Use when fixing a production bug, investigating a regression, writing a post-mortem, or auditing a missed defect. Triggers on "fix this bug", "production bug", "regression test", "post-mortem", "test gap", "why did the tests miss this".

  • Windows qa engineer

    CodeAlive-AI/ai-driven-development/skills/windows-qa-engineer Skill

    127★ repo

    Use when testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP. Triggers on "test this Windows app", "QA the app", "run smoke test", "click the button", "fill the form", "check the UI", "Windows automation", "UFO QA", "verify the dialog", or any Windows desktop UI testing task. Not for web/browser testing (use Playwright), mobile testing, or non-Windows platforms.

  • Testing dbt models

    AltimateAI/data-engineering-skills/skills/dbt/testing-dbt-models Skill

    120★ repo

    Adds schema tests and data quality validation to dbt models. Use when working with dbt tests for: (1) Adding or modifying tests in schema.yml files (2) Task mentions "test", "validate", "data quality", "unique", "not_null", or "accepted_values" (3) Ensuring data integrity - primary keys, foreign keys, relationships (4) Debugging test failures or understanding why dbt test failed Matches existing project test patterns and YAML style before adding new tests.

    The same file is in 4 other repositories

  • Tdd

    itseffi/agentic-os/.agents/skills/tdd Skill

    120★ repo

    Test-driven development - write failing test first, then minimal code. Use before implementing any feature or bugfix.

  • E2e testing patterns

    aAAaqwq/AGI-Super-Team/skills/e2e-testing-patterns Skill

    120★ repo

    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.

    The same file is in 2 other repositories

  • E2e testing

    aAAaqwq/AGI-Super-Team/skills/e2e-testing Skill

    120★ repo

    Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.

    The same file is in 9 other repositories

  • Market ab test setup

    aAAaqwq/AGI-Super-Team/skills/market-ab-test-setup Skill

    120★ repo

    When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.

  • Playwright automation

    aAAaqwq/AGI-Super-Team/skills/playwright-automation Skill

    120★ repo

    Playwright 浏览器自动化。用于自动化爬虫、数据采集、表单填写、UI 测试等需要浏览器自动化的场景。无需人工干预,适合 cron 定时任务。

  • Sp test driven development

    aAAaqwq/AGI-Super-Team/skills/sp-test-driven-development Skill

    120★ repo

    Write the test first, watch it fail, write minimal code to pass

  • Sp testing anti patterns

    aAAaqwq/AGI-Super-Team/skills/sp-testing-anti-patterns Skill

    120★ repo

    Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.

  • Synthetic market research

    aAAaqwq/AGI-Super-Team/skills/synthetic-market-research Skill

    120★ repo

    You are an expert market researcher who uses LLM-generated synthetic survey responses and Semantic Similarity Rating (SSR) to produce fast, cheap, dir Fast, cheap market research using LLM-generated synthetic survey responses with Semantic Similarity Rating (SSR). Runs purchase intent, concept tests, and pricing research in minutes instead of weeks, at $0 per respondent. Based on PyMC Labs' validated methodology (90% correlation with real humans across 57 surveys). Triggers: synthetic research, market research, survey, purchase intent, concept test, consumer research, SSR, synthetic survey, product validation, pricing research, Likert scale.

  • Tdd guide

    aAAaqwq/AGI-Super-Team/skills/tdd-guide Skill

    120★ repo

    Test-driven development workflow with test generation, coverage analysis, and multi-framework support

  • Tdd workflow

    aAAaqwq/AGI-Super-Team/skills/tdd-workflow Skill

    120★ repo

    Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

    The same file is in 8 other repositories