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

  • Web3 testing

    AravindS-Wick/aravindhan-skills/skills/library/web3-testing Skill

    no license0★ repo

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

  • Wordpress penetration testing

    AravindS-Wick/aravindhan-skills/skills/library/wordpress-penetration-testing Skill

    no license0★ repo

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

  • Playwright skill

    AravindS-Wick/aravindhan-skills/skills/playwright-skill Skill

    no license0★ repo

    IMPORTANT - Path Resolution: This skill can be installed in different locations (plugin system, manual installation, global, or project-specific). Before executing any commands, determine the skill directory based on where you loaded this SKILL.md file, and use that path in all commands below.

  • Playwright

    AravindS-Wick/aravindhan-skills/skills/playwright Skill

    no license0★ repo

    Browser automation with Playwright. Use when the user asks to test a website, take screenshots, check responsive design, test login flows, fill forms, check broken links, or automate any browser task.

  • Pr monitor

    AravindS-Wick/aravindhan-skills/skills/pr-monitor Skill

    no license0★ repo

    Monitor PR CI checks with intelligent flaky test detection and optional auto-rerun. Use when the user wants to watch a PR, detect flaky tests, or automatically rerun failed CI. Invoke with /pr-monitor to monitor current PR or /pr-monitor <pr-number> for specific PR.

  • Qa automation

    AravindS-Wick/aravindhan-skills/skills/qa-automation Skill

    no license0★ repo

    Manage and execute tasks for qa-automation. Use when generating Playwright E2E tests, building test strategy, finding uncovered code paths, auditing WCAG 2.1 AA accessibility violations, or creating unit test stubs for web, mobile, or API codebases.

  • Tdd

    AravindS-Wick/aravindhan-skills/skills/tdd Skill

    no license0★ repo

    Enforces writing failing tests (red-green-refactor loop) in Jest, PyTest, JUnit, Vitest, Go test, or RSpec before implementing or modifying backend logic.

  • Webapp testing

    AravindS-Wick/aravindhan-skills/skills/webapp-testing Skill

    no license0★ repo

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

  • Lucid

    dd3ok/lucid/fixtures/policy-pack-codex-plugin/.codex/skills/lucid Skill

    0★ repo

    Test Codex home skill fixture.

  • Lucid

    dd3ok/lucid/fixtures/policy-pack-codex-plugin/plugins/lucid/skills/lucid Skill

    0★ repo

    Test Codex plugin skill fixture.

  • Lucid

    dd3ok/lucid/fixtures/policy-pack-hermes/.hermes/skills/lucid Skill

    0★ repo

    Test Hermes top-level skill fixture.

  • Lucid

    dd3ok/lucid/fixtures/policy-pack-hermes/.hermes/skills/productivity/lucid Skill

    0★ repo

    Test Hermes categorized skill fixture.

  • Lucid

    dd3ok/lucid/fixtures/source-graph/skills/lucid Skill

    0★ repo

    Fixture skill used by source graph evals.

  • Qa test data builders

    barcelosvinicius/basic-engineering/plugins/be/skills/qa-test-data-builders Skill

    0★ repo

    Use when writing unit or integration tests that need test data. Centralize object creation in fixture builders, follow the AAA pattern (Arrange, Act, Assert), and keep data deterministic — avoids repetition and flaky tests.

  • Browser agent automation

    m00kk/agent-skills-playbook/skills/browser-agent-automation Skill

    0★ repo

    Automates web tasks with LLM-driven browsers using Playwright, Browser-Use, or Playwright MCP. Use for browser automation agents, scraping with agents, form filling, or E2E flows described in natural language.

  • Specdd test

    specdd/plugin-cline/skills/specdd-test Skill

    0★ repo

    Use when Cline needs to derive, add, update, or assess tests from active SpecDD specs.

  • Specdd trace

    specdd/plugin-cline/skills/specdd-trace Skill

    0★ repo

    Use when Cline needs to trace SpecDD specs to code, tests, docs, changed files, or coverage gaps.

  • Tests gen

    victoriacheng15/dev-toolchain/tests-gen Skill

    0★ repo

    Programmatically scaffolds language-specific unit test suites with table-driven assertions for Go, TS, Python, and Rust.

  • Firebase emulator e2e harness

    JordanChoo/acfs-agent-skills/firebase-emulator-e2e-harness Skill

    no license0★ repo

    Build or repair deterministic E2E and integration harnesses around Firebase emulators. Use when Playwright, Vitest, or similar tests need seeded Auth, Firestore, Storage, or Functions state without depending on live Firebase services.

  • Firebase stack

    JordanChoo/acfs-agent-skills/firebase-stack Skill

    no license0★ repo

    Discipline for Firebase + GCP projects (Firestore, Functions, Hosting, Storage, Auth, Cloud Tasks, Cloud Scheduler, Secret Manager, BigQuery). Use when the repo contains firebase.json / firestore.rules / firestore.indexes.json, when running `firebase deploy`, editing rules or indexes, working with emulators, provisioning GCP infra, or rotating secrets. Enforces emulator-first testing, rules-test-before-deploy, index/query consistency, secrets hygiene, and scripted pre-flight gates.

  • Playwright testing

    JordanChoo/acfs-agent-skills/playwright-testing Skill

    no license0★ repo

    Discipline for Playwright end-to-end tests. Use when the repo has `@playwright/test` in deps, a `playwright.config.{ts,cjs}`, a `tests/e2e/` directory, or the user mentions e2e, flaky tests, selectors, traces, or Playwright. Enforces selector hierarchy, fixtures-first imports, no-mock policy in protected paths, emulator-only project IDs, trace-on-failure artifact discipline, and structured flake triage.

  • Webapp testing

    MauroProto/mis-skills/external/anthropics-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

  • Tdd

    MauroProto/mis-skills/external/mattpocock-skills/engineering/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 17 other repositories

  • Migrate to shoehorn

    MauroProto/mis-skills/external/mattpocock-skills/misc/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

  • Neon postgres branches

    MauroProto/mis-skills/external/neondatabase-agent-skills/neon-postgres-branches Skill

    0★ repo

    Choose and create the right Neon branch type for testing and development. Use when users ask about Neon branching, migration testing with real data, isolated test environments, schema-only branch workflows for sensitive data, or branch creation via Neon CLI or Neon MCP. Triggers include "Neon branch", "test migrations safely", "branch production data", "schema-only branch", "reset branch" and "sensitive data testing".

  • Test driven development

    MauroProto/mis-skills/external/obra-superpowers/test-driven-development Skill

    0★ repo

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

    The same file is in 33 other repositories

  • Python testing patterns

    MauroProto/mis-skills/external/wshobson-agents/python-testing-patterns Skill

    0★ repo

    Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.

    The same file is in 3 other repositories

  • Write tests

    hesprs/harness/skills/write-tests Skill

    0★ repo

    Defines test standards. Must use before writing any test code.

  • Playwright cli

    MichaelYochpaz/agent-skills/skills/playwright-cli Skill

    0★ repo

    Browser automation via playwright-cli for coding agents. Open browsers, navigate pages, take accessibility snapshots, interact with elements including canvas and WebGL content, capture screenshots, inspect network and console, manage cookies and storage, and generate Playwright test code. Use when the user mentions browser testing, web page inspection, taking screenshots, investigating page elements, UI testing, end-to-end testing, web scraping, data extraction, userscripts, or any browser-based interaction. Do not use for ordinary execution of existing Playwright test suites (use npx playwright test) or simple static page fetching. Use for interactive test debugging, authoring, or healing when browser inspection or control is needed.

  • Browser test

    shoji9x9/skills/skills/browser-test Skill

    0★ repo
  • Hilt

    Randomguy01/claudekit/plugins/hilt/skills/hilt Skill

    no license0★ repo

    Set up and use Hilt for dependency injection in an Android app. Use this skill when the user works with Hilt or Dagger-based DI on Android — annotating the Application with @HiltAndroidApp, injecting into activities/fragments/services with @AndroidEntryPoint, writing @Module bindings with @Binds/@Provides, qualifiers, component scopes, multi-module setups, injecting ViewModels (@HiltViewModel) and using them from Compose or Navigation, WorkManager injection, or testing Hilt code. Applies even when the user doesn't say "Hilt" by name — e.g. "wire up dependency injection on Android," "@Inject / @Module won't compile," "provide a Retrofit/OkHttp/Room instance to my ViewModel," or "swap a fake binding in an instrumented test." Skip for manual/constructor DI without a framework, plain Dagger on non-Android platforms, or DI on other platforms entirely.

  • Firebase emulators

    DentVega/firebase-agent-skills/skills/firebase-emulators Skill

    0★ repo

    Configures and runs the Firebase Local Emulator Suite for development — Firestore, Auth, Functions, Storage, RTDB, Pub/Sub, Eventarc — including client connection from web and Expo/React Native, seeding data via import/export, running rules unit tests, and using emulators in CI. Use whenever the user wants to develop or test Firebase code without hitting production, burning quota, or risking real data.

  • Smoke test

    jrausercisco/trmnl-agent-bridge/plugins/claude/trmnl-agent-bridge/skills/smoke-test Skill

    0★ repo

    Run the TRMNL Agent Bridge smoke test in dry mode or live mode and summarize push and current-screen verification results.

  • Smoke test

    jrausercisco/trmnl-agent-bridge/plugins/trmnl-agent-bridge/skills/smoke-test Skill

    0★ repo

    Run the TRMNL Agent Bridge smoke test in dry mode or live mode and summarize push and current-screen verification results.

  • Perform code review

    lhenrique42/ai-templates/skills/perform-code-review Skill

    0★ repo

    Perform comprehensive code review by analyzing git diff, verifying conformance with project rules, validating test suites, and checking adherence to technical specs and tasks. Generates a structured code review report with severity-classified findings. Use when asked for code review, code quality validation, or pre-merge verification. Do not use for QA testing, bug fixing, or task implementation.

  • Run bugfix workflow

    lhenrique42/ai-templates/skills/run-bugfix-workflow Skill

    0★ repo

    Read documented bugs from bugs.md, analyze root causes, implement fixes with regression tests, validate the full test suite, update bug correction status, and generate a final bugfix report. Use when asked to fix bugs, resolve issues, or run the bugfix workflow for a feature. Do not use for new feature implementation, code review, or QA testing.

  • Validate feature qa

    lhenrique42/ai-templates/skills/validate-feature-qa Skill

    0★ repo

    Validate feature implementation against PRD, technical spec, and task definitions using Playwright MCP E2E testing, WCAG 2.2 accessibility verification, and visual analysis. Documents bugs with screenshot evidence and produces a comprehensive QA report. Use when asked to run QA, validate a feature, or test implementation completeness. Do not use for code review, bug fixing, or task implementation.

  • Create pr

    rauleburro/skills/skills/create-pr Skill

    no license0★ repo

    Creates a GitHub Pull Request after validating that tests, linter, and coverage pass. Pushes the branch, generates an English PR title and description from the commits, and integrates with Jira (links the ticket, updates status). Use this skill when the user says "create PR", "crear PR", "open PR", "push and create PR", "make a pull request", "abre un PR", "sube el PR", "/create-pr", or any variation of wanting to submit their work as a pull request. Also triggers when the user says they're done with a task and want to send it for review. Works with any project stack (Django, Next.js, Node, etc.).

  • Tdd

    tyecode/skills/skills/engineering/tdd Skill

    0★ repo

    Enforces test-driven development — failing test written before any implementation code. Use when adding features, fixing bugs, writing tests, or when user says "use TDD".

  • Memory poisoning test designer

    vibesec-advisory/vibesec-advisory-skill-library/SKILLS/memory-write-quarantine-review/skills/memory-poisoning-test-designer Skill

    0★ repo

    Use when a workflow needs a cross-session test that checks whether hostile, stale, low-trust, or unsupported memory can steer future planning, retrieval, tools, or output.

  • Tool policy fixture builder

    vibesec-advisory/vibesec-advisory-skill-library/SKILLS/negative-authorization-test-review/skills/tool-policy-fixture-builder Skill

    0★ repo

    Use when denied authorization rows need to become concrete policy, wrapper, sandbox, MCP, or CI fixtures that can fail closed before a real tool executes.

  • Specdd test

    specdd/plugin-antigravity/skills/specdd-test Skill

    0★ repo

    Use when Antigravity needs to derive, add, update, or assess tests from active SpecDD specs.

  • Specdd trace

    specdd/plugin-antigravity/skills/specdd-trace Skill

    0★ repo

    Use when Antigravity needs to trace SpecDD specs to code, tests, docs, changed files, or coverage gaps.

  • Mina o1js testing fuzzing

    mysteryon88/skills/mina-protocol/skills/mina-o1js-testing-fuzzing Skill

    0★ repo

    Use when writing or reviewing Mina o1js tests, negative tests, LocalBlockchain tests, proof-enabled smoke tests, fuzz or property-style tests, replay tests, or invariant coverage.

  • Web3 universalmutator

    mysteryon88/skills/web3-universalmutator Skill

    0★ repo

    Use when the user specifically wants Web3 smart-contract mutation testing with Universal Mutator for TON or EVM projects: TON/Blueprint/Acton using Tact, Tolk, FunC; Solidity/EVM using Solidity, Vyper, Fe with Foundry, Hardhat, Truffle, or source-level workflows. Do not use for pure fuzzing, input generation, standalone Web3 audits, or generic non-Web3 Universal Mutator runs unless comparing fuzzing with mutation testing.

  • Refactor testing

    evindunn/ai-skills/refactor-testing Skill

    0★ repo

    Find, propose, cache, and implement high-value tests in a local code repository with a target-selection checkpoint. Use when Codex is asked to refactor testing, add missing tests, improve coverage, search a repo for modules that would benefit from tests, identify the best test target, confirm or choose alternatives, cache candidates and completed refactors for about one hour, implement tests with locally available tooling, and mark completed targets after implementation.

  • Dev pilot

    JimmyBlanquet/project-forge/skills/dev-pilot Skill

    0★ repo

    Full autonomous pipeline orchestrator that loops over features.json and executes the complete development cycle for each feature: spec → plan → tasks → implement → validate → deploy → smoke test. Use this when the user wants to run the autonomous development pipeline, process all pending features, execute the full dev cycle end-to-end, go from features.json to deployed features automatically, or automate the entire SDLC for a project. Also triggers on "dev pilot", "dev-pilot", "run the pipeline", "process all features", "autonomous mode", "full cycle", or "pipeline run". Manages feature lifecycle in features.json (todo → specifying → implementing → validating → staging → done) with escalation on failures. This does NOT implement individual features (use ralph-loop), run individual spec steps (use speckit-* skills), or manage infrastructure. It is the top-level orchestrator that chains all other tools together.

  • Audit sdlc

    JimmyBlanquet/project-forge/skills/speckit/audit-sdlc Skill

    0★ repo

    Audit the software development lifecycle (SDLC) maturity of the current project. Scans the codebase, CI/CD configs, testing setup, security tools, documentation, and operational readiness, then produces a scored report with a prioritized action plan. Use this skill when the user wants to assess project health, check SDLC coverage, run a maturity audit, find gaps in their development workflow, compare their project to industry standards, or get recommendations for improvement. Also triggers on "audit sdlc", "project health check", "what am I missing", "maturity assessment", "how production-ready am I", "gap analysis", "check my project", "what should I improve", "development best practices check", or "sdlc review". This is a read-only diagnostic skill — it does NOT fix issues, only reports findings and recommends actions. Designed for AI-first solo developer workflows with the 80/20 rule in mind: maximum impact, minimum effort.

  • E2e

    JimmyBlanquet/project-forge/skills/speckit/e2e Skill

    0★ repo

    Run comprehensive end-to-end tests on the application using agent-browser (accessibility-tree-based browser testing). Use this skill when the user wants to run E2E tests, perform automated browser testing, verify the app works end-to-end, test user journeys in a real browser, check for UI bugs or regressions, do responsive testing across viewports, hunt for security issues via browser interaction, or validate that a feature works from the user's perspective. Also triggers on "speckit e2e", "speckit-e2e", "test the app in the browser", "run browser tests", "check if the UI works", "test user flows", "verify the feature end to end", or "automated acceptance testing". This skill launches 3 parallel research sub-agents (app structure, data flows, bug hunting), starts the dev server, creates a combined test plan, executes tests with agent-browser snapshots and screenshots, and fixes bugs as they are found. It generates an e2e-report.md with results and evidence screenshots. This does NOT generate a recette/UAT checklist without running tests (use speckit-recette), write unit tests or integration tests in code (those are part of speckit-tasks), or run tests via Playwright/Cypress — it uses agent-browser for exploration. For deterministic regression tests in CI, use Playwright (`pnpm test:e2e`).

  • Recette

    JimmyBlanquet/project-forge/skills/speckit/recette Skill

    0★ repo

    Generate a recette (acceptance testing checklist) from the feature specification to validate that a feature meets all acceptance scenarios. Use this skill when the user wants to create a recette, build a UAT checklist, generate acceptance test scenarios, prepare for manual or automated feature validation, create a QA checklist, or verify a feature against its spec. Also triggers on "speckit recette", "speckit-recette", "create recette", "acceptance testing", "QA checklist", "generate test checklist from spec", "validate the feature", "UAT scenarios", "recette checklist", or "verification checklist". This skill reads spec.md, extracts all acceptance scenarios (AS1.1, AS1.2, etc.), and generates a structured recette.md with pre-conditions, manual test steps, expected outcomes, non-functional checks (performance, security, accessibility), and a systematic debugging protocol for failures. It can optionally run automated verification using agent-browser if installed. This does NOT run full E2E test suites with parallel research agents (use speckit-e2e for that), write the feature specification (use speckit-specify), or generate implementation tasks (use speckit-tasks). The recette is a validation artifact, not a planning artifact.

  • Test bridge

    JimmyBlanquet/project-forge/skills/speckit/test-bridge Skill

    0★ repo

    Pont entre les Acceptance Scenarios SpecKit et Playwright Agents. Convertit les AS de spec.md en specs Markdown compatibles Planner, lance le Generator, et vérifie la traçabilité spec→test. Utiliser après speckit-tasks pour garantir que chaque scenario d'acceptation a un test E2E correspondant.

  • Specdd test

    specdd/plugin-copilot/skills/specdd-test Skill

    0★ repo

    Use when GitHub Copilot needs to derive, add, update, or assess tests from active SpecDD specs.

  • Specdd trace

    specdd/plugin-copilot/skills/specdd-trace Skill

    0★ repo

    Use when GitHub Copilot needs to trace SpecDD specs to code, tests, docs, changed files, or coverage gaps.

  • Ghost db

    webdevtodayjason/dev-kit/plugins/dev-kit/skills/ghost-db Skill

    no license0★ repo

    Ephemeral, forkable Postgres databases via ghost.build — the agent-native database service. Use this skill when the user needs: a throwaway Postgres for testing, a safe fork of an existing database to experiment against without polluting state, an isolated DB per agent task, or any work that benefits from "create-fork-discard freely" semantics. Triggers: user says "ghost create", "fork the database", "spin up a Postgres", "I need a test DB", "give me a database for this agent", "ghost.build", or describes a scenario that would otherwise require a Docker postgres container + manual setup + manual teardown. The CLI lives at `~/.local/bin/ghost`. MCP tools are also available (install via `ghost mcp install`) and are the preferred surface for in-conversation database operations.

  • Tdd

    webdevtodayjason/dev-kit/plugins/dev-kit/skills/tdd Skill

    no license0★ 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 292 other repositories

  • Ui demo video

    giostriquer/agent-workshop/plugins/toolkit/skills/ui-demo-video Skill

    0★ repo

    Use after UI work that can be verified visually — a new element, layout change, or user flow in a web app whose dev server a browser can drive. Records a Playwright-driven video walkthrough of the running app, emitting a per-scene PNG frame the model reads to verify the UI itself — both shareable evidence (PR demo) and a model feedback loop. Use the frames as the visual feedback loop even when nobody asked for a video. NOT for API-only or non-visual changes, and not a test suite — scenes demonstrate and verify visually, they do not assert.

  • Tdd

    patdhlk/skills/skills/tdd Skill

    0★ repo

    Test-driven development in vertical slices - red-green-refactor against real behavior, wired into the issue lifecycle (picks up an issue, sets in-progress, closes done). Use when the user wants to build a feature or fix a bug test-first, mentions TDD or red-green-refactor, or hands over an issue ID to implement.

    The same file is in 1 other repository

  • Sf test scenario generator

    SahirVhora/sf-agent-skills/skills/sf-test-scenario-generator Skill

    0★ repo

    Use when you need to generate UAT test scenarios from live SF business rules and workflow config -- covering happy path, edge cases, and cross-process interactions.

  • Godot qa playtester

    schmoenraad/godot-gamestudio/plugins/godot-gamestudio/skills/godot-qa-playtester Skill

    0★ repo

    Independently verify Godot milestones through imports, parse checks, tests, runtime input, state inspection, screenshots, animation checks, performance evidence, and regression testing. Use as the final verifier in Godot Gamestudio or for standalone Godot QA.

  • Godot qa playtester

    schmoenraad/godot-gamestudio/skills/godot-qa-playtester Skill

    0★ repo

    Independently verify Godot milestones through imports, parse checks, tests, runtime input, state inspection, screenshots, animation checks, performance evidence, and regression testing. Use as the final verifier in Godot Gamestudio or for standalone Godot QA.