agentsclimarketplace

Test

10,607 rows, by stacks then stars

1,559 of these skill files have been read, by 1,201 distinct authors, and what they tell an agent counted. What Test authors agree on, and what they forbid

  • Tabletest

    nchaugen/tabletest-claude-plugin/skills/tabletest Skill

    0★ repo

    Claude Code plugin to help write TableTest-style JUnit tests in Java and Kotlin

  • Basic

    rdzehtsiar/agent-skill-auditor/fixtures/spec/basic Skill

    0★ repo

    Minimal valid skill fixture for scanner smoke tests.

  • E2e representative

    rdzehtsiar/agent-skill-auditor/fixtures/supply-chain/e2e-representative Skill

    0★ repo

    Reviews a local release note draft with pinned helper evidence.

  • Manual tester

    wamalalawrence/agent-skills/skills/manual-tester Skill

    no license0★ repo

    Manual testing workflow for validating intended behavior, exploring workflows, finding defects, documenting actual vs expected behavior, collecting evidence, and preparing retest guidance. Use when: planning or executing manual tests, validating acceptance criteria, doing exploratory testing, checking edge cases, reporting defects, or identifying regression and automation candidates. Collaborates with product-owner for intended behavior, software-engineer for technical risk areas, and test-automation-engineer for high-value automation candidates.

  • Product owner

    wamalalawrence/agent-skills/skills/product-owner Skill

    no license0★ repo

    Product ownership workflow for turning product goals, stakeholder needs, tracker tickets (Jira, GitHub Issues, GitLab Issues, Azure DevOps, and others), and rough ideas into clear, testable, implementation-ready work. Use when: clarifying goals, refining requirements, defining scope, writing acceptance criteria, preparing tracker-ready stories or tasks, or handing work to engineering and testing. Collaborates with software-engineer for feasibility and tradeoffs, manual-tester for scenario coverage, and test-automation-engineer for automation-friendly acceptance criteria.

  • Test automation engineer

    wamalalawrence/agent-skills/skills/test-automation-engineer Skill

    no license0★ repo

    Test automation engineering workflow for choosing the right test level, designing maintainable automated checks, preventing flakiness, integrating tests into CI, and deciding when not to automate. Use when: creating or reviewing automated regression tests, API tests, contract tests, integration tests, UI/e2e tests, fixtures, selectors, or test reporting. Collaborates with software-engineer for code quality and architecture, manual-tester for real scenarios and defects, and product-owner for acceptance criteria and business-critical workflows.

  • Ab test setup

    vikynofebriputra-creator/Orkas-Awesome-AgentSkills/product/skills/marketing-skills/references/ab-test-setup Skill

    0★ 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," or "hypothesis." For tracking implementation, see analytics-tracking.

    The same file is in 5 other repositories

  • Product test

    vikynofebriputra-creator/Orkas-Awesome-AgentSkills/product/skills/product-test Skill

    0★ repo

    Use to turn a PRD section, user story, feature slice, or behavior description into product test scenarios and pass/fail conditions. Use when the user asks for product testing, acceptance criteria, Given/When/Then scenarios, QA-ready scenarios, pass/fail checks, edge cases, error states, non-functional acceptance checks, or story-level verification.

    The same file is in 1 other repository

  • Container skill

    ToxicityRadius/skill-stocktake/tests/fixtures/home/.codex/skills/container-skill Skill

    0★ repo

    Use when testing nested fixture exclusion.

  • Swift protocol di testing

    asong56/skills/03-build/mobile/swift-protocol-di-testing Skill

    0★ repo

    Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.

  • Test driven development

    asong56/skills/03-build/universal/test-driven-development Skill

    0★ repo

    TDD methodology, philosophy, anti-patterns, and vertical-slice testing. Use when writing tests, planning test strategy, or reviewing test quality.

  • Universal testing

    asong56/skills/03-build/universal/universal-testing Skill

    0★ repo

    Language-agnostic TDD meta-skill. Inject runtime parameters (runtime, test_runner, mock_library, coverage_tool, coverage_gate) to activate language-specific idioms while keeping the core RED → GREEN → REFACTOR philosophy, assertion patterns, and testing tiers constant. Incorporates former: python-testing, kotlin-testing, rust-testing, cpp-testing, golang-testing, react-testing, csharp-testing, fsharp-testing, perl-testing.

  • Ai regression testing

    asong56/skills/04-assure/ai-regression-testing Skill

    0★ repo

    Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code.

  • Automated testing

    asong56/skills/04-assure/automated-testing Skill

    0★ repo

    Automated test suite: Playwright-based web app testing (functional, visual regression, accessibility) + Lightpanda web vitals benchmarking (load time, DOM-ready, Core Web Vitals) + /qa Test→Fix→Verify loop with auto-bootstrapping for any project stack. Use for QA and performance regression.

  • Browser testing with devtools

    asong56/skills/04-assure/browser-testing-with-devtools Skill

    0★ repo

    Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with

  • Code health

    asong56/skills/04-assure/code-health Skill

    0★ repo

    Code quality dashboard: runs all available tools (type check, lint, tests, coverage, dead-code, bundle size), scores each category, presents a composite dashboard, and tracks trends in memory/metrics.db. HARD GATE: never fixes issues.

  • Windows desktop e2e

    asong56/skills/04-assure/windows-desktop-e2e Skill

    0★ repo

    E2E testing for Windows native desktop apps (WPF, WinForms, Win32/MFC, Qt) using pywinauto and Windows UI Automation.

  • Python test architecture

    genaptic/skillsets/dist/dev/claude/plugins/python-best-practices/skills/python-test-architecture Skill

    0★ repo

    Use when, and only when, the user explicitly requests repository-wide Python test strategy, multi-level test architecture, suite-wide fixture ownership, global determinism, coverage policy, flake elimination, CI selection, or runtime budgets. Do not use this skill unless the requested result is repository-wide or multi-layer; one focused behavior contract or tests added while implementing another feature do not qualify.

  • Python cli testing

    genaptic/skillsets/dist/dev/claude/plugins/python-cli-apps/skills/python-cli-testing Skill

    0★ repo

    Design Python CLI tests for invocation, entry points, parsing/help, status, streams, isolation, and platform CI. Use when writing focused subprocess assertions for one command's exit status and stderr. A comprehensive CLI-only matrix uses this skill alone. Add python-test-architecture only when explicitly combining it with repository-wide test architecture or CI policy. Do not use for broad strategy without a CLI deliverable, choosing the failure contract, or running an existing smoke command.

  • Rust core best practices

    genaptic/skillsets/dist/dev/claude/plugins/rust-best-practices/skills/rust-core-best-practices Skill

    0★ repo

    Review and implement general Rust changes against the target repository's toolchain, MSRV, Cargo policy, ownership model, error conventions, linting, documentation, tests, and safety boundaries. Use when a Rust task needs a broad repository-aware quality pass without one narrower concern dominating. Do not use when crate layout, type structure, abstractions, async behavior, networking, testing, dependencies, portability, workspace prose, or rustdoc is the primary outcome; prefer the corresponding specialized Rust skill.

  • Rust testing strategy

    genaptic/skillsets/dist/dev/claude/plugins/rust-best-practices/skills/rust-testing-strategy Skill

    0★ repo

    Plan and review reliable Rust unit, integration, doctest, binary-smoke, live-dependency, and end-to-end tests, including placement, fixtures, determinism, authorization, and evidence. Use when choosing the smallest test boundary or designing coverage across crates and processes. Do not use when public API documentation and doctest prose are the primary deliverable; use rustdoc-maintenance instead.

  • Python test architecture

    genaptic/skillsets/dist/dev/codex/plugins/python-best-practices/skills/python-test-architecture Skill

    0★ repo

    Use when, and only when, the user explicitly requests repository-wide Python test strategy, multi-level test architecture, suite-wide fixture ownership, global determinism, coverage policy, flake elimination, CI selection, or runtime budgets. Do not use this skill unless the requested result is repository-wide or multi-layer; one focused behavior contract or tests added while implementing another feature do not qualify.

  • Python cli testing

    genaptic/skillsets/dist/dev/codex/plugins/python-cli-apps/skills/python-cli-testing Skill

    0★ repo

    Design Python CLI tests for invocation, entry points, parsing/help, status, streams, isolation, and platform CI. Use when writing focused subprocess assertions for one command's exit status and stderr. A comprehensive CLI-only matrix uses this skill alone. Add python-test-architecture only when explicitly combining it with repository-wide test architecture or CI policy. Do not use for broad strategy without a CLI deliverable, choosing the failure contract, or running an existing smoke command.

  • Rust core best practices

    genaptic/skillsets/dist/dev/codex/plugins/rust-best-practices/skills/rust-core-best-practices Skill

    0★ repo

    Review and implement general Rust changes against the target repository's toolchain, MSRV, Cargo policy, ownership model, error conventions, linting, documentation, tests, and safety boundaries. Use when a Rust task needs a broad repository-aware quality pass without one narrower concern dominating. Do not use when crate layout, type structure, abstractions, async behavior, networking, testing, dependencies, portability, workspace prose, or rustdoc is the primary outcome; prefer the corresponding specialized Rust skill.

  • Rust testing strategy

    genaptic/skillsets/dist/dev/codex/plugins/rust-best-practices/skills/rust-testing-strategy Skill

    0★ repo

    Plan and review reliable Rust unit, integration, doctest, binary-smoke, live-dependency, and end-to-end tests, including placement, fixtures, determinism, authorization, and evidence. Use when choosing the smallest test boundary or designing coverage across crates and processes. Do not use when public API documentation and doctest prose are the primary deliverable; use rustdoc-maintenance instead.

  • Python test architecture

    genaptic/skillsets/dist/dev/opencode/python/best-practices/python-test-architecture Skill

    0★ repo

    Use when, and only when, the user explicitly requests repository-wide Python test strategy, multi-level test architecture, suite-wide fixture ownership, global determinism, coverage policy, flake elimination, CI selection, or runtime budgets. Do not use this skill unless the requested result is repository-wide or multi-layer; one focused behavior contract or tests added while implementing another feature do not qualify.

  • Python cli testing

    genaptic/skillsets/dist/dev/opencode/python/cli-apps/python-cli-testing Skill

    0★ repo

    Design Python CLI tests for invocation, entry points, parsing/help, status, streams, isolation, and platform CI. Use when writing focused subprocess assertions for one command's exit status and stderr. A comprehensive CLI-only matrix uses this skill alone. Add python-test-architecture only when explicitly combining it with repository-wide test architecture or CI policy. Do not use for broad strategy without a CLI deliverable, choosing the failure contract, or running an existing smoke command.

  • Rust core best practices

    genaptic/skillsets/dist/dev/opencode/rust/best-practices/rust-core-best-practices Skill

    0★ repo

    Review and implement general Rust changes against the target repository's toolchain, MSRV, Cargo policy, ownership model, error conventions, linting, documentation, tests, and safety boundaries. Use when a Rust task needs a broad repository-aware quality pass without one narrower concern dominating. Do not use when crate layout, type structure, abstractions, async behavior, networking, testing, dependencies, portability, workspace prose, or rustdoc is the primary outcome; prefer the corresponding specialized Rust skill.

  • Rust testing strategy

    genaptic/skillsets/dist/dev/opencode/rust/best-practices/rust-testing-strategy Skill

    0★ repo

    Plan and review reliable Rust unit, integration, doctest, binary-smoke, live-dependency, and end-to-end tests, including placement, fixtures, determinism, authorization, and evidence. Use when choosing the smallest test boundary or designing coverage across crates and processes. Do not use when public API documentation and doctest prose are the primary deliverable; use rustdoc-maintenance instead.

  • Python test architecture

    genaptic/skillsets/dist/preview/claude/plugins/python-best-practices/skills/python-test-architecture Skill

    0★ repo

    Use when, and only when, the user explicitly requests repository-wide Python test strategy, multi-level test architecture, suite-wide fixture ownership, global determinism, coverage policy, flake elimination, CI selection, or runtime budgets. Do not use this skill unless the requested result is repository-wide or multi-layer; one focused behavior contract or tests added while implementing another feature do not qualify.

  • Python cli testing

    genaptic/skillsets/dist/preview/claude/plugins/python-cli-apps/skills/python-cli-testing Skill

    0★ repo

    Design Python CLI tests for invocation, entry points, parsing/help, status, streams, isolation, and platform CI. Use when writing focused subprocess assertions for one command's exit status and stderr. A comprehensive CLI-only matrix uses this skill alone. Add python-test-architecture only when explicitly combining it with repository-wide test architecture or CI policy. Do not use for broad strategy without a CLI deliverable, choosing the failure contract, or running an existing smoke command.

  • Rust core best practices

    genaptic/skillsets/dist/preview/claude/plugins/rust-best-practices/skills/rust-core-best-practices Skill

    0★ repo

    Review and implement general Rust changes against the target repository's toolchain, MSRV, Cargo policy, ownership model, error conventions, linting, documentation, tests, and safety boundaries. Use when a Rust task needs a broad repository-aware quality pass without one narrower concern dominating. Do not use when crate layout, type structure, abstractions, async behavior, networking, testing, dependencies, portability, workspace prose, or rustdoc is the primary outcome; prefer the corresponding specialized Rust skill.

  • Rust testing strategy

    genaptic/skillsets/dist/preview/claude/plugins/rust-best-practices/skills/rust-testing-strategy Skill

    0★ repo

    Plan and review reliable Rust unit, integration, doctest, binary-smoke, live-dependency, and end-to-end tests, including placement, fixtures, determinism, authorization, and evidence. Use when choosing the smallest test boundary or designing coverage across crates and processes. Do not use when public API documentation and doctest prose are the primary deliverable; use rustdoc-maintenance instead.

  • Python test architecture

    genaptic/skillsets/dist/preview/codex/plugins/python-best-practices/skills/python-test-architecture Skill

    0★ repo

    Use when, and only when, the user explicitly requests repository-wide Python test strategy, multi-level test architecture, suite-wide fixture ownership, global determinism, coverage policy, flake elimination, CI selection, or runtime budgets. Do not use this skill unless the requested result is repository-wide or multi-layer; one focused behavior contract or tests added while implementing another feature do not qualify.

  • Python cli testing

    genaptic/skillsets/dist/preview/codex/plugins/python-cli-apps/skills/python-cli-testing Skill

    0★ repo

    Design Python CLI tests for invocation, entry points, parsing/help, status, streams, isolation, and platform CI. Use when writing focused subprocess assertions for one command's exit status and stderr. A comprehensive CLI-only matrix uses this skill alone. Add python-test-architecture only when explicitly combining it with repository-wide test architecture or CI policy. Do not use for broad strategy without a CLI deliverable, choosing the failure contract, or running an existing smoke command.

  • Rust core best practices

    genaptic/skillsets/dist/preview/codex/plugins/rust-best-practices/skills/rust-core-best-practices Skill

    0★ repo

    Review and implement general Rust changes against the target repository's toolchain, MSRV, Cargo policy, ownership model, error conventions, linting, documentation, tests, and safety boundaries. Use when a Rust task needs a broad repository-aware quality pass without one narrower concern dominating. Do not use when crate layout, type structure, abstractions, async behavior, networking, testing, dependencies, portability, workspace prose, or rustdoc is the primary outcome; prefer the corresponding specialized Rust skill.

  • Rust testing strategy

    genaptic/skillsets/dist/preview/codex/plugins/rust-best-practices/skills/rust-testing-strategy Skill

    0★ repo

    Plan and review reliable Rust unit, integration, doctest, binary-smoke, live-dependency, and end-to-end tests, including placement, fixtures, determinism, authorization, and evidence. Use when choosing the smallest test boundary or designing coverage across crates and processes. Do not use when public API documentation and doctest prose are the primary deliverable; use rustdoc-maintenance instead.

  • Python test architecture

    genaptic/skillsets/dist/preview/opencode/python/best-practices/python-test-architecture Skill

    0★ repo

    Use when, and only when, the user explicitly requests repository-wide Python test strategy, multi-level test architecture, suite-wide fixture ownership, global determinism, coverage policy, flake elimination, CI selection, or runtime budgets. Do not use this skill unless the requested result is repository-wide or multi-layer; one focused behavior contract or tests added while implementing another feature do not qualify.

  • Python cli testing

    genaptic/skillsets/dist/preview/opencode/python/cli-apps/python-cli-testing Skill

    0★ repo

    Design Python CLI tests for invocation, entry points, parsing/help, status, streams, isolation, and platform CI. Use when writing focused subprocess assertions for one command's exit status and stderr. A comprehensive CLI-only matrix uses this skill alone. Add python-test-architecture only when explicitly combining it with repository-wide test architecture or CI policy. Do not use for broad strategy without a CLI deliverable, choosing the failure contract, or running an existing smoke command.

  • Rust core best practices

    genaptic/skillsets/dist/preview/opencode/rust/best-practices/rust-core-best-practices Skill

    0★ repo

    Review and implement general Rust changes against the target repository's toolchain, MSRV, Cargo policy, ownership model, error conventions, linting, documentation, tests, and safety boundaries. Use when a Rust task needs a broad repository-aware quality pass without one narrower concern dominating. Do not use when crate layout, type structure, abstractions, async behavior, networking, testing, dependencies, portability, workspace prose, or rustdoc is the primary outcome; prefer the corresponding specialized Rust skill.

  • Rust testing strategy

    genaptic/skillsets/dist/preview/opencode/rust/best-practices/rust-testing-strategy Skill

    0★ repo

    Plan and review reliable Rust unit, integration, doctest, binary-smoke, live-dependency, and end-to-end tests, including placement, fixtures, determinism, authorization, and evidence. Use when choosing the smallest test boundary or designing coverage across crates and processes. Do not use when public API documentation and doctest prose are the primary deliverable; use rustdoc-maintenance instead.

  • Python test architecture

    genaptic/skillsets/packs/python/best-practices/skills/python-test-architecture Skill

    0★ repo

    Use when, and only when, the user explicitly requests repository-wide Python test strategy, multi-level test architecture, suite-wide fixture ownership, global determinism, coverage policy, flake elimination, CI selection, or runtime budgets. Do not use this skill unless the requested result is repository-wide or multi-layer; one focused behavior contract or tests added while implementing another feature do not qualify.

  • Python cli testing

    genaptic/skillsets/packs/python/cli-apps/skills/python-cli-testing Skill

    0★ repo

    Design Python CLI tests for invocation, entry points, parsing/help, status, streams, isolation, and platform CI. Use when writing focused subprocess assertions for one command's exit status and stderr. A comprehensive CLI-only matrix uses this skill alone. Add python-test-architecture only when explicitly combining it with repository-wide test architecture or CI policy. Do not use for broad strategy without a CLI deliverable, choosing the failure contract, or running an existing smoke command.

  • Rust core best practices

    genaptic/skillsets/packs/rust/best-practices/skills/rust-core-best-practices Skill

    0★ repo

    Review and implement general Rust changes against the target repository's toolchain, MSRV, Cargo policy, ownership model, error conventions, linting, documentation, tests, and safety boundaries. Use when a Rust task needs a broad repository-aware quality pass without one narrower concern dominating. Do not use when crate layout, type structure, abstractions, async behavior, networking, testing, dependencies, portability, workspace prose, or rustdoc is the primary outcome; prefer the corresponding specialized Rust skill.

  • Rust testing strategy

    genaptic/skillsets/packs/rust/best-practices/skills/rust-testing-strategy Skill

    0★ repo

    Plan and review reliable Rust unit, integration, doctest, binary-smoke, live-dependency, and end-to-end tests, including placement, fixtures, determinism, authorization, and evidence. Use when choosing the smallest test boundary or designing coverage across crates and processes. Do not use when public API documentation and doctest prose are the primary deliverable; use rustdoc-maintenance instead.

  • Regex test mcp

    MukundaKatta/mcp-stack/io.github.MukundaKatta/regex-test-mcp MCP server

    0★ repo

    Trustworthy JS regex testing. Real offsets, named groups, safe against zero-width loops.

  • Skill coverage monitor

    dailyaiagents-cpu/dailyai-os/io.github.dailyaiagents-cpu/skill-coverage-monitor MCP server

    0★ repo

    Walks every skill directory in skills/ and ~/.openclaw/skills/, validates each has SOUL.md (voice...