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

  • Qa test

    badrusiddique/enggenie-skill/skills/qa-test Skill

    0★ repo

    Use for QA-perspective testing - Playwright automation or manual browser testing focused on user journeys, not implementation details

  • Review pull request

    jmlrt/skills/review-pull-request Skill

    0★ repo

    Review pull requests as a reviewer. Use when validating a PR before merge: performs independent code review, runs tests, validates manual testing. Handles single PRs with detailed analysis or multiple PRs in parallel batch mode with summary triage table.

  • Migrate to shoehorn

    coderbaba0/ai_agents_skills/migrate-to-shoehorn Skill

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

    coderbaba0/ai_agents_skills/tdd Skill

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

    The same file is in 6 other repositories

  • Test driven development

    bensonmaxai/minis-coding-success-skills/skills/test-driven-development Skill

    no license0★ repo

    Use when implementing a feature, fixing a bug, or refactoring code where correctness matters. Optimizes for higher coding success on Minis on iOS by requiring reproducibility first, identifying the test framework, writing the smallest failing test possible, making the minimum fix, rerunning targeted tests, and only then broadening validation. Useful for Python, JavaScript, web apps, scripts, and small tools.

  • Webapp testing

    bensonmaxai/minis-coding-success-skills/skills/webapp-testing Skill

    no license0★ repo

    Use when testing local web applications, HTML tools, or browser-based UI changes on Minis on iOS. Optimized for higher frontend success rate: start the app safely, confirm the page loads, inspect visible behavior, reproduce UI bugs, test key flows with browser automation, and compare expected vs actual results before declaring the work done.

  • Ci

    jovd83/Cypress-skill/ci Skill

    0★ repo

    CI and delivery skill for Cypress automation. Use when Codex needs to design, debug, or optimize Cypress execution in GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, sharded pipelines, artifact workflows, or shared setup and teardown.

  • Core

    jovd83/Cypress-skill/core Skill

    0★ repo

    Battle-tested Cypress patterns for E2E, API, component, visual, accessibility, and security testing. Covers selectors, assertions, hooks, intercepts, auth flows, debugging, and framework recipes for React, Next.js, Vue, and Angular.

  • Auto sync

    jovd83/Cypress-skill/coverage_plan/auto-sync Skill

    0★ repo

    Coverage-maintenance skill for Cypress planning and documentation. Use when Codex needs to synchronize coverage plans, scenario IDs, traceability links, and summary counts after tests, requirements, or narrative test documents change.

  • Generation

    jovd83/Cypress-skill/coverage_plan/generation Skill

    0★ repo

    Coverage-planning skill for Cypress work. Use when Codex needs to turn confirmed requirements into a structured, risk-aware Cypress coverage plan with scenarios, execution types, priorities, and traceability.

  • Review

    jovd83/Cypress-skill/coverage_plan/review Skill

    0★ repo

    Coverage-plan review skill for Cypress work. Use when Codex needs to present a proposed coverage plan, surface assumptions and tradeoffs, collect user feedback, and secure explicit approval before large implementation or documentation work.

  • Cypress cli

    jovd83/Cypress-skill/cypress-cli Skill

    0★ repo

    Automates browser interactions for web testing, form filling, screenshots, and data extraction using cypress-cli. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, extract information from web pages, mock network requests, manage browser sessions, or generate test code. allowed-tools: Bash(cypress-cli:*)

  • Cypress handover

    jovd83/Cypress-skill/documentation/cypress-handover Skill

    0★ repo

    Use when you need a Cypress task handover that preserves status, session state, blockers, and exact resume steps for a human or later agent.

  • Handover

    jovd83/Cypress-skill/documentation/handover Skill

    0★ repo

    Use when you need the legacy Cypress handover entrypoint path; follow the canonical Cypress handover workflow in documentation/cypress-handover.

  • Root cause

    jovd83/Cypress-skill/documentation/root_cause Skill

    0★ repo

    Failure-analysis skill for Cypress runs. Use when Codex needs to investigate a failing test, distinguish likely product bugs from test issues, and produce a concise developer-focused root-cause report backed by evidence.

  • Session state

    jovd83/Cypress-skill/documentation/session-state Skill

    0★ repo

    Use when you need the legacy Cypress session-state entrypoint path; record session state in the canonical Cypress handover workflow.

  • Bdd

    jovd83/Cypress-skill/documentation/test_cases/bdd Skill

    0★ repo

    Legacy Cypress-specific alias for BDD case formatting. Prefer the standalone `test-artifact-export-skill` skill for Gherkin, BDD, and export-ready case rendering, and use this only when Cypress-local conventions must be preserved explicitly.

  • Plain text

    jovd83/Cypress-skill/documentation/test_cases/plain_text Skill

    0★ repo

    Legacy Cypress-specific alias for plain-text case formatting. Prefer the standalone `test-artifact-export-skill` skill for lightweight narrative case output, and use this only when Cypress-local conventions must be preserved explicitly.

  • Tdd

    jovd83/Cypress-skill/documentation/test_cases/tdd Skill

    0★ repo

    Legacy Cypress-specific alias for TDD-style case documentation. Prefer the standalone `test-artifact-export-skill` skill for formatting approved test cases or building export-ready artifacts, and use this only when Cypress-local conventions must be preserved explicitly.

  • Tests

    jovd83/Cypress-skill/documentation/tests Skill

    0★ repo

    Automation-code documentation skill for Cypress suites. Use when Codex needs to add or improve human-readable comments, docblocks, or file-level explanations around existing Cypress tests without drowning the code in redundant commentary.

  • Intellij junie

    jovd83/Cypress-skill/installers/intellij-junie Skill

    0★ repo

    Editor-setup skill for Cypress plus Junie in IntelliJ IDEA. Use when Codex needs to help configure a practical JetBrains environment for Cypress authoring, execution, debugging, and local skill usage.

  • Vscode codex

    jovd83/Cypress-skill/installers/vscode-codex Skill

    0★ repo

    Editor-setup skill for Cypress plus OpenAI Codex in Visual Studio Code. Use when Codex needs to help configure a practical VS Code environment for Cypress authoring, execution, debugging, and local skill usage.

  • Testlink

    jovd83/Cypress-skill/mappers/testlink Skill

    0★ repo

    Test-management mapping skill for TestLink. Use when Codex needs to apply authoritative TestLink case IDs back into local Cypress docs, titles, or annotations so the repository can trace automation to imported TestLink records.

  • Testrail

    jovd83/Cypress-skill/mappers/testrail Skill

    0★ repo

    Test-management mapping skill for TestRail. Use when Codex needs to apply authoritative TestRail case IDs back into local Cypress docs, titles, or annotations so the repository can trace automation to imported TestRail records.

  • Xray

    jovd83/Cypress-skill/mappers/xray Skill

    0★ repo

    Test-management mapping skill for Xray. Use when Codex needs to apply authoritative Xray issue or case IDs back into local Cypress docs, titles, or annotations so the repository can trace automation to imported Xray records.

  • Zephyr

    jovd83/Cypress-skill/mappers/zephyr Skill

    0★ repo

    Test-management mapping skill for Zephyr Scale. Use when Codex needs to apply authoritative Zephyr case IDs back into local Cypress docs, titles, or annotations so the repository can trace automation to imported Zephyr records.

  • Migration

    jovd83/Cypress-skill/migration Skill

    0★ repo

    Migration skill for moving existing UI automation to Cypress. Use when Codex needs to translate Playwright or Selenium/WebDriver patterns, plan incremental migration, preserve coverage during framework change, or explain architectural differences that affect the suite design.

  • Orchestrator

    jovd83/Cypress-skill/orchestrator Skill

    0★ repo

    Central entrypoint for broad or ambiguous Cypress requests. Use when Codex needs to classify the user's testing goal, choose the right Cypress subskill, and move from intent to implementation, planning, documentation, execution, or reporting without unnecessary menu-driven back-and-forth.

  • Pom

    jovd83/Cypress-skill/pom Skill

    0★ repo

    Test-architecture skill for Cypress page objects, fixtures, helpers, and custom commands. Use when Codex needs to decide whether to introduce a Page Object Model, how to structure page objects, and how to separate browser state, UI behavior, and stateless utilities cleanly.

  • Testlink

    jovd83/Cypress-skill/reporters/testlink Skill

    0★ repo

    Test-management reporting skill for TestLink. Use when Codex needs to publish Cypress execution results into TestLink using the project's mappings, environment configuration, and chosen reporting flow.

  • Testrail

    jovd83/Cypress-skill/reporters/testrail Skill

    0★ repo

    Test-management reporting skill for TestRail. Use when Codex needs to publish Cypress execution results into TestRail using the project's mappings, environment configuration, and chosen reporting flow.

  • Xray

    jovd83/Cypress-skill/reporters/xray Skill

    0★ repo

    Test-management reporting skill for Xray. Use when Codex needs to publish Cypress execution results into Xray using the project's mappings, environment configuration, and chosen reporting flow.

  • Zephyr

    jovd83/Cypress-skill/reporters/zephyr Skill

    0★ repo

    Test-management reporting skill for Zephyr Scale. Use when Codex needs to publish Cypress execution results into Zephyr using the project's mappings, environment configuration, and chosen reporting flow.

  • Stakeholder

    jovd83/Cypress-skill/reporting/stakeholder Skill

    0★ repo

    Stakeholder-reporting skill for Cypress execution results. Use when Codex needs to turn raw Cypress runs into a concise, non-technical summary of tested scope, release health, business impact, and recommended next actions.

  • Testlink

    jovd83/Cypress-skill/transformers/testlink Skill

    0★ repo

    Legacy Cypress-specific alias for TestLink case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into TestLink-ready artifacts, and use this only when Cypress-local conventions must be preserved explicitly.

  • Testrail

    jovd83/Cypress-skill/transformers/testrail Skill

    0★ repo

    Legacy Cypress-specific alias for TestRail case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into TestRail-ready artifacts, and use this only when Cypress-local conventions must be preserved explicitly.

  • Xray

    jovd83/Cypress-skill/transformers/xray Skill

    0★ repo

    Legacy Cypress-specific alias for Xray case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into Xray-ready artifacts, and use this only when Cypress-local conventions must be preserved explicitly.

  • Zephyr

    jovd83/Cypress-skill/transformers/zephyr Skill

    0★ repo

    Legacy Cypress-specific alias for Zephyr case export. Prefer the standalone `test-artifact-export-skill` skill for transforming approved test cases into Zephyr-ready artifacts, and use this only when Cypress-local conventions must be preserved explicitly.

  • Mutmut

    kpatryk/skills/skills/mutmut Skill

    0★ repo

    Comprehensive guide for mutmut, a Python mutation testing tool focused on fast, incremental workflows. Use this skill whenever a user asks about mutation testing, surviving mutants, improving test quality beyond coverage, mutmut configuration in `setup.cfg` or `pyproject.toml`, mutmut TUI usage (`mutmut browse`), applying mutants to disk, or performance tuning (stack depth, pytest args, coverage line filtering). Trigger this skill even when users only mention "mutation score", "killed vs survived mutants", "tests pass but bug slips through", or "how do I make pytest tests stronger".

  • Pytest

    kpatryk/skills/skills/pytest Skill

    0★ repo

    Expert guidance for writing, organizing, debugging, and running Python tests with pytest. Covers fixtures, parametrize, marks, mocking (monkeypatch + pytest-mock), async tests, output capture, conftest.py patterns, and plugins (pytest-cov, pytest-asyncio, pytest-xdist). Use this skill whenever the user is writing Python tests, setting up test infrastructure, debugging failing tests, adding pytest configuration in pyproject.toml, working with conftest.py, or using any pytest plugin. Invoke it even when the user just says "write me a test" or "my test is failing" or "add coverage" — if it involves Python testing, this skill applies.

  • Test scenarios

    weakened-fixedinvestmenttrust229/pm-skills-ko/pm-execution/skills/test-scenarios Skill

    0★ repo

    유저 스토리를 바탕으로 테스트 목표, 사전 조건, 사용자 역할, 단계별 액션, 예상 결과를 포함한 종합적인 테스트 시나리오를 작성합니다. QA 테스트 케이스 작성, 테스트 계획 수립, 인수 테스트 정의, 기능 검증 준비 시 사용하세요.

  • Refactor guru

    guillevc/skills/skills/misc/refactor-guru Skill

    0★ repo

    Use when the user asks to refactor code, clean up messy code, or diagnose code that feels hard to test, follow, or change. Trigger on named or informal smells: god class, long method, feature envy, shotgun surgery, spaghetti code, tight coupling, "this is a mess," "this class does too much," "I keep changing 10 files," or "I can't write tests for this." Also use for structural goals such as making code pluggable, adding many variants or export formats, supporting undo, splitting modules for independent deployment, or improving code that works but is hard to explain, remember, or onboard new developers into.

  • Swift factory di

    guillevc/skills/skills/misc/swift-factory-di Skill

    0★ repo

    MUST USE for questions about the Swift Factory dependency injection library by hmlongco, also called FactoryKit. Covers Factory 2.x APIs, best practices, testing, and migration. Trigger on setting up containers or registrations, scopes (.singleton, .cached, .shared, .graph, .unique), property wrappers (@Injected, @LazyInjected, @WeakLazyInjected, @DynamicInjected, @InjectedObject, @InjectedObservable), flaky tests from container state, circular dependency errors, SwiftUI previews, migration from Factory 1.x to 2.x, ContainerTrait, contexts (.onTest, .onPreview, .onSimulator), imports of FactoryKit/Factory, Container.shared, SharedContainer, @Injected keypaths like \.serviceName, or any Factory-specific API. Do not use for Swinject, swift-dependencies, Dagger, the factory design pattern, or generic DI concepts.

  • Test doubles

    guillevc/skills/skills/misc/test-doubles Skill

    0★ repo

    Identify, classify, design, and create test doubles using Fowler's taxonomy: Dummy, Fake, Stub, Spy, and Mock. Use whenever the user needs help with test doubles, mocking, stubbing, faking, spies, or test isolation in any language. Trigger on creating mocks or stubs for unit tests, choosing a double type, state vs behavior verification, brittle over-mocked tests, "what kind of test double is this?", fakes for integration tests, replacing real dependencies, classical vs mockist TDD, tests coupled to implementation details, or "should I mock this?" Also trigger on mocking frameworks such as Mockito, unittest.mock, Sinon, jest.mock, Moq, gomock, testdouble.js, RSpec mocks, OCMock, Mockery, and NSubstitute.

  • Modernize tests

    guillevc/skills/skills/xcode-skills/modernize-tests Skill

    0★ repo

    Modernize test suites to use modern Swift Testing features or migrate from XCTest.

  • Run all tests and fix

    gologo13/agent-skills/skills/run-all-tests-and-fix Skill

    0★ repo

    Execute the full test suite and systematically fix any failures, ensuring code quality and f...; keywords: test, fix. Use only on explicit request; skip in routine implementation discussions.

  • Write unit tests

    gologo13/agent-skills/skills/write-unit-tests Skill

    0★ repo

    Create comprehensive unit tests for the current code and generate the test file with proper ...; keywords: coverage, unit-test, test, error. Use only on explicit request; skip in routine implementation discussions.

  • Playwright e2e testing

    Perdolique/workflow/skills/playwright-e2e-testing Skill

    0★ repo

    Write and maintain Playwright end-to-end tests for web apps. Use when the user asks for browser or E2E coverage, or for tests covering pages, routes, redirects, navigation, dialogs, authentication, or multi-step user flows, even if they do not explicitly mention Playwright. Also use for API mocking, fixtures, and Playwright-specific assertions.

  • Vitest unit testing

    Perdolique/workflow/skills/vitest-unit-testing Skill

    0★ repo

    Write and maintain Vitest unit tests for TypeScript code. Use when the user needs unit coverage for utilities, services, or stores, or asks for Vitest-based tests with mocks, spies, and assertions.

  • Tdd

    abijith-suresh/skills/skills/tdd Skill

    0★ repo

    Builds features test-first using red-green-refactor. Use only when the user explicitly invokes the tdd skill. Do not trigger from ordinary requests to add tests or implement a feature.

  • Webapp testing

    vijpatel7/favorite_skills_and_plugins/.agents/skills/webapp-testing Skill

    0★ repo

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    The same file is in 45 other repositories

  • Webapp testing

    agykit/agykit/.agent/skills/webapp-testing Skill

    no license0★ repo

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    The same file is in 45 other repositories

  • Ios test runner

    2sem/mobile-team-skills/plugins/mobile-team-skills/skills/ios-test-runner Skill

    no license0★ repo

    Build and run WhereWeGo iOS tests, report pass/fail results. Use on main agent for smoke tests after simple changes. Escalate to tester subagent for full coverage analysis, diagnosing complex failures, or writing new tests.

  • Ios test runner

    2sem/mobile-team-skills/skills/ios-test-runner Skill

    no license0★ repo

    Build and run WhereWeGo iOS tests, report pass/fail results. Use on main agent for smoke tests after simple changes. Escalate to tester subagent for full coverage analysis, diagnosing complex failures, or writing new tests.

  • Test generator

    Pratiyush/agent-catalog/skills/skill/test-generator Skill

    0★ repo

    Generate test file stubs and boilerplate from source code analysis. Use when the user asks to create tests, add test coverage, or scaffold test files for existing source code.

  • Skill a

    tomkraaij/ai-skills-librarian/fixtures/sample-skills/skill-a Skill

    no license0★ repo

    A fixture skill for tests.

  • Skill b

    tomkraaij/ai-skills-librarian/fixtures/sample-skills/skill-b Skill

    no license0★ repo

    Another fixture skill for tests.

  • Playwright pool

    timi-ty/agent-forge/skills/playwright-pool Skill

    0★ repo

    Set up and use the Playwright browser pool MCP server. Enables multiple agents to run isolated browser sessions simultaneously without contention. Works with both Cursor and Claude Code. TRIGGER on "set up playwright pool", "install playwright pool", "browser pool", or any browser automation task where session isolation is needed. Also triggered automatically by sync-skills after first install.

  • Python unit tests

    ThiagoPanini/aidriven/.claude/skills/python-unit-tests Skill

    0★ repo

    Generate high-quality Python unit tests using pytest, organized with the Given/When/Then (GWT) pattern. Invoke this skill whenever a user wants to create, generate, write, or add Python tests for any code — functions, classes, services, APIs, or modules. Trigger on requests like "write tests for this", "generate unit tests", "add test coverage", "create pytest tests", "test this function", "I need tests for my Python code", "write GWT tests", or "help me test this class". Also use this skill when the user pastes Python code and asks for tests, asks how to test something, wants to improve existing test coverage, or needs tests for edge cases, error handling, or validation logic. Even if the user doesn't say "GWT" or "Given/When/Then", use this skill for any Python test generation request.

  • Python unit tests

    ThiagoPanini/aidriven/.github/skills/python-unit-tests Skill

    0★ repo

    Generate high-quality Python unit tests using pytest, organized with the Given/When/Then (GWT) pattern. Invoke this skill whenever a user wants to create, generate, write, or add Python tests for any code — functions, classes, services, APIs, or modules. Trigger on requests like "write tests for this", "generate unit tests", "add test coverage", "create pytest tests", "test this function", "I need tests for my Python code", "write GWT tests", or "help me test this class". Also use this skill when the user pastes Python code and asks for tests, asks how to test something, wants to improve existing test coverage, or needs tests for edge cases, error handling, or validation logic. Even if the user doesn't say "GWT" or "Given/When/Then", use this skill for any Python test generation request.