agentsclimarketplace

Test

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

  • Clean shell

    uwuclxdy/agenticat/skills/clean-shell Skill

    5★ repo

    Defensive Bash/POSIX shell quality: strict-mode `set` flags, traps, idempotent mutation of live systems (deploy, sshd/sudoers, systemd), ShellCheck discipline, bats-core tests. Use when writing, hardening, reviewing, or testing shell scripts, or wiring shellcheck/bats into CI.

  • Emulator testing

    uwuclxdy/agenticat/skills/emulator-testing Skill

    5★ repo

    Boots and drives Android AVDs and iOS simulators from the CLI (adb, `xcrun simctl`, `integration_test`, Alchemist goldens). Use for headless app tests, screenshot verification, or emulator boot/GPU issues.

  • Webapp testing

    uwuclxdy/agenticat/skills/webapp-testing Skill

    5★ repo

    Playwright toolkit for local web apps: Python scripts that navigate, click, fill forms, capture screenshots, and read console logs against a dev server or static HTML. Use to verify or debug frontend behavior.

  • Junit testing

    VersoXBT/claude-initial-setup/skills/java/junit-testing Skill

    4★ repo

    JUnit 5 testing patterns including annotations, Mockito mocking, Spring Boot test slices, MockMvc, Testcontainers integration, and parameterized tests. Use when the user is writing Java tests, setting up test infrastructure, mocking dependencies, testing Spring controllers, or running integration tests with real databases. Trigger on any mention of JUnit, Mockito, @SpringBootTest, MockMvc, Testcontainers, or Java testing.

  • Mcp server creation

    VersoXBT/claude-initial-setup/skills/mcp-development/mcp-server-creation Skill

    4★ repo

    Guide for creating MCP (Model Context Protocol) servers in TypeScript and Python, including scaffolding, transports, lifecycle hooks, and testing. Use when the user wants to build an MCP server, add tools/resources/prompts to an MCP server, configure stdio or SSE transport, or test MCP server functionality.

  • Mocking strategies

    VersoXBT/claude-initial-setup/skills/testing/mocking-strategies Skill

    4★ repo

    Mocks vs stubs vs spies, dependency injection for testing, jest.mock/unittest.mock/gomock, and when NOT to mock. Use when the user needs to isolate dependencies in tests, asks about mocking external services, or has tests tightly coupled to implementation details.

  • Tdd workflow

    VersoXBT/claude-initial-setup/skills/testing/tdd-workflow Skill

    4★ repo

    Red-green-refactor TDD cycle, test-first methodology, coverage targets (80%+), and test pyramid. Use when the user is implementing a new feature, fixing a bug, asks about TDD, or mentions writing tests before code. Always push for test-first.

  • Test architecture

    VersoXBT/claude-initial-setup/skills/testing/test-architecture Skill

    4★ repo

    Test organization, fixtures, factories (factory_boy/faker), test isolation, database cleanup, and test configuration. Use when the user is setting up a test suite, organizing test files, creating test fixtures, or dealing with test isolation issues.

  • Creo test

    oyusypenko/creo/skills/creo-test Skill

    4★ repo

    Testing orchestration that routes to unit test and E2E test subagents. Manages test plans, coverage tracking, and coordinates test execution across the full stack. Supports Vitest/Jest for unit tests and Playwright for E2E tests. Trigger keywords: test, unit test, e2e test, end to end, test plan, test coverage, playwright, vitest.

  • Pi iteration workflow

    ralvarezdev/ralvaskills/skills/personal/pi-iteration-workflow Skill

    4★ repo

    Edit-test workflow for the voldemorbot robot codebase — Windows-to-Pi SSH deploy loop, pixi/ROS2 rebuild triggers, flaky-WiFi survival via screen, PowerShell SSH quoting pitfalls, sudo caching on the Pi Zero. Use when pushing platform/robot changes to hardware, restarting the robot service, or a Pi SSH session misbehaves.

  • Tdd

    ralvarezdev/ralvaskills/skills/workflows/tdd Skill

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

  • Controller tests

    soden46/syarif-laravel-ai-skills/skills/controller-tests Skill

    4★ repo

    Laravel guidance to write focused controller tests using HTTP assertions; keep heavy logic in Actions/Services and unit test them

  • E2e playwright

    soden46/syarif-laravel-ai-skills/skills/e2e-playwright Skill

    4★ repo

    Laravel E2E testing with official Playwright patterns for locators, auth state, seeds, traces, screenshots, CI, and cross-browser workflows.

  • Aie web qa

    mrhinkle/aienterprise-skills/plugins/aie-web/skills/aie-web-qa Skill

    4★ repo

    Runs a unified pre-launch or post-update quality-assurance pass on a website — the holistic "does this actually work?" gate. Walks pages, forms, navigation, third-party integrations, cross-browser and mobile behavior, JavaScript console health, accessibility basics, HTTPS/security, and a performance smoke test. Produces a QA report with issues rated by severity, reproduction steps, and a launch recommendation; supports regression testing after fixes. Stack-agnostic. Trigger on "QA my site," "test my site," "does everything work," "smoke test," "test before launch," "regression test," "check all pages," "test my forms," "check mobile," "cross-browser test," "broken links," or "is my site ready to launch."

  • Aie web testing

    mrhinkle/aienterprise-skills/plugins/aie-web/skills/aie-web-testing Skill

    4★ repo

    Write and run automated browser tests for a web app using Playwright — smoke tests, critical user journeys (sign-up, login, contact/checkout forms), navigation, and console/network-error checks — then report pass/fail with screenshots and repro steps. Scaffolds Playwright if the project doesn't have it, uses resilient role/text selectors, and can wire tests into CI. Complements a manual QA pass with real automation. Works with any stack the browser can load (React, Next.js, Vue, Svelte, plain HTML, WordPress). Trigger on "write tests for my site," "add Playwright tests," "test this user flow," "end-to-end tests," "e2e," "browser tests," "test my signup/checkout," or "set up automated testing."

  • Skill function test

    Ldxs001/workbuddy-skills/skills/skill-function-test Skill

    4★ repo

    技能场景测试套件 —— 备份 → 蓝皮书 → 配置确认 → S1-S3场景测试 → D1-D6功能测试 → S4执行忠实度 → 修复 → bump → 双格式报告 → 结论写入test-report.md。配置驱动流程,钩子强制阻断。

  • Pressure test

    escoffier-labs/skillet/skillet/skills/pressure-test Skill

    4★ repo

    A skillet full of agent skills that actually ship work. Production-tested SKILL.md workflows for audits, security, releases, and handoffs.

  • Refire

    escoffier-labs/skillet/skillet/skills/refire Skill

    4★ repo

    A skillet full of agent skills that actually ship work. Production-tested SKILL.md workflows for audits, security, releases, and handoffs.

  • Eval driven dev

    MarieLynneBlock/arcanum-artifex/skills/agentic/evaluation/eval-driven-dev Skill

    no license4★ repo

    Build an automated evaluation pipeline that tests a Python LLM application end-to-end with pixie test — real code paths, real LLM calls, instrumented external data — and scores outputs with evaluators instead of assertions. Use when adding evals to a Python AI app.

  • Acceptance test plan

    MarieLynneBlock/arcanum-artifex/skills/analysis/acceptance-test-plan Skill

    no license4★ repo

    Produces a traceable acceptance test plan with individually numbered test cases. Each test case maps to a source requirement (user story, use case, or FR), specifies preconditions, steps, and expected results, and includes coverage of the happy path, edge cases, and negative scenarios.

  • Hypothesis testing and ab evaluation

    MarieLynneBlock/arcanum-artifex/skills/data-science/hypothesis-testing-and-ab-evaluation Skill

    no license4★ repo

    [TODO] Define the specific workflow this skill standardises, including default libraries, quality checks, and expected deliverables.

  • Csharp nunit

    MarieLynneBlock/arcanum-artifex/skills/development/dotnet/csharp-nunit Skill

    no license4★ repo

    Get best practices for NUnit unit testing, including data-driven tests

  • Csharp tunit

    MarieLynneBlock/arcanum-artifex/skills/development/dotnet/csharp-tunit Skill

    no license4★ repo

    Get best practices for TUnit unit testing, including data-driven tests

  • Csharp xunit

    MarieLynneBlock/arcanum-artifex/skills/development/dotnet/csharp-xunit Skill

    no license4★ repo

    Get best practices for XUnit unit testing, including data-driven tests

  • Java junit

    MarieLynneBlock/arcanum-artifex/skills/development/java/java-junit Skill

    no license4★ repo

    Get best practices for JUnit 5 unit testing, including data-driven tests

  • Pytest coverage

    MarieLynneBlock/arcanum-artifex/skills/development/python/pytest-coverage Skill

    no license4★ repo

    Run pytest tests with coverage, discover lines missing coverage, and increase coverage to 100%.

  • Test strategy

    MarieLynneBlock/arcanum-artifex/skills/development/test-strategy Skill

    no license4★ repo

    Produces a test strategy document defining what to test, at which layer, with which tools, and to what coverage standard. It applies the test pyramid model, surfaces coverage gaps in existing codebases, and produces a concrete plan — not a generic "write more tests" recommendation.

  • Javascript typescript jest

    MarieLynneBlock/arcanum-artifex/skills/development/typescript/javascript-typescript-jest Skill

    no license4★ repo

    Best practices for writing JavaScript/TypeScript tests using Jest, including mocking strategies, test structure, and common patterns.

  • Hypothesis generation

    MarieLynneBlock/arcanum-artifex/skills/scientific/hypothesis-generation Skill

    no license4★ repo

    Structured hypothesis formulation from observations. Use when you have experimental observations or data and need to formulate testable hypotheses with predictions, propose mechanisms, and design experiments to test them. Follows scientific method framework. For open-ended ideation use scientific-brainstorming; for automated LLM-driven hypothesis testing on datasets use hypogenic.

  • Statistical analysis

    MarieLynneBlock/arcanum-artifex/skills/scientific/statistical-analysis Skill

    no license4★ repo

    Guided statistical analysis with test selection and reporting. Use when you need help choosing appropriate tests for your data, assumption checking, power analysis, and APA-formatted results. Best for academic research reporting, test selection guidance. For implementing specific models programmatically use statsmodels.

  • Swift testing

    jeremieb/swift-unit-test-instructions/skills/swift-testing Skill

    4★ repo

    Writes unit tests and UI tests for Swift, SwiftUI, and UIKit projects following enterprise or indie testing standards. Use when user says "write tests", "add unit tests", "test this code", "create test cases", "add XCTest", "write Swift Testing tests", "help me test this", or "add tests for". Applies enterprise or indie standard from references/ based on project CLAUDE.md config.

  • Go testing with testify

    n-n-code/n-n-code-skills/.agents/skills/go-testing-with-testify Skill

    4★ repo

    Use when writing, reviewing, or hardening Go tests that rely on stretchr/testify — `assert`, `require`, `mock`, and `suite` — including table-driven tests, subtests, parallel tests, mocks versus hand-written fakes, error-wrap assertions, and flaky test triage with `-race` and `-count`.

  • Playwright testing

    n-n-code/n-n-code-skills/.agents/skills/playwright-testing Skill

    4★ repo

    Use when generating, debugging, reviewing, or hardening Playwright E2E specs in an existing working harness across Node, Python, .NET, or Java — including flake triage, locator refinement with UI Mode or `codegen`, `playwright-cli` exploration, visual or responsive coverage, page-object, fixture, auth-reuse usage, or mock-boundary decisions. Not for first-time install, config repair, browser installation, or reusable-auth plumbing — route those to `setup-playwright`.

  • Project config and tests

    n-n-code/n-n-code-skills/.agents/skills/project-config-and-tests Skill

    4★ repo

    Overlay for config contracts, defaults, path helpers, and deterministic test coverage. Use alongside the repo's principle skill when the main task is config behavior or test coverage.

  • Recursive thinking

    n-n-code/n-n-code-skills/.agents/skills/recursive-thinking Skill

    4★ repo

    Recursive self-questioning heuristic for stress-testing a plan, diagnosis, design, review, or recommendation before acting. Use when the user asks to use recursive thinking, go deeper, interrogate assumptions, pressure-test an approach, ask why/how questions, or find what would change the conclusion. Avoid for simple factual lookups or low-ambiguity tasks.

  • Setup playwright

    n-n-code/n-n-code-skills/.agents/skills/setup-playwright Skill

    4★ repo

    Use when adding, extending, or repairing a repo-owned Playwright E2E harness across Node `@playwright/test`, Playwright Pytest, or .NET/Java test frameworks — including browser installation, harness config, auth reuse plumbing, package placement, or CI smoke/sharding setup. Not for ordinary spec debugging once the harness already works; route that to `playwright-testing`.

  • Tester mindset

    n-n-code/n-n-code-skills/.agents/skills/tester-mindset Skill

    4★ repo

    Testing mindset skill for context-driven test strategy, exploratory testing, validation design, acceptance criteria, oracles, weak-test detection, edge cases, heuristics, checklists, and evidence review for code, products, plans, or claims. Use when the user asks what to test, how to test, whether evidence is enough, or to bring a tester mindset. Do not use for merely running an existing test command.

  • Testing

    sefaertunc/Worclaude/.claude/skills/testing Skill

    4★ repo

    Test philosophy, coverage strategy, test-first patterns, what to test and what not to

  • Doa e2etest

    medalsoftchina/workcopilot/embedded-skills/doa-e2etest Skill

    4★ repo

    端到端测试全流程:安装配置 Playwright → 编写 E2E 测试用例 → 执行测试 → 生成精美 HTML 报告 → 输出 PDF。USE FOR: E2E测试、端到端测试、Playwright测试、前端自动化测试、编写E2E用例、生成测试报告、测试报告PDF、测试报告HTML、Playwright配置、自动化回归测试、UI测试、冒烟测试。DO NOT USE FOR: 单元测试(使用 test-driven-development skill)、API测试、性能测试。

  • Doa testreport

    medalsoftchina/workcopilot/embedded-skills/doa-testreport Skill

    4★ repo

    端到端测试全流程:安装配置 Playwright → 编写 E2E 测试用例 → 执行测试 → 生成精美 HTML 报告 → 输出 PDF。USE FOR: E2E测试、端到端测试、Playwright测试、前端自动化测试、编写E2E用例、生成测试报告、测试报告PDF、测试报告HTML、Playwright配置、自动化回归测试、UI测试、冒烟测试。DO NOT USE FOR: 单元测试(使用 test-driven-development skill)、API测试、性能测试。

  • Local lint test

    mpagot/os-autoinst-distri-opensuse-skills/skills/local-lint-test Skill

    no license4★ repo

    Recommends the fastest local commands to validate edited OSADO code before pushing. Activate when the user asks "how do I check my code", "what should I run locally", "lint my changes", "does this compile", "run perltidy", "run perlcritic", "run a unit test", "check formatting", or after editing files to verify correctness. Covers compilation, formatting, linting, unit tests, YAML validation, and static analysis -- always preferring the lightest targeted command over full-suite runs.

  • Test catalog

    mpagot/os-autoinst-distri-opensuse-skills/skills/test-catalog Skill

    no license4★ repo

    Add or audit a Perldoc documentation header on an OSADO test module following the test catalog standard. Use when a user asks to "add header", "document", or "add catalog header" to a Perl test module.

  • Unit test wizard

    mpagot/os-autoinst-distri-opensuse-skills/skills/unit-test-wizard Skill

    no license4★ repo

    Writes and reviews OSADO Perl unit tests for library modules in lib/. Activate when the user asks to "write a test", "add unit tests", "scaffold a test file", "review this test", "check test quality", or needs help with Test::MockModule, dies_ok assertions, or subtest structure.

  • Vr planner

    mpagot/os-autoinst-distri-opensuse-skills/skills/vr-planner Skill

    no license4★ repo

    Plans how to verify changes to an os-autoinst-distri-opensuse (OSADO) checkout. Use this skill when the user asks "how do I test my change", "what verification run (VR) should I do", "which openQA job should I clone", or "what's affected by my edit". Determines required unit tests, affected test modules, YAML schedules, and openqa-clone-job commands.

  • Test driven development

    KhaledSaeed18/dotclaude/.claude-plugin/plugins/engineering/skills/test-driven-development Skill

    4★ repo

    Implement a feature or bugfix test-first using the red-green-refactor cycle — write a failing test, watch it fail, write the minimal code to pass, then clean up. Works in any language or test runner. Use when building new behaviour or fixing a bug and you want the test to actually prove the code works.

  • Grill me

    KhaledSaeed18/dotclaude/.claude-plugin/plugins/productivity/skills/grill-me Skill

    4★ repo

    Relentlessly stress-test a plan, design, architecture, idea, or strategy until all critical decisions are resolved. Use when a plan, design, or decision needs adversarial stress-testing before committing to it.

  • Webapp testing

    KhaledSaeed18/dotclaude/.claude-plugin/plugins/testing/skills/webapp-testing Skill

    4★ repo

    Verify a web application works correctly in a real browser using Playwright. Covers page navigation, form submission, user interactions, console error detection, screenshot capture, and responsive layout checking. Use when you need to confirm a UI feature actually works end-to-end, catch regressions after a change, verify a form flow completes, or check that the page is free of console errors. Requires Node.js; installs Playwright if not already present.

  • Test driven development

    KhaledSaeed18/dotclaude/skills/engineering/test-driven-development Skill

    4★ repo

    Implement a feature or bugfix test-first using the red-green-refactor cycle — write a failing test, watch it fail, write the minimal code to pass, then clean up. Works in any language or test runner. Use when building new behaviour or fixing a bug and you want the test to actually prove the code works.

  • Grill me

    KhaledSaeed18/dotclaude/skills/productivity/grill-me Skill

    4★ repo

    Relentlessly stress-test a plan, design, architecture, idea, or strategy until all critical decisions are resolved. Use when a plan, design, or decision needs adversarial stress-testing before committing to it.

  • Webapp testing

    KhaledSaeed18/dotclaude/skills/testing/webapp-testing Skill

    4★ repo

    Verify a web application works correctly in a real browser using Playwright. Covers page navigation, form submission, user interactions, console error detection, screenshot capture, and responsive layout checking. Use when you need to confirm a UI feature actually works end-to-end, catch regressions after a change, verify a form flow completes, or check that the page is free of console errors. Requires Node.js; installs Playwright if not already present.

  • Bank the suite

    mikestangdevs/craft-skills/skills/rigor/bank-the-suite Skill

    4★ repo

    Use after completing any unit of work in a repo that has a real test suite — before starting the next task, compacting context, or declaring done. Runs the FULL suite (not just the tests near the change), in the background and parallelized when it's slow, and 'banks' a green state: honest pass/fail counts, pre-existing failures explicitly carved out by name, no moving on while red is unexplained. Use when the agent only ran the two tests it just wrote, when a long suite keeps getting skipped 'for speed', when failures are described vaguely ('a few unrelated tests fail'), or when work is about to stack on top of an unverified base.

  • Test like you mean it

    mikestangdevs/craft-skills/skills/rigor/test-like-you-mean-it Skill

    4★ repo

    Use after building any feature, model, or fix that the team has to trust — before calling it done. Replaces smoke tests and tests-written-to-pass with an adversarial test wave: tests designed to BREAK the thing (invariants, conservation laws, edge regimes, reference cross-checks, hostile inputs), where findings are expected and get fixed, not explained away. Use when the agent (or you) just wrote tests alongside the code it's testing, when a suite passes suspiciously fast, when coverage exists but confidence doesn't, or when someone says 'tests pass' and you still wouldn't bet on it in production.

  • Test driven development

    izyanrajwani/agent-skills-library/skills/test-driven-development Skill

    no license4★ repo

    Red-green-refactor development methodology requiring verified test coverage. Use for feature implementation, bugfixes, refactoring, or any behavior changes where tests must prove correctness.

    The same file is in 8 other repositories

  • Testing

    Lion-1209/Lion-Skills/skills/testing Skill

    4★ repo

    需为代码写测试或改进脆弱测试时。

  • Test

    Epistates/sparX/.claude/skills/test Skill

    4★ repo

    Verify sparX setup is working correctly. Use when the user wants to check their installation, test skills, or troubleshoot setup issues.

  • Test

    Imran-ml/claude-skills/.claude/skills/test Skill

    no license4★ repo

    Use this skill to run tests, identify failures, and fix them. Triggered by "run tests", "fix failing tests", "make tests pass", or "/test".

  • Testrail

    nmoinvaz/speedy-gonzales/skills/testrail Skill

    no license4★ repo

    Interact with the TestRail Test Management API. Use when fetching test plans, test runs, test cases, submitting test results, or attaching screenshots and logs to test evidence. Supports the full execution lifecycle from locating tests to recording step-by-step outcomes.

  • Supreme benchmarking

    davccavalcante/supreme-coding-guidelines-skill.ah/skills/supreme-benchmarking Skill

    no license4★ repo

    Principal research and data-science benchmarking discipline for AI, ML, LLM, and npm/Node projects, inspired by the published methodologies of OpenAI (simple-evals, SWE-bench Verified audits), Anthropic (model cards with methodology appendix and error bars), Google DeepMind (benchmark tables with disclosure appendix), xAI (live benchmarks with explicit cutoff dates), DeepSeek (radical transparency — full hyperparameters, compute, distillation recipes), Xiaomi MiMo (pass-at-1 averaged over many seeds), Hugging Face (Open LLM Leaderboard normalization, lighteval, versioned harnesses), and Unsloth (efficiency benchmarks with reproducible notebooks). Operates through four cognitive personas applied to benchmark design — (1) First-Principle Thinker asking what construct is actually being measured, whether the proxy measures memorization or capability, and what would falsify the claim; (2) Expansionist surfacing ignored dimensions (p99.9 latency, cold start, cost per task, energy, robustness to paraphrase, multi-turn degradation, variance across seeds); (3) Outsider removing bias via preregistration of methodology before results, blind evaluation where possible, baseline re-run integrity (never copy competitor numbers from papers — re-run all baselines in the same config), and the test of whether a competitor or regulator would accept the methodology; (4) Executor running the controlled protocol peer-to-peer without trying to please — pinned versions, fixed seeds, minimum five runs, warmup discarded, isolated environment, raw data published, and uncomfortable results published unchanged. Enforces statistical rigor gates (95 percent confidence intervals, median plus IQR, effect size, significance tests, multiple-comparison correction), contamination and saturation defense (canary strings, n-gram overlap checks, held-out private sets, benchmark refresh cadence), LLM-specific protocol (pass-at-k disclosure, temperature disclosure, prompt-sensitivity spread across three to five paraphrases, eval-harness version pinning — lm-eval-harness, HELM, lighteval, inspect-ai, promptfoo), npm/Node-specific protocol (tinybench or mitata for micro, hyperfine for CLI, size-limit for bundle, JIT warmup and GC isolation), reporting in the Anthropic, Hugging Face, and Unsloth style (tables with best result bolded, bar charts with error bars, radar charts for multi-dimension, efficiency-frontier scatter of score versus cost, methodology appendix, benchmark card analogous to a model card, raw JSONL published), one-command reproducibility package, honest disclosure (negative results published, best-of-N disclosed, limitations section, conflicts of interest declared), and continuous regression tracking in CI with threshold alerting. Requires ah-parser. Output mode follows user preference at parser activation; user code, eval outputs, raw data, configs, and benchmark artifacts are always preserved verbatim. Honest measurement over impressive numbers — non-negotiable.

  • Stress test

    erhwenkuo/stock_skills/.claude/skills/stress-test Skill

    no license4★ repo

    Portfolio stress test. Receives a list of holdings and identifies portfolio weaknesses through shock sensitivity, scenario analysis, and causal chain analysis.

  • Market validation

    Dragoon0x/product-skills/skills/strategy/market-validation Skill

    no license4★ repo

    Test assumptions before committing resources. Generates lean validation plans, fake door tests, and interview scripts. Use before building anything expensive or when there's no evidence anyone wants what's being built.