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

  • Browser verification

    SWEStash/swe-workflow-skills/plugins/qa/skills/browser-verification Skill

    1★ repo

    Verify a web app change by driving the real UI in a browser — reproduce the user flow end to end, watch console errors and network failures, exercise loading/error/empty states, capture screenshots as evidence. Use before claiming a UI change works. Triggers: check it in the browser, verify the UI, click through the flow, console errors, test it like a user, smoke test the frontend. Designing persistent test suites → test-suite-design; the generic done-gate → verification-before-completion (this is its browser-specific practice).

  • Code slop cleanup

    SWEStash/swe-workflow-skills/plugins/qa/skills/code-slop-cleanup Skill

    1★ repo

    Strip AI slop from a branch diff before PR — judge each hunk against the surrounding file's conventions, remove without changing behavior, re-run tests. Removal only: hunting bugs → code-reviewing; structural improvement → refactoring; repo-wide audit → technical-debt-review; pruning tests → test-suite-design.

  • Tdd workflow

    SWEStash/swe-workflow-skills/plugins/qa/skills/tdd-workflow Skill

    1★ repo

    Guide test-driven development with red-green-refactor. For NEW code via test-first — use test-suite-design for adding tests to existing code.

  • Test data strategy

    SWEStash/swe-workflow-skills/plugins/qa/skills/test-data-strategy Skill

    1★ repo

    Design and generate test data — factories, synthetic data, property-based testing, boundary analysis, contract testing, load scenarios, GDPR-safe data. Triggers: test data, synthetic data, fake data, factory, seed data, fixtures, property-based testing, fuzz testing, boundary values, contract testing, Pact, load test data, anonymize, GDPR test data.

  • Test suite design

    SWEStash/swe-workflow-skills/plugins/qa/skills/test-suite-design Skill

    1★ repo

    Design comprehensive test suites for existing code — strategy across unit/integration/e2e, fixtures, factories, helpers. Triggers: add tests, write tests for, increase coverage, test this module, testing strategy, test plan, what tests do I need, test infrastructure, test helpers, this has no tests. Not for TDD — use tdd-workflow.

  • Project review

    SWEStash/swe-workflow-skills/plugins/strategy/skills/project-review Skill

    1★ repo

    Review a built project's execution health before a milestone — scope alignment, roadmap / execution-plan adherence, implementation maturity (what's production-ready vs stub/deferred), and the evidence it actually works (tests, coverage, validation results, changelog). Use strategic-review for vision/positioning/market; technical-debt-review for a pure code-health audit.

  • Browser verification

    SWEStash/swe-workflow-skills/skills/browser-verification Skill

    1★ repo

    Verify a web app change by driving the real UI in a browser — reproduce the user flow end to end, watch console errors and network failures, exercise loading/error/empty states, capture screenshots as evidence. Use before claiming a UI change works. Triggers: check it in the browser, verify the UI, click through the flow, console errors, test it like a user, smoke test the frontend. Designing persistent test suites → test-suite-design; the generic done-gate → verification-before-completion (this is its browser-specific practice).

  • Cicd pipeline

    SWEStash/swe-workflow-skills/skills/cicd-pipeline Skill

    1★ repo

    Design CI/CD pipelines for automated build, test, deploy — GitHub Actions, GitLab CI, quality gates. Triggers: CI/CD, pipeline, GitHub Actions, GitLab CI, workflow, automated deployment, build pipeline, continuous integration, continuous deployment, automate tests on PR, deploy automatically, quality gate.

  • Code slop cleanup

    SWEStash/swe-workflow-skills/skills/code-slop-cleanup Skill

    1★ repo

    A comprehensive SWE workflow, encoded. Might be useful to you too.

  • Data quality

    SWEStash/swe-workflow-skills/skills/data-quality Skill

    1★ repo

    Keep warehouse and pipeline data trustworthy — dbt tests, expectations (Great Expectations/Soda), data contracts with upstream producers, source freshness, schema-drift and volume anomaly detection, lineage and blast radius, severity and alerting. Triggers: data quality, bad data in dashboards, data validation, dbt tests, data contract, schema drift, stale data, freshness check, duplicate rows, nulls in the warehouse, data lineage, data SLA, upstream schema change broke us. Generating test/synthetic data → test-data-strategy; schema design → data-modeling.

  • Dx audit

    SWEStash/swe-workflow-skills/skills/dx-audit Skill

    1★ repo

    Audit and improve developer experience — inner-loop feedback (build/test/reload times), CI wait and queue times, flaky tests, local environment setup, onboarding time-to-first-PR, tooling friction, docs discoverability; produce a prioritized remediation plan. Triggers: developer experience, DX audit, devex, builds are slow, CI takes forever, flaky tests, onboarding takes weeks, tooling friction, developer productivity, engineers are frustrated. Code health/debt hotspots → technical-debt-review; designing one pipeline → cicd-pipeline.

  • Project review

    SWEStash/swe-workflow-skills/skills/project-review Skill

    1★ repo

    Review a built project's execution health before a milestone — scope alignment, roadmap / execution-plan adherence, implementation maturity (what's production-ready vs stub/deferred), and the evidence it actually works (tests, coverage, validation results, changelog). Use strategic-review for vision/positioning/market; technical-debt-review for a pure code-health audit.

  • Statistical analysis

    SWEStash/swe-workflow-skills/skills/statistical-analysis Skill

    1★ repo

    Design and analyze experiments and statistical tests — test selection with stated assumptions, sample size and power, effect sizes and confidence intervals over bare p-values, and pitfall discipline (multiple comparisons, p-hacking, peeking/optional stopping). Owns experiment statistics generally; live A/B evaluation of AI/LLM apps (quality metrics, judges, feedback) → ai-evaluation.

  • Tdd workflow

    SWEStash/swe-workflow-skills/skills/tdd-workflow Skill

    1★ repo

    Guide test-driven development with red-green-refactor. For NEW code via test-first — use test-suite-design for adding tests to existing code.

  • Test data strategy

    SWEStash/swe-workflow-skills/skills/test-data-strategy Skill

    1★ repo

    Design and generate test data — factories, synthetic data, property-based testing, boundary analysis, contract testing, load scenarios, GDPR-safe data. Triggers: test data, synthetic data, fake data, factory, seed data, fixtures, property-based testing, fuzz testing, boundary values, contract testing, Pact, load test data, anonymize, GDPR test data.

  • Test suite design

    SWEStash/swe-workflow-skills/skills/test-suite-design Skill

    1★ repo

    Design comprehensive test suites for existing code — strategy across unit/integration/e2e, fixtures, factories, helpers. Triggers: add tests, write tests for, increase coverage, test this module, testing strategy, test plan, what tests do I need, test infrastructure, test helpers, this has no tests. Not for TDD — use tdd-workflow.

  • E2e runbooks

    Lukk17/agent-standards/.agents/skills/e2e-runbooks Skill

    1★ repo

    Use whenever the user wants to add, run, or refine an end-to-end capability test (one feature exercised against a live stack, behaviour-only assertions, manual or AI-runnable). Triggers on phrases like "add an e2e test for X", "verify the upload flow end-to-end", "run the e2e sweep", "test that the MCP tool actually fires", "smoke test against the staging stack", "build a capability test for the auth flow". Methodology covers spec / tasks-template / runs triple, behaviour-only assertions, canary fixtures, number-by-setup-cost ordering, per-run token + duration accounting, and API client alternatives (Bruno / hurl / curl / VS Code REST Client / httpie). Distinct from the `e2e-testing` skill (Playwright UI testing); this one is for backend capability sweeps. Pairs with the `e2e-runbooks` OpenSpec schema at [Lukk17/openspec-schemas](https://github.com/Lukk17/openspec-schemas) for projects using OpenSpec.

  • E2e testing

    Lukk17/agent-standards/.agents/skills/e2e-testing Skill

    1★ repo

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

  • Flutter testing apps

    Lukk17/agent-standards/.agents/skills/flutter-testing-apps Skill

    1★ repo

    Implements unit, widget, and integration tests for a Flutter app. Use when ensuring code quality and preventing regressions through automated testing.

  • Golang testing

    Lukk17/agent-standards/.agents/skills/golang-testing Skill

    1★ repo

    Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.

  • Python testing

    Lukk17/agent-standards/.agents/skills/python-testing Skill

    1★ repo

    Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.

  • Springboot tdd

    Lukk17/agent-standards/.agents/skills/springboot-tdd Skill

    1★ repo

    Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.

  • Springboot verification

    Lukk17/agent-standards/.agents/skills/springboot-verification Skill

    1★ repo

    Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.

  • Tdd workflow

    Lukk17/agent-standards/.agents/skills/tdd-workflow Skill

    1★ repo

    Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with around 90% line coverage of real logic including unit, integration, and E2E tests.

  • Numerical investigation

    leon2k2k2k/agent-skills/numerical-investigation Skill

    1★ repo

    Complete guide for numerical mathematical investigations. Conducts structured interview to understand background, designs implementation and tests, creates detailed plan, then executes code, testing, and reporting.

  • Preflight

    Background-Craft/hydrant-skills/skills/preflight Skill

    1★ repo

    Run the pre-PR quality gate on a Hydrant branch — lint, build, tests, coverage assessment, acceptance-criteria check, dependency-graph verification, production-safety review, and adversarial review. Use when the user asks for `/preflight`, says "preflight HYD-123", or wants final validation before shipping.

  • Tdd pruning pre prune

    stevennitesh/programming-agent-skills/docs/validation/evals/tdd-pruning-pre-prune Skill

    1★ repo

    Use for tracer-bullet red-green-refactor on red-testable new behavior. For bugs, use only when expected behavior, the exact symptom, the cause, and a trusted red-capable reproduction are known. Hand off bugs when any of those facts is uncertain to $diagnosing-bugs; hand off throwaway design questions to $prototype.

  • Tdd slice

    stevennitesh/programming-agent-skills/skills/.archive/tdd-slice Skill

    1★ repo

    Use when approved work changes caller-visible or user-visible behavior, adds a new behavior path, or an understood bug needs a new durable behavior or regression check.

  • Tdd

    stevennitesh/programming-agent-skills/skills/custom/tdd Skill

    1★ repo

    Use for tracer-bullet red-green-refactor on red-testable new behavior. For bugs, use only when expected behavior, the exact symptom, the cause, and a trusted red-capable reproduction are known. Hand off bugs when any of those facts is uncertain to $diagnosing-bugs; hand off throwaway design questions to $prototype.

  • Analyze tests

    lgtm-hq/ai-skills/skills/analyze-tests Skill

    1★ repo

    Test suite analysis. Use when asked to analyze, review, or evaluate a project's tests for quality, coverage gaps, and best practices.

  • Stand general

    lgtm-hq/ai-skills/skills/stand-general Skill

    1★ repo

    Global coding standards for all projects and languages. Use when writing any code. Covers linting with lintro, testing with coverage, semantic commits, PR creation, and pre-push AI review with coderabbit and greptile CLIs.

  • Test api

    lgtm-hq/ai-skills/skills/test-api Skill

    1★ repo

    Playwright API testing best practices. Use when writing REST API tests with Playwright. Enforces Zod schema validation, client/fixture separation, and contract testing.

  • Test shell

    lgtm-hq/ai-skills/skills/test-shell Skill

    1★ repo

    BATS shell script testing. Use when writing or running shell script tests. Covers setup/teardown, assertions, mocking, helper patterns, and coverage with kcov.

  • Test ui qsf

    lgtm-hq/ai-skills/skills/test-ui-qsf Skill

    1★ repo

    QSF project conventions for the Playwright E2E suite. Use when working in the QSF playwright-tests directory (authFixtures, ___ping-* handles, data-test-label test IDs, .auth storage states) — not for generic Playwright advice.

  • Test ui

    lgtm-hq/ai-skills/skills/test-ui Skill

    1★ repo

    Playwright E2E testing best practices. Use when writing browser tests, visual regression, or accessibility tests in any project. Enforces user-facing locators, auto-waiting, web-first assertions, and Page Object Model.

  • Test

    lgtm-hq/ai-skills/skills/test Skill

    1★ repo

    Run tests with coverage reporting. Auto-detects test frameworks (Vitest, Playwright, RSpec, pytest, Jest, BATS, etc.) and runs appropriate test commands. Use when asked to run tests, check coverage, or validate code.

  • Turbo test

    lgtm-hq/ai-skills/skills/turbo-test Skill

    1★ repo

    Canonical Agent Skills library for Claude Code, Cursor, Codex, and other agents.

  • Local ci

    jsirish/workflow-skills/skills/local-ci Skill

    no license1★ repo

    Cross-project agent workflow skills — session onboarding, handoffs, PR review, and merge workflows

  • Visual regression upgrade

    jsirish/workflow-skills/skills/visual-regression-upgrade Skill

    no license1★ repo

    Verify visual parity between two web environments (production vs upgraded/UAT) by capturing full-page screenshots of matching URLs and producing a pixel-diff HTML report. USE THIS SKILL whenever an agent needs to answer "does it look the same", "check the upgrade visually", "compare prod and UAT", "did the layout change", "screenshot diff", "visual regression", or verify a CMS major-version upgrade (SilverStripe 4→5, Drupal 9→10, WordPress major bumps) hasn't broken the front-end. Self-contained — bundles a Playwright capture script, URL crawler, and pixel-diff report generator.

    The same file is in 1 other repository

  • Test and verify

    sainzs/santiagosainz-skills/skills/core/test-and-verify Skill

    1★ repo

    Test and verify one behavior through a tight evidence loop: baseline, failing proof when useful, minimal edit, and final proof. Use for tests, verification, TDD, regression-proofing, smoke checks, readiness validation, or prove-change.

  • Migrate to shoehorn

    rmerk/crewai-headless-flow/.agents/skills/migrate-to-shoehorn Skill

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

  • Tdd

    rmerk/crewai-headless-flow/.agents/skills/tdd Skill

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

  • Jira ticket plan audit

    rmerk/crewai-headless-flow/vendor/agent-skills/skills/jira-ticket-plan-audit Skill

    1★ repo

    Audit a PR diff against a saved Jira implementation plan at .agents/jira-plans/{KEY}.md. Checks file coverage, test strategy, backend escalation scope, and scope creep. Use after jira-ticket-implement or when user says audit AS-12345 against plan.

  • Test driven development

    rmerk/crewai-headless-flow/vendor/agent-skills/skills/test-driven-development Skill

    1★ repo

    Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

    The same file is in 7 other repositories

  • Harness testing

    looties-io/looties-skills/harness-testing Skill

    1★ repo

    Use when writing, designing, or strengthening harness tests — tests that boot a larger unit of a system (an HTTP handler, a job, a UI flow) into a realistic but controlled environment (fake requests, mocked services/APIs, controlled env vars, an in-memory/seeded database, fake timers) and assert end-to-end behavior. Use when asked to "test the whole handler", "integration test without a real DB/network", "mock the services and run the real code path", "add a test harness", or to improve reliability of code that only misbehaves when wired to its dependencies. Framework-agnostic; includes notes for TypeScript/Deno/Node, Python, and Go.

  • Feynman

    patrick204nqh/skills/skills/structure/feynman Skill

    1★ repo

    Tests whether the user actually understands a topic by explaining it back in plain language, then naming the specific point where the explanation gets fuzzy or hand-wavy — and proposes the smallest next step to close that gap. Make sure to use this skill whenever the user says "Feynman", "test my understanding", "do I actually understand this", "find the gap", "what am I missing", "I think I get it but…", "explain it back to me", or asks the agent to check their grasp of a topic rather than just present information — even if they don't use those exact phrases.

  • Testing

    tdyzzsp47/claude-skills/skills/testing Skill

    1★ repo

    単体・結合・E2Eテストの戦略立案から実装・自動化までをカバーするスキル。テストピラミッドに基づく適切なテスト配分、テストケースの設計技法、フレーキーテスト対策が必要なときに使う。

  • Unopim dev cycle

    unopim/agent-skills/skills/unopim-dev-cycle Skill

    1★ repo

    Development workflow for UnoPim. Activates when running tests, linting code, building assets, or debugging; or when the user mentions test, lint, pint, build, npm, pest, format, style, quality, coverage, or needs to verify code works.

  • Stress test the plan

    k-anss/whetstone/skills/stress-test-the-plan Skill

    1★ repo

    Red-team a decision or plan: surface its fatal flaw, expose hidden assumptions, and trace how it fails over multiple rounds — deliberately pessimistic, no comfort, no rubber-stamping. Trigger when the user says "stress-test this plan", "red-team my decision", "find the holes", "what am I missing", or "argue against this". Do NOT trigger — and the skill must say so — when the user is in emotional distress, or has already decided and is executing (then only "how to die less", not "should you do it"). It also declares its own bias: it is deliberately pessimistic and can talk a good opportunity out of existence; the real call sits between this and a normal read.

  • Repro first

    Rookage/agent-discipline/skills/repro-first Skill

    1★ repo

    Use when debugging bugs, failures, broken behavior, flaky tests, regressions, crashes, or performance issues. Build a reproducible feedback loop before hypothesizing or fixing; useful when the user says debug, diagnose, failing, broken, cannot use, slow, or error.

  • Test driven development

    roronoazoroshao369/vibe-coding-os/skills/core/test-driven-development Skill

    1★ repo

    Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.

  • Test fixture library

    roronoazoroshao369/vibe-coding-os/skills/core/test-fixture-library Skill

    1★ repo

    Reusable test fixtures in tests/fixtures/*.json with declarative schema. Generated test cases feed into injection counters, redactor, and validation gates.

  • Test modernizer

    jlreyes/swift-agent-kit/skills/test-modernizer Skill

    no license1★ repo

    Apple's guide for modernizing test suites: migrating XCTest to Swift Testing and restructuring existing Swift Testing tests around newer features. Use when asked to modernize, migrate, or convert tests; not for writing brand-new tests, running tests, or XCUI automation (which cannot migrate). (Content extracted from your local Xcode on install.)

  • Tachyon slack notify

    quantum-box/agent-packages/plugins/tachyon/skills/tachyon-slack-notify Skill

    no license1★ repo

    Distribution repository for agent skills and plugins

  • Direct response creative testing

    scumunna/programmatic-skills/skills/direct-response-creative-testing Skill

    1★ repo

    Design, run, and read direct-response creative tests across programmatic and paid-social campaigns. Use when the user asks how to test creative, compare hooks or offers, read asset-level performance, avoid false winners, manage fatigue, set a creative learning agenda, run holdouts, decide when a test is significant enough to act, or brief the next batch of conversion creative.

  • Openclaw agent browser

    yzp100911/CrabAgent/xCrab/skills/openclaw-agent-browser Skill

    1★ repo

    Headless browser automation CLI for AI agents. Use when interacting with websites — navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, scraping, testing web apps, downloading files, or automating any browser task. Triggers on requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data", "test this web app", "login to a site", "monitor a page", or any task requiring programmatic web interaction.

    The same file is in 2 other repositories

  • Qa

    mtthsnc/tempest/plugins/tempest/skills/qa Skill

    1★ repo

    Use when you must verify a change actually works through the REAL browser UI — acceptance, end-to-end, smoke tests, form interactions, navigation, login flows — driven by the agent-browser tool. Invoke when "click through it", "does the UI work", "smoke test the page", or browser-level evidence (screenshots, assertions) is wanted, not just unit tests. Produces PASS/FAIL backed by a verified assertion and a saved screenshot.

  • Aurelia ecosystem

    Expert-Vision-Software/aurelia-expert/skills/aurelia-ecosystem Skill

    1★ repo

    Wire first-party Aurelia v2 plugins and ecosystem concerns into an app — picks the right reference for HTTP/fetch-client, validation, dialog, state, i18n, forms, testing, and SSR/prerendering. Use when adding @aurelia/fetch-client, @aurelia/validation, @aurelia/dialog, @aurelia/state, or @aurelia/i18n; writing Vitest + @aurelia/testing component tests; binding forms with model.bind/matcher.bind; or configuring server-side rendering, prerendering, hydration, sitemap/robots, and client takeover. Leading word — wire.

  • Foo skill

    flowleap-ai/flowleap-plugins/test/fixtures/invalid-marketplace-missing-name/plugins/foo/skills/foo-skill Skill

    1★ repo

    A well-formed fixture skill; the failure under test lives in marketplace.json, not here.

  • Diagnose

    yoelgal/better-dev/skills/diagnose Skill

    1★ repo

    Use when a bug, regression, crash, flaky test, or a report that "X is broken / throwing / failing / slow", "why is prod down", or "make it faster" needs root-causing before any fix - the fix-side entry into the work-item loop, where a symptom becomes a reproducible red signal and a root cause.