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

  • Test driven development

    ahnafyy/skills-evals/test/fixtures/sample-repo/skills/test-driven-development Skill

    1★ repo

    Write a failing test before implementing any fix or feature. Use when fixing bugs, adding features, or refactoring code that lacks test coverage.

  • Github repo setup

    fullREFIT/skills/skills/github-repo-setup Skill

    1★ repo

    Repository-agnostic setup agent that clones, inspects, installs, and smoke-tests any GitHub repository using the repo's own manifests rather than assumptions. Detects language stack (Node, Python, Rust, Go, Ruby, Deno, Bun, Docker) from lockfiles, aligns toolchains via version managers (nvm, pyenv, rustup, asdf, mise), installs with the correct package manager, handles .env setup, runs a minimum smoke test, and produces structured phase reports. Optimized for macOS arm64 with Homebrew, nvm, pyenv, and 1Password CLI; branches for Linux and Windows. Use when setting up a cloned repository, evaluating a new GitHub project, reproducing an environment, or onboarding a codebase. MANDATORY TRIGGERS: github repo setup, clone and install, repo setup, set up repository, install this repo, set up this project, onboard codebase, reproduce environment, new repo, fresh repo, get this repo running, set up dev environment, repo install, universal setup, github setup.

  • Entalpa implement

    entalpa/entalpa-mcp/skills/entalpa-implement Skill

    1★ repo

    Use this skill when working with Entalpa through its MCP server to implement stories and requirements that were authored on the Entalpa website, inspect the project/stakeholder/story/requirement/subsystem hierarchy, record code references, implementation status, and test coverage back onto requirements, or otherwise perform requirements-engineering work that should preserve traceability and avoid destructive MCP tool calls.

  • Testing

    Aiweline/WelineFramework/.codex/skills/testing Skill

    1★ repo

    WelineFramework local testing adapter. Use when working in this repo on how to write module tests, choose validation layers, or run PHPUnit, Pest, Vitest, Playwright, HTTP smoke, Browser smoke, or WLS-backed test flows. Read dev/ai/skills/testing/SKILL.md before acting.

  • E2E自动化工程师 端到端流程测试

    Aiweline/WelineFramework/dev/ai/codex/plugins/weline-codex-plugin/skills/E2E自动化工程师-端到端流程测试 Skill

    1★ repo

    E2E automation engineer skill for Playwright-driven flow validation, browser interaction coverage, and end-to-end regression checks. Disabled by default for E2E case/spec work; use only when the user explicitly asks for E2E tests or execution.

  • Testing

    Aiweline/WelineFramework/dev/ai/codex/plugins/weline-codex-plugin/skills/testing Skill

    1★ repo

    WelineFramework testing guide and routing skill. Use when the user asks how to write tests, where module tests live, how to run PHPUnit/Pest/Vitest/Playwright, or how to choose unit, integration, HTTP smoke, Browser smoke, and E2E coverage. Does not authorize creating test artifacts unless the user explicitly asks.

  • 单元测试工程师 单元测试覆盖

    Aiweline/WelineFramework/dev/ai/codex/plugins/weline-codex-plugin/skills/单元测试工程师-单元测试覆盖 Skill

    1★ repo

    Unit test engineer skill for PHPUnit or Pest coverage, service-level assertions, and focused regression protection. Disabled by default; use only when the user explicitly asks to write, update, or run unit tests.

  • E2E自动化工程师 端到端流程测试

    Aiweline/WelineFramework/dev/ai/skills/E2E自动化工程师-端到端流程测试 Skill

    1★ repo

    E2E automation engineer skill for Playwright-driven flow validation, browser interaction coverage, and end-to-end regression checks. Disabled by default for E2E case/spec work; use only when the user explicitly asks for E2E tests or execution.

  • Testing

    Aiweline/WelineFramework/dev/ai/skills/testing Skill

    1★ repo

    WelineFramework testing guide and routing skill. Use when the user asks how to write tests, where module tests live, how to run PHPUnit/Pest/Vitest/Playwright, or how to choose unit, integration, HTTP smoke, Browser smoke, and E2E coverage. Does not authorize creating test artifacts unless the user explicitly asks.

  • 单元测试工程师 单元测试覆盖

    Aiweline/WelineFramework/dev/ai/skills/单元测试工程师-单元测试覆盖 Skill

    1★ repo

    Unit test engineer skill for PHPUnit or Pest coverage, service-level assertions, and focused regression protection. Disabled by default; use only when the user explicitly asks to write, update, or run unit tests.

  • Mvp e2e promotability

    authenticfake/clike/extensions/vscode/templates/harper-init/.clike/skills/mvp-e2e-promotability Skill

    1★ repo

    Convert requirements into narrow but end-to-end promotable MVP slices instead of shallow demos or decorative code.

  • Add tests

    bob798/ai-skill-kit/development/add-tests Skill

    no license1★ repo

    给已有代码补充单元测试。先读实现,识别可测函数,逐函数补充测试用例,确保全部通过。

  • Ok itest

    bob798/ai-skill-kit/development/ok-itest Skill

    no license1★ repo

    Generate executable integration-test specs, skeletons, and PR reports for Spring Boot + Spring AI services. Trigger when the user wants to write integration tests, add wire-level ITs, draft an IT spec, or produce a PR test report.

  • Ok testaudit nuxt

    bob798/ai-skill-kit/development/ok-testaudit-nuxt Skill

    no license1★ repo

    Audit test coverage for the Nuxt 3 + Vitest + Playwright frontend (os-web), identify gaps, and generate missing tests with a structured multi-phase approach

  • Ok testaudit server

    bob798/ai-skill-kit/development/ok-testaudit-server Skill

    no license1★ repo

    Audit test coverage for the Spring Boot + Spring AI backend (os-server), identify gaps (esp. multi-tenant isolation & LLM tool chains), and generate missing tests with a structured multi-phase approach

  • Test audit

    bob798/ai-skill-kit/development/test-audit Skill

    no license1★ repo

    Audit test coverage across all dimensions, identify gaps, and generate missing tests with a structured multi-phase approach

  • Ci

    jovd83/playwright-skill/ci Skill

    1★ repo

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

  • Core

    jovd83/playwright-skill/core Skill

    1★ repo

    Core Playwright implementation skill for resilient test authoring and debugging. Use when Codex needs practical Playwright guidance for locators, assertions, fixtures, authentication, network behavior, API testing, component testing, debugging, framework-specific recipes, or broader test architecture decisions.

  • Auto sync

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

    1★ repo

    Coverage-maintenance skill for Playwright 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/playwright-skill/coverage_plan/generation Skill

    1★ repo

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

  • Review

    jovd83/playwright-skill/coverage_plan/review Skill

    1★ repo

    Coverage-plan review skill for Playwright 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.

  • Root cause

    jovd83/playwright-skill/documentation/root_cause Skill

    1★ repo

    Failure-analysis skill for Playwright 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.

  • Bdd

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

    1★ repo

    Legacy Playwright-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 Playwright-local conventions must be preserved explicitly.

  • Plain text

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

    1★ repo

    Legacy Playwright-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 Playwright-local conventions must be preserved explicitly.

  • Tdd

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

    1★ repo

    Legacy Playwright-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 Playwright-local conventions must be preserved explicitly.

  • Tests

    jovd83/playwright-skill/documentation/tests Skill

    1★ repo

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

  • Intellij junie

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

    1★ repo

    Editor-setup skill for Playwright plus Junie in IntelliJ IDEA. Use when Codex needs to help configure an IntelliJ-based Playwright workflow with the Junie assistant and verify the environment is ready for authoring and running tests.

  • Vscode codex

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

    1★ repo

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

  • Testlink

    jovd83/playwright-skill/mappers/testlink Skill

    1★ repo

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

  • Testrail

    jovd83/playwright-skill/mappers/testrail Skill

    1★ repo

    Test-management mapping skill for TestRail. Use when Codex needs to apply authoritative TestRail case IDs back into local Playwright docs, titles, or annotations so automation can be traced or reported accurately.

  • Xray

    jovd83/playwright-skill/mappers/xray Skill

    1★ repo

    Test-management mapping skill for Xray. Use when Codex needs to apply authoritative Xray test keys or issue IDs back into local Playwright docs, tags, or annotations for reliable traceability and reporting.

  • Zephyr

    jovd83/playwright-skill/mappers/zephyr Skill

    1★ repo

    Test-management mapping skill for Zephyr Scale. Use when Codex needs to apply authoritative Zephyr test keys back into local Playwright docs, titles, or annotations so execution and planning artifacts stay aligned.

  • Migration

    jovd83/playwright-skill/migration Skill

    1★ repo

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

  • Orchestrator

    jovd83/playwright-skill/orchestrator Skill

    1★ repo

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

  • Playwright cli

    jovd83/playwright-skill/playwright-cli Skill

    1★ repo

    Browser-automation skill for terminal-driven Playwright work. Use when Codex needs to navigate websites, inspect pages, interact with forms, capture screenshots or traces, manage browser sessions, mock requests, or generate test code through a local `playwright-cli` workflow instead of writing a full test first.

  • Pom

    jovd83/playwright-skill/pom Skill

    1★ repo

    Test-architecture skill for Playwright page objects, fixtures, and helpers. 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/playwright-skill/reporters/testlink Skill

    1★ repo

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

  • Testrail

    jovd83/playwright-skill/reporters/testrail Skill

    1★ repo

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

  • Xray

    jovd83/playwright-skill/reporters/xray Skill

    1★ repo

    Test-management reporting skill for Xray. Use when Codex needs to publish Playwright execution results into Xray or Jira using the project's mappings, import format, and chosen reporting flow.

  • Zephyr

    jovd83/playwright-skill/reporters/zephyr Skill

    1★ repo

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

  • Stakeholder

    jovd83/playwright-skill/reporting/stakeholder Skill

    1★ repo

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

  • Testlink

    jovd83/playwright-skill/transformers/testlink Skill

    1★ repo

    Legacy Playwright-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 Playwright-local conventions must be preserved explicitly.

  • Testrail

    jovd83/playwright-skill/transformers/testrail Skill

    1★ repo

    Legacy Playwright-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 Playwright-local conventions must be preserved explicitly.

  • Xray

    jovd83/playwright-skill/transformers/xray Skill

    1★ repo

    Legacy Playwright-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 Playwright-local conventions must be preserved explicitly.

  • Zephyr

    jovd83/playwright-skill/transformers/zephyr Skill

    1★ repo

    Legacy Playwright-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 Playwright-local conventions must be preserved explicitly.

  • Measure

    rmzlb/baaton-skills/marketing/measure Skill

    1★ repo

    Marketing measurement, reporting, and iteration frameworks. Metrics by platform, attribution models, content performance analysis, A/B testing, and reporting templates. Use when: analyzing content performance, building reports, deciding what to post next, setting up tracking, A/B testing content, or reviewing marketing ROI. Trigger words: analytics, metrics, performance, report, ROI, conversion, A/B test, what's working, engagement rate, attribution, funnel analysis, dashboard. NOT for: writing content (use write), auditing quality (use audit), or defining strategy (use strategy).

  • Test

    eduardo-lezama/intranet-dashboard/.windsurf.bak/skills/test Skill

    no license1★ repo

    Usar al crear o modificar tests con pytest

  • Paystack testing

    rexedge/paystack/skills/paystack-testing Skill

    no license1★ repo

    Paystack Testing Guide — comprehensive testing strategies for Paystack integrations using test mode keys. Covers test card numbers, bank account test data, webhook testing, transaction simulation, transfer testing, and end-to-end test patterns. Use this skill whenever writing tests for Paystack payments, simulating transactions in test mode, testing webhook handlers, mocking Paystack API responses, validating payment flows before going live, or debugging failed test transactions. Also use when you see references to sk_test_, pk_test_, test card numbers, or Paystack test mode.

  • Qemu user mode

    BenGardiner/bitbake-yocto-agent-skills/qemu-user-mode Skill

    1★ repo

    Runs target binaries via QEMU user-mode emulation. Use when testing ARM binaries natively on a host system, extracting root filesystems, or running headless Yocto tests without booting a full QEMU system image. Do not use for full system emulation or kernel debugging.

  • Dummy test skill

    MatrixFounder/Universal-skills/tests/mock-skill-creation/dummy-test-skill Skill

    1★ repo

    Use when [TRIGGER: specific symptoms or situations]...

  • Legacy safety rails

    ForeverSc/ai-handrail/skills/legacy-safety-rails Skill

    1★ repo

    Use when a legacy project needs test coverage, observability, feature flags, or rollback mechanisms before refactoring. Triggers when user says "add tests to this old code", "make this safe to refactor", "add guardrails", "protect this before changing it", or after legacy-doc-bootstrap has created docs.

  • Test strategy designer

    bingooyong/agent-skills/skills/test-strategy-designer Skill

    no license1★ repo

    Analyze code changes and design targeted test strategies covering impact scope, test types, and priority. Use when (1) determining what tests are needed after code changes, (2) designing test plans for new features or bug fixes, (3) estimating test effort and coverage gaps, (4) selecting appropriate test types. Outputs actionable test strategies with priority and scope.

  • Test and fix

    yu-iskw/coding-agent-fabric/.claude/skills/test-and-fix Skill

    1★ repo

    Run unit tests and automatically fix code failures, regression bugs, or test mismatches. Use when tests are failing, after implementing new features, or to repair "broken" tests.

    The same file is in 1 other repository

  • Test integration docker

    yu-iskw/coding-agent-fabric/.claude/skills/test-integration-docker Skill

    1★ repo

    Run comprehensive integration tests using real skills (Vercel, Anthropic, Expo) in a Docker container. Managed via Makefile for standard lifecycle control.

  • Javascript testing patterns

    yunseo-kim/agent-toolbox/.agents/skills/javascript-testing-patterns Skill

    no license1★ repo

    Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.

  • Ab test setup

    yunseo-kim/agent-toolbox/catalog/skills/ab-test-setup Skill

    no license1★ repo

    Plan, design, and implement A/B tests and experiments with proper sample sizing, statistical significance, and hypothesis frameworks

  • Ci triage

    yunseo-kim/agent-toolbox/catalog/skills/ci-triage Skill

    no license1★ repo

    Triage CI failures and PR review comments with structured methodology. Use when investigating failing CI jobs, flaky tests, or analyzing PR review feedback. Covers blocker-first prioritization, failure categorization, local reproduction discipline, and parallel log analysis.

  • Flags sdk

    yunseo-kim/agent-toolbox/catalog/skills/flags-sdk Skill

    no license1★ repo

    Comprehensive guide for implementing feature flags and A/B tests using the Flags SDK (the `flags` npm package). Use when: (1) Creating or declaring feature flags with `flag()`, (2) Setting up feature flag providers/adapters (Vercel, Statsig, LaunchDarkly, PostHog, GrowthBook, Hypertune, Edge Config, OpenFeature, Flagsmith, Reflag, Split, Optimizely, or custom adapters), (3) Implementing precompute patterns for static pages with feature flags, (4) Setting up evaluation context with `identify` and `dedupe`, (5) Integrating the Flags Explorer / Vercel Toolbar, (6) Working with feature flags in Next.js (App Router, Pages Router, Middleware) or SvelteKit, (7) Writing custom adapters, (8) Encrypting/decrypting flag values for the toolbar, (9) Any task involving the `flags`, `flags/next`, `flags/sveltekit`, `flags/react`, or `@flags-sdk/*` packages. Triggers on: feature flags, A/B testing, experimentation, flags SDK, flag adapters, precompute flags, Flags Explorer, feature gates, flag overrides.

  • Frontend testing

    yunseo-kim/agent-toolbox/catalog/skills/frontend-testing Skill

    no license1★ repo

    Generate comprehensive Vitest and React Testing Library tests for frontend components, hooks, and utilities. Covers test structure, incremental workflow, async patterns, mocking strategies, and coverage goals. Use when writing or reviewing frontend tests, improving coverage, or setting up testing infrastructure for React projects.

  • Webapp testing

    yunseo-kim/agent-toolbox/catalog/skills/webapp-testing Skill

    no license1★ repo

    Test local web applications using Playwright with server lifecycle management, browser automation, and visual verification. Use for frontend testing, debugging UI, capturing screenshots, and viewing browser logs.