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

  • Tdd workflow

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/tdd-workflow Skill

    2★ repo

    Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.

  • Tdd workflows tdd cycle

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/tdd-workflows-tdd-cycle Skill

    2★ repo

    Applies the red-green-refactor test-driven development cycle to implement focused behavior changes with executable tests first.

  • Tdd workflows tdd green

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/tdd-workflows-tdd-green Skill

    2★ repo

    Implement the minimal code needed to make failing tests pass in the TDD green phase.

  • Tdd workflows tdd red

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/tdd-workflows-tdd-red Skill

    2★ repo

    Generate failing tests for the TDD red phase to define expected behavior and edge cases.

  • Tdd workflows tdd refactor

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/tdd-workflows-tdd-refactor Skill

    2★ repo

    Guides safe TDD refactoring by preserving behavior with tests while simplifying structure, naming, and design.

  • Temporal python testing

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/temporal-python-testing Skill

    2★ repo

    Comprehensive testing approaches for Temporal workflows using pytest, progressive disclosure resources for specific testing scenarios.

  • Test automator

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/test-automator Skill

    2★ repo

    Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering. Build scalable testing strategies with advanced CI/CD integration.

  • Test driven development

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/test-driven-development Skill

    2★ repo

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

  • Test fixing

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/test-fixing Skill

    2★ repo

    Systematically identify and fix all failing tests using smart grouping strategies. Use when explicitly asks to fix tests (\"fix these tests\", \"make tests pass\"), reports test failures (\"tests are failing\", \"test suite is broken\"), or completes implementation and wants tests passing.

  • Testing patterns

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/testing-patterns Skill

    2★ repo

    Jest testing patterns, factory functions, mocking strategies, and TDD workflow. Use when writing unit tests, creating test factories, or following TDD red-green-refactor cycle.

  • Testing qa

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/testing-qa Skill

    2★ repo

    Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.

  • Unit testing test generate

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/unit-testing-test-generate Skill

    2★ repo

    Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.

  • Web security testing

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/web-security-testing Skill

    2★ repo

    Web application security testing workflow for OWASP Top 10 vulnerabilities including injection, XSS, authentication flaws, and access control issues.

  • Web3 testing

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/web3-testing Skill

    2★ repo

    Master comprehensive testing strategies for smart contracts using Hardhat, Foundry, and advanced testing patterns.

  • Webapp testing

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/webapp-testing Skill

    2★ repo

    To test local web applications, write native Python Playwright scripts.

  • Wordpress penetration testing

    newmindsgroup/ai-agent-skills-library/sources/sickn33-antigravity-awesome-skills/skills/wordpress-penetration-testing Skill

    2★ repo

    Assess WordPress installations for common vulnerabilities and WordPress 7.0 attack surfaces.

  • Terraform module change

    bmaltais/skills/terraform-module-change Skill

    no license2★ repo

    End-to-end workflow for making a change to an existing Terraform module resource: fetch provider docs, implement the change, write a pure-logic tftest fixture (no provider credentials needed), wire test discovery via Makefile, run the full validation cycle (terraform test → fmt → tflint), and update RELEASE_NOTES.md. Use when the user asks to add, update, or fix an argument on an existing Terraform resource, add a new behaviour to an existing resource block, ensure a resource re-syncs on upstream changes, or "update X to use the new Y argument". Trigger on phrases like "update this resource to use", "add X to my terraform resource", "ensure sync when", "how do I make terraform detect changes in", "update my tf code for provider version X", "write tests for this tf change". DO NOT use for: scaffolding new modules (use terraform-caf-azurerm-module), full provider version upgrades across a module (use eslz-module-upgrade), or pure validation runs without code changes (use terraform-validation-workflow).

  • Creative testing

    celeryhq/simplified-ai/skills/creative-testing Skill

    2★ repo

    Design, produce, and evaluate disciplined social creative tests for marketers. Use when the user asks for A/B tests, hook tests, creative variants, message experiments, format tests, offer or CTA tests, an experimentation roadmap, ways to improve a campaign systematically, or draft variants whose results can produce a reusable marketing learning.

  • Ios testing

    almasumdev/awesome-ios-agent-skills/.github/skills/testing_and_automation/ios-testing Skill

    no license2★ repo

    Expert guidance on iOS unit and snapshot testing with XCTest, the new Swift Testing framework, and swift-snapshot-testing. Use when writing or auditing tests.

  • Ios ui testing

    almasumdev/awesome-ios-agent-skills/.github/skills/testing_and_automation/ios-ui-testing Skill

    no license2★ repo

    Expert guidance on XCUITest — accessibility identifiers, robust element queries, screenshot flows, test plans, and CI stability. Use when writing end-to-end UI tests.

  • E2e engineer

    IrfanSadiqRahat/constellation/agents/e2e-engineer Skill

    no license2★ repo

    Playwright / Cypress, page objects, parallel sharding, flake control.

  • Qa lead

    IrfanSadiqRahat/constellation/agents/qa-lead Skill

    no license2★ repo

    Test pyramid, coverage targets, risk-based test allocation.

  • Tdd discipline

    IrfanSadiqRahat/constellation/methodology/tdd-discipline Skill

    no license2★ repo

    Role-aware TDD. NO production code without a failing test first. Tests live alongside the role's typed artifact.

  • Advise testing qa skills

    the-long-ride/skill-master/skills/advise-testing-qa-skills Skill

    2★ repo

    Use when a human wants to design, evaluate, or improve AI agent skills for testing, QA, regression checks, browser verification, accessibility checks, performance checks, or test automation workflows

  • Cli tool

    Skryx-L-A/project-kit/skills/cli-tool Skill

    2★ repo

    Build and set up a command-line tool project — a clean CLI with subcommands, --help, and proper exit codes, a real test suite, and a pip/npm publish path. This is a project-kit sub-skill loaded by new-project routing. Use WHENEVER the user wants to build, create, or ship a CLI, a command-line tool, a terminal utility, a dev tool, or a binary/script that's run from the shell and (optionally) published to PyPI or npm.

  • Claude e2e skill

    Vironnimo/vbot/tests/e2e/fixtures/mixed-project/.claude/skills/claude-e2e-skill Skill

    2★ repo

    Deterministic Claude Project Skill fixture.

  • Open e2e skill

    Vironnimo/vbot/tests/e2e/fixtures/mixed-project/.opencode/skills/open-e2e-skill Skill

    2★ repo

    Deterministic OpenCode Project Skill fixture.

  • Tests

    tufantunc/review-pro/core/skills/tests Skill

    2★ repo

    Test-quality audit of changed tests/code: weak or missing assertions, missing coverage for new behavior/branches/edge cases, flaky patterns, unrealistic test data, testing implementation details, skipped tests. Use for test review, coverage check, flakiness or assertion-quality audit of a diff.

  • Planned execution

    grimaldost/craft-collection/plugins/humblepowers/skills/planned-execution Skill

    2★ repo

    Turn an agreed design or spec into a complete implementation plan and execute it task by task with fresh subagents and two-stage review — the midweight lane between direct implementation and a governed PR series. Use when a feature needs a multi-step plan with review checkpoints but not series machinery: 'write the implementation plan for this spec', 'execute this plan task by task', 'plan then build this', 'run docs/plans/<file>', or when work has outgrown a single TDD loop but doesn't warrant keel or convoy. The plan contract is firm: bite-sized steps with exact paths, complete code, exact commands with expected output, and no placeholders — a zero-context engineer could execute it cold. The loop is firm too: per task, a fresh implementer subagent, then spec-compliance review, then code-quality review, re-reviewing after each fix. Not for deciding what to build (brainstorming comes first), not for governed multi-PR series with gates and dependency DAGs (keel and convoy own that), and not for small single-loop fixes (test-driven-development directly).

  • Test driven development

    grimaldost/craft-collection/plugins/humblepowers/skills/test-driven-development Skill

    2★ repo

    Red-green-refactor discipline for features and bug fixes: write one minimal failing test, watch it fail for the expected reason, write the least code that passes, refactor only on green. Use when implementing any feature or bugfix, when fixing a bug (the reproducing test comes first and the fix follows), when tempted to backfill tests after the code, or when a new test passes on its first run and therefore proves nothing yet. The bright line: production code is written only against a test you have watched fail; code that preceded its test is deleted and redone test-first, because adapting it quietly converts test-first into test-after. Exceptions — throwaway prototypes, generated code, pure configuration — are agreed with the user, not self-granted. Hands red-green evidence to verification-before-completion. Not for designing suite architecture or coverage strategy, and not for diagnosing an unexplained failure (systematic-debugging owns diagnosis and returns here for the fix).

  • Verification before completion

    grimaldost/craft-collection/plugins/humblepowers/skills/verification-before-completion Skill

    2★ repo

    Evidence before completion claims: identify the command that would prove the claim, run it fresh in this session, read the full output including exit code, and only then state the result — with the evidence. Use when about to report work as done, fixed, passing, or ready; before committing, opening a PR, or moving to the next task; when relaying a subagent's result (verify the diff, not the report); and when adding a regression test (red-green it: revert the fix, watch it fail, restore, watch it pass). Claims match their evidence — 'tests pass' means this session's run with zero failures, not a previous run or an expectation; if verification fails, the deliverable is the actual state with output. Prefer wiring recurring checks into pre-commit or CI over re-remembering them. Not for designing what to verify (a test-strategy concern) — this skill governs the moment of claiming, not the shape of the suite.

  • Verify before done

    logicleap-labs/claude-plugins/plugins/verify-before-done/skills/verify-before-done Skill

    2★ repo

    MANDATORY before declaring ANY code change "done", "fixed", "working", "ready", "shipped", or before ending a turn after editing source. Use whenever you modified code, config, scripts, SQL, infra, or tests and are about to say it works. Forces you to RUN something that exercises the change (test, build, lint, typecheck, smoke script, reproducible command) and record the evidence. Triggers on "done", "fixed", "working", "all tests pass", "build succeeded", "should work now", "ready to merge".

  • Loop review

    VioletScar-Hui/Build_Great_Loop/loop-review Skill

    2★ repo

    Audit and harden an EXISTING agentic-loop prompt or harness against loop-engineering best practices. Use this whenever the user has an agent/loop iterative/autonomous prompt and wants it reviewed, critiqued, scored, or made more reliable — or when they describe loop misbehavior and want to know why: "my agent runs forever / never stops", "it quits too early", "it says it's done but it isn't", "it keeps redoing the same thing", "it forgets progress after a restart", "it edits the tests to pass", "review/improve my iterative agent prompt", "why is my loop flaky". It produces a scored report — critical gaps first, each with a concrete fix — and can rewrite the prompt to close them. Exclude one-shot chatbot/system prompts. If symptoms belong to a completed run or run artifacts, loop-retro diagnoses first. Whole-harness audits are led here even when criteria are the suspected defect. This skill also owns maintenance audits of this six-skill router.

  • Qa

    dustinkeeton/wafflestack/.claude/skills/qa Skill

    2★ repo

    Functional QA of a green PR against the linked issue's intent — read the full diff plus the issue's acceptance criteria, best-effort run the project's tests and exercise the changed behavior, and assess whether the diff carries real test coverage, posting findings as one PR review. Severity stays honest — "no QA concerns" is a valid outcome for a change that does what its issue asked and proves it with tests. Invokable by users and agents.

  • Qa

    dustinkeeton/wafflestack/stacks/code-quality/skills/qa Skill

    2★ repo

    Functional QA of a green PR against the linked issue's intent — read the full diff plus the issue's acceptance criteria, best-effort run the project's tests and exercise the changed behavior, and assess whether the diff carries real test coverage, posting findings as one PR review. Severity stays honest — "no QA concerns" is a valid outcome for a change that does what its issue asked and proves it with tests. Invokable by users and agents.

  • Tdd

    dustinkeeton/wafflestack/stacks/code-quality/skills/tdd Skill

    2★ repo

    Test-Driven Development skill. Guides writing tests before implementation — test-first workflow, co-located test files, and boundary mocking. Enforces Red-Green-Refactor cycle.

  • Obsidian plugin dev

    dustinkeeton/wafflestack/stacks/obsidian-dev/skills/obsidian-plugin-dev Skill

    2★ repo

    Obsidian plugin development patterns, API usage, manifest configuration, settings management, testing, and build pipeline. Use when working on plugin architecture, lifecycle hooks, tests, or Obsidian API integration.

  • Test driven development

    Alex7develop/my-agent-skills/skills/test-driven-development Skill

    2★ repo

    Писать код через цикл red-green-refactor — сначала падающий тест, потом минимальная реализация, потом рефакторинг. Используй при реализации новой логики, исправлении багов, изменении поведения кода. Триггерится на фразы "напиши функцию/фичу", "исправь баг", "добавь логику для X", "покрой тестами". Обязательно применяй при изменении поведения, даже если явно не попросили про тесты.

  • Tdd

    risadams/ink-and-agency/skills/codebase-build/tdd Skill

    no license2★ repo

    Test-driven development — the red → green loop and the rules that make its tests worth keeping. Use when the user wants to build a feature or fix a bug test-first, mentions "red-green-refactor", TDD, or integration tests.

  • Penetration tester

    risadams/ink-and-agency/skills/quality-security/penetration-tester Skill

    no license2★ repo

    Use when you need to conduct authorized security penetration tests to identify real vulnerabilities through active exploitation and validation. Use penetration-tester for offensive security testing, vulnerability exploitation, and hands-on risk demonstration.

  • Test automator

    risadams/ink-and-agency/skills/quality-security/test-automator Skill

    no license2★ repo

    Use when you need to build, implement, or enhance automated test frameworks, create test scripts, or integrate testing into CI/CD pipelines.

  • Ab test analysis

    risadams/ink-and-agency/skills/research-analysis/ab-test-analysis Skill

    no license2★ repo

    Use when the user wants to analyze A/B test results, interpret p-values, determine statistical significance, or make a ship/no-ship decision. Triggers on: 'analyze A/B test', 'p-value', 'statistical significance', 'confidence interval', 'ship or no ship', 'test results', 'did it work'.

  • Mcp testing

    batteryshark/skill-tap/skills/development/mcp/mcp-testing Skill

    2★ repo

    Test FastMCP servers through direct unit tests, in-memory MCP clients, elicitation handlers, and focused deployed-transport integration checks.

  • Assumption mapper

    Abhillashjadhav/PM-agent-OS/.claude/skills/assumption-mapper Skill

    no license2★ repo

    Discovery-stage skill: breaks a product idea into its load-bearing assumptions, ranked riskiest-first, each tagged testable/untestable with a proposed test. Use when the user pitches an idea and asks what it depends on — 'map the assumptions', 'what are we betting on', 'what could kill this', 'what needs to be true', 'riskiest assumption first' — or when /pm routes such a request here. Do NOT use to write the PRD or spec (Build stage), to size the market (opportunity-sizer's job), for knowledge questions about assumption-testing methods, or for analyzing non-product documents.

  • Failure to eval capture

    Abhillashjadhav/PM-agent-OS/.claude/skills/failure-to-eval-capture Skill

    no license2★ repo

    Iterate-stage skill: converts a production failure into a scrubbed, permanent eval case — PII removed with the failure's trigger structure demonstrably preserved, wired into regression testing. Use when a bad output escaped to production — 'capture this failure as an eval case', 'turn this incident into a permanent regression test', 'encode this so it never ships again' — or when /pm routes such a request here. Do NOT use for batch curation of reviewed outputs (golden-dataset-builder), for root-causing why the model failed, for PII scrubbing with no eval encoding, or for regression-testing definitions.

  • Unit economics stress test

    Abhillashjadhav/PM-agent-OS/.claude/skills/unit-economics-stress-test Skill

    no license2★ repo

    Build-stage skill: models a feature's per-user token cost at three scale points — every number derived from stated assumptions, arithmetic fully reproducible. Use when inference cost needs stress-testing before commitment — 'what does this cost per user at 1k/50k/1M users', 'will inference eat our margin at scale', 'run the unit economics on this feature' — or when /pm routes such a request here. If token counts or prices are missing it asks for them or proposes labeled assumptions — it never silently invents them. Do NOT use for portfolio-level roadmap economics (roadmap-reality-check), pricing-structure design (pricing-tradeoff), bare per-MTok price lookups, or general infra cost reduction.

  • Test discipline

    niksavis/basicly/.agents/skills/test-discipline Skill

    2★ repo

    Write isolated order-independent automated tests that assert on observable behavior rather than private internals. Use when writing reviewing or debugging any test (unit integration or end-to-end) in any language especially when tests share fixtures touch global or filesystem state flake depending on run order or reach into implementation details.

  • Pentest toolkit

    nibzard/skills/skills/pentest-toolkit Skill

    2★ repo

    AI-Powered Security Testing Toolkit - Professional penetration testing scripts for discovering vulnerabilities, analyzing application structure, and generating context-aware security tests. All scripts return structured JSON for agent consumption.

    The same file is in 2 other repositories

  • Pentest toolkit

    nibzard/skills/skills/pentest-toolkit/skills/pentest-toolkit Skill

    2★ repo

    AI-Powered Security Testing Toolkit - Professional penetration testing scripts for discovering vulnerabilities, analyzing application structure, and generating context-aware security tests. All scripts return structured JSON for agent consumption.

  • Example skill

    weiox/skm/tests/fixtures/vendor-pack-updated/skills/example-skill Skill

    no license2★ repo

    Use when testing updated vendor fixture content

  • Penetration testing

    kinhluan/skills/.agent-skills/penetration-testing Skill

    2★ repo

    Offensive security, penetration testing, and vulnerability exploitation. Use when conducting security assessments, red team exercises, web application pentesting, network exploitation, or learning ethical hacking techniques. Covers PTES methodology, reconnaissance, exploitation, post-exploitation, and reporting.

  • Component test

    Recusive/Skills/component-test Skill

    2★ repo

    Generate production-grade Vitest tests from HTML elements captured in DevTools. Two-phase workflow (analysis → generation) with edge case discovery.

  • Stress test

    Recusive/Skills/stress-test Skill

    2★ repo

    Create an in-app stress test that runs from browser DevTools console via window.__orbit_debug. Drives the real message pipeline (Tauri events, Zustand stores, Rust backend) with no mocks.

  • Test engineer

    Recusive/Skills/test-engineer Skill

    2★ repo

    Write meaningful tests for TypeScript/React (Vitest) and Rust (cargo test) code.

  • E2e medallion architecture

    kimtth/ms-fabric-skills-dev-starter/.agents/skills/e2e-medallion-architecture Skill

    no license2★ repo

    Implement end-to-end Medallion Architecture (Bronze/Silver/Gold) lakehouse patterns in Microsoft Fabric using PySpark, Delta Lake, and Fabric Pipelines. Use when the user wants to: (1) design a Bronze/Silver/Gold data lakehouse, (2) set up multi-layer workspace with lakehouses for each tier, (3) build ingestion-to-analytics pipelines with data quality enforcement, (4) optimize Spark configurations per medallion layer, (5) orchestrate Bronze-to-Silver-to-Gold flows via notebooks. Triggers: "medallion architecture", "bronze silver gold", "lakehouse layers", "e2e data pipeline", "end-to-end lakehouse", "data lakehouse pattern", "multi-layer lakehouse", "build medallion", "setup medallion".

  • Device testing

    troyjthomas/ios-agent-skills/skills/device-testing Skill

    2★ repo

    Test your app on real devices, catch edge cases, and verify accessibility before shipping. Use this skill after polish is complete and you're preparing for TestFlight or App Store submission. This is the final quality gate before real users touch the app.

  • Testing strategy

    troyjthomas/ios-agent-skills/skills/testing-strategy Skill

    2★ repo

    Comprehensive testing approach for iOS apps built with Claude Code. Covers what Claude Code can test automatically (unit tests, build verification), what requires manual testing (interactive behavior, visual feel), and how to set up CI/CD with GitHub Actions. Use this skill during and after the build phase, and especially before shipping. Becomes critical for post-v1 updates where regressions hide.

  • Ouroboros intent e2e

    secondorderai/ouroboros/.agents/skills/ouroboros-intent-e2e Skill

    2★ repo

    Run Ouroboros desktop intent-based E2E test plans written in Markdown by driving the Electron app through Agent Browser over Chrome DevTools Protocol. Use when asked to execute, debug, or author natural-language desktop QA charters in test-plan/.

  • Ouroboros test plan author

    secondorderai/ouroboros/.agents/skills/ouroboros-test-plan-author Skill

    2★ repo

    Create intent-based Ouroboros desktop E2E Markdown test plans from a high-level goal, feature, module, bug, PRD, ticket, or UI area. Use when asked to generate, draft, author, improve, or expand files under test-plan/ for Agent Browser desktop testing.

  • Agent browser

    secondorderai/ouroboros/packages/desktop/resources/agent-browser/skills/agent-browser Skill

    2★ repo

    Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.