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

  • Doc coauthoring reader testing

    evertonfernandes3321-wq/mythos-skills/doc-coauthoring-reader-testing Skill

    0★ repo

    Co-autoria de documentos tecnicos (specs, RFCs, propostas, design docs, READMEs, ADRs, runbooks) em 3 estagios com gates, para qualquer dominio e stack — coleta de contexto multi-turn (info dump + perguntas clarificadoras), refino secao-a-secao (clarificar->brainstorm->curar->draft->iterar) com edits incrementais, e reader testing com contexto fresco (prever perguntas do leitor, testar com sub-agente/instancia fresca, cacar ambiguidade) antes de publicar. Use para escrever docs que realmente funcionam para o leitor.

  • E2e test architecture

    evertonfernandes3321-wq/mythos-skills/e2e-test-architecture Skill

    0★ repo

    Arquitetura de testes E2E resilientes para qualquer framework (Playwright/Cypress/Selenium/WebdriverIO/Appium/Detox e outros) — Page Object Model, prioridade de seletores por papel/acessibilidade, esperas resilientes sem timeout fixo (auto-wait), locator chaining/filtering, isolamento de estado entre testes e disciplina anti-flakiness. Playbook stack-agnostico com exemplos por ecossistema, verificacao empirica e modo de auditoria de conformidade. Complementa a auditoria de cobertura (test-coverage-audit) focando em confiabilidade e manutenibilidade dos testes de ponta a ponta.

  • Test coverage audit

    evertonfernandes3321-wq/mythos-skills/test-coverage-audit Skill

    0★ repo

    Auditoria de cobertura de testes para qualquer stack — identifica areas criticas sem testes e propoe testes unitarios, de integracao e de casos de erro, priorizando autenticacao, pagamentos, dados de usuario e logica de negocio. Foca em comportamento (nao implementacao) e indica o framework de teste adequado ao projeto.

  • Cook

    SoftwareOneHN/dev-kit/references/cook Skill

    0★ repo

    Implement tasks incrementally with test-first discipline. Use when ready to write code after planning. Supports --tdd flag for strict RED→GREEN→REFACTOR cycle.

  • Test

    SoftwareOneHN/dev-kit/references/test Skill

    0★ repo

    Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports.

  • Skill activation test

    muqian2026-rgb/qian-public/skills/skill-activation-test Skill

    no license0★ repo

    Test whether a Cursor skill triggers correctly: 5 positive prompts, 3 negative, metadata audit. Use after writing or updating any SKILL.md. Pairs with book-learn-distill.

  • Browser testing with devtools

    jae-labs/skills/skills/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 real runtime data. Requires the chrome-devtools MCP server to be configured.

  • Test driven development

    jae-labs/skills/skills/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

  • Test driven development

    BAKUGOS1/SkilledAgents-Toolkit/plugins/skilled-agents/skills/test-driven-development Skill

    0★ repo

    Use when implementing any feature or bugfix in Wrkly — write the test first, watch it fail, write minimal code to pass.

  • Webapp testing

    BAKUGOS1/SkilledAgents-Toolkit/plugins/skilled-agents/skills/webapp-testing Skill

    0★ repo

    Local web application testing workflow for browser automation, Playwright-style checks, screenshots, console logs, UI behavior debugging, responsive verification, and regression QA. Use when verifying a local web app, testing a frontend change, reproducing UI bugs, checking browser console errors, or validating user flows after implementation.

  • Webapp testing

    BAKUGOS1/SkilledAgents-Toolkit/skills/codex/webapp-testing Skill

    0★ repo

    Local web application testing workflow for browser automation, Playwright-style checks, screenshots, console logs, UI behavior debugging, responsive verification, and regression QA. Use when verifying a local web app, testing a frontend change, reproducing UI bugs, checking browser console errors, or validating user flows after implementation.

  • Test driven development

    BAKUGOS1/SkilledAgents-Toolkit/skills/projects/wrkly/test-driven-development Skill

    0★ repo

    Use when implementing any feature or bugfix in Wrkly — write the test first, watch it fail, write minimal code to pass.

  • Test knowledge

    openjck/agent-skills/skills/test-knowledge Skill

    0★ repo

    Help one improve their understanding of a topic by reading their summary of the topic, correcting any mistakes in their understanding, encouraging them to write a new summary, and repeating this process until they provide a summary that is accurate.

  • Data connector building

    selamy-labs/agent-skills/skills/data-connector-building Skill

    0★ repo

    Use when building integrations or replacing synthetic demos with real data sources. Requires source contracts, idempotent ingestion, validation, observability, and fixture-backed tests.

  • Feature coverage not just line coverage

    selamy-labs/agent-skills/skills/feature-coverage-not-just-line-coverage Skill

    0★ repo

    Use when coverage percentage is treated as proof. Require named feature behavior tests, source fixtures, and anti-overfit checks alongside line coverage.

  • Instrumented service scaffold

    selamy-labs/agent-skills/skills/instrumented-service-scaffold Skill

    0★ repo

    Use when creating or reviewing a new long-running service so observability, runtime flags, tests, coverage gates, and release controls exist from the first commit.

  • Property based testing

    selamy-labs/agent-skills/skills/property-based-testing Skill

    0★ repo

    Use when example tests can't cover the input space — parsers, serializers, encoders, money math, state machines, anything with a roundtrip or invariant. Assert properties that hold for all inputs, let the framework generate cases and shrink failures to a minimal counterexample.

  • Sim zero mode

    selamy-labs/agent-skills/skills/sim-zero-mode Skill

    0★ repo

    Use when building/testing an app or agent that depends on paid APIs or LLM calls and you must exercise plumbing/UI/harness without spend or real intelligence, for CI, demos, local dev. Activates on test without burning API budget, demo without live calls, or fakes/offline mode.

  • Table driven tests

    selamy-labs/agent-skills/skills/table-driven-tests Skill

    0★ repo

    Use when one behavior should be checked against many input and output cases. Put cases in a named table and run the same assertion path.

  • Test design

    selamy-labs/agent-skills/skills/test-design Skill

    0★ repo

    Use when writing or reviewing tests: how to STRUCTURE and NAME them, what one test should cover, and when to split versus parameterize versus use soft assertions. Covers test structure and design, not the red-green-refactor workflow.

  • Native macos test

    Myra-Agents/skills/skills/native-macos-test Skill

    0★ repo

    Author and run reusable component UI tests for a NATIVE macOS app (Tauri, Electron, or any WKWebView/AppKit app) by driving the macOS accessibility (AX) tree — match elements by AXRole + name/label, act with AXPress, type with real key events. YOU (the agent) run everything; the user just converses. The harness is vendored into the app repo (default tests/native/) so the test library is versioned WITH the app and self-locating across sessions. USE THIS when asked to: "test the desktop/Tauri app", "write a UI test for the native app", "add an AX/accessibility test", "automate clicking through the app", "add this flow to the test library", "component test for the macOS app", "regression test the app UI". Triggers: "test the app", "UI test", "AX test", "automate the desktop app", "drive the app", "macOS app test". Pixel-coordinate clicking is banned — everything targets stable AX anchors.

  • Swift auth security audit suite

    esaldgut/ai-native-engineering-workspace/global-skills/apple-auth/swift-auth-security-audit-suite Skill

    0★ repo

    Build a security-audit test suite for an iOS auth subsystem that thinks like an attacker — token-leakage scans (UserDefaults / pasteboard / os_log), ATS validation (no NSAllowsArbitraryLoads), injection and boundary inputs, anti-enumeration (no provider-specific "user not found" leaks for ANY OAuth/OIDC provider), OAuth `state` CSRF + constant-time comparison, concurrent-refresh single-flight, and first-launch Keychain-cleanup idempotency. Built with Swift Testing (@Suite/@Test, Issue.record for soft audit findings). Use when hardening or reviewing the auth/network/storage layers.

  • Swift clean architecture test patterns

    esaldgut/ai-native-engineering-workspace/global-skills/apple-auth/swift-clean-architecture-test-patterns Skill

    0★ repo

    Layered test patterns for Swift MVVM + Clean Architecture — pure unit tests for Core, contract tests for Domain use-cases against repository protocols, @MainActor state-transition tests for @Observable ViewModels, Mirror-based negative-invariant tests (assert no stored property leaks a secret/URL without enumerating every field), and CaseIterable coherence guards for typed-error siblings (errorMessage + category stay in sync). Built with Swift Testing (@Suite/@Test, parameterized, @Tag). Use when adding tests for any layer of a Clean Architecture iOS app.

  • Swift testing framework conventions mvvm

    esaldgut/ai-native-engineering-workspace/global-skills/apple-auth/swift-testing-framework-conventions-mvvm Skill

    0★ repo

    Conventions for testing a Swift MVVM app — when to use Swift Testing vs XCTest (XCTest stays ONLY for XCUIApplication UI automation and XCTMetric performance, per Apple WWDC24), import ordering (regular imports first, @testable last, and why it's substantive not just style), final-class / actor mock idioms with exposed call-counts (the MockK-equivalent), and CaseIterable regression-guard tests that keep typed-error siblings in sync. Use when establishing or reviewing test conventions for any MVVM iOS module.

  • Test quality maintenance

    Nick2bad4u/codex-skills/skills/test-quality-maintenance Skill

    no license0★ repo

    Personal multi-skill repository for reusable Codex workflows.

  • Eval loops

    K-9Nine/skipthespec/eval-loops Skill

    0★ repo

    Design, build, run, and maintain automated test and evaluation loops so Claude can verify its own work without deploying to users. Use when the user says 'eval loop', 'set up evals', 'test harness', 'automated testing', 'how do I know it works', 'regression suite', 'grade the agent', or when a build needs a verification net. Implements Anthropic's evals method: 20-50 tasks from real failures, deterministic graders + LLM-as-judge, grade outcomes not paths, isolated trials, pass@k vs pass^k, read the transcripts. The safety net under autonomous-build and the quality gate before dogfood-loop promotion. Load autonomous-dev first.

  • Qa generated test case

    stardustai/stardust-skills/skills/qa-generated-test-case Skill

    0★ repo

    Generate high-coverage Chinese functional and business-flow test cases from PRDs, especially Web admin or platform PRDs. Use when Codex is asked to extract PRD text, design QA coverage, generate the fixed 7-column testcase table, export CSV/XLSX, validate testcase format, or optionally consult an external indexed PRD memory source without reading full historical archives.

  • Rust testing

    AojdevStudio/development-kit/.claude/skills/rust-testing Skill

    no license0★ repo

    Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.

    The same file is in 8 other repositories

  • Java testing

    mtkhawaja/java-skills/skills/java-testing Skill

    0★ repo

    Use when writing or reviewing Java tests, unit or integration — JUnit Jupiter with AssertJ assertions, the @DisplayName / method-name mirroring convention, behavior-focused naming, Mockito (annotation mocks, no deep stubs, @MockitoBean for Spring), and Testcontainers with @ServiceConnection for real backing services (database, Kafka, Redis). Catches JUnit-assertion use, class-level @DisplayName, imperative or deep-stub mocking, H2-instead-of-real-DB, container-per-method, and slow/flaky suites.

  • Tdd loop

    HM-IT-CODE/forge-skills/skills/engineering/tdd-loop Skill

    0★ repo

    Drives a strict test-driven development loop for any new behavior or bug fix. Use when the user asks to implement a feature, add functionality, fix a bug, or says "use TDD" / "write tests first". Forbids writing production code before a failing test exists.

  • Minimal skill

    tanker327/agent-skill-analysis/tests/fixtures/minimal-skill Skill

    0★ repo

    A minimal skill fixture used exclusively for testing fromDir. Not a real skill.

  • Tech trend watch

    krkrkrr/skills/skills/docs/tech-trend-watch Skill

    no license0★ repo

    Long-term technology stack review using State of JS, State of CSS, and Thoughtworks Technology Radar — satisfaction×usage matrix, ADOPT/TRIAL/ASSESS/HOLD mapping, P0–P3 migration priority. Use for annual stack audits, planning major migrations (jest→vitest, webpack→Vite, etc.), or on-demand replacement decisions. Not for general architecture design.

  • Frontend review testing

    krkrkrr/skills/skills/frontend/frontend-review-testing Skill

    no license0★ repo

    Use when auditing test infrastructure — vitest coverage, playwright configuration, VRT setup, coverage merging. Produces recommendations for Week 2 testing phase. Runs `scripts/audit-coverage.sh`.

  • Translate programming language

    krkrkrr/skills/skills/lang/translate-programming-language Skill

    no license0★ repo

    Plan and execute language-to-language server or application migrations with behavior parity. Use when porting modules, services, APIs, or runtimes between programming languages; generating source-runtime oracles and fixtures; generating migrated parity tests; detecting runtime, standard-library, serialization, numeric, encoding, time, regex, or protocol differences; building temporary compatibility layers; accumulating migration knowledge; benchmarking; shadow testing; canarying; or planning cutover and rollback.

  • Ddd bdd tdd flow

    krkrkrr/skills/skills/meta/ddd-bdd-tdd-flow Skill

    no license0★ repo

    Use when creating a new application or feature from scratch following a structured flow. Executes five mandatory phases in order: (1) structured requirements interview, (2) DDD SUDO modeling with Mermaid diagrams + user review, (3) comprehensive BDD Gherkin feature writing + user review, (4) property derivation and property-based integration/e2e test generation, (5) TDD implementation following t_wada's Red-Green-Refactor cycle. Outputs land in doc/ (models + features), test/ (all tests), src/ (implementation). When NOT to use: small incremental changes to an already-modeled feature; refactors with no behavioral change; hotfixes.

  • Playwright cli

    krkrkrr/skills/skills/testing/playwright-cli Skill

    no license0★ repo

    Automate browser interactions, test web pages and work with Playwright tests.

  • Playwright test

    krkrkrr/skills/skills/testing/playwright-test Skill

    no license0★ repo

    Best practices and reference for Playwright Test (E2E). Covers how to write tests, avoiding fixed waits, network triggers, DnD, shard/retry setup on GitHub Actions, and more. Use when writing, reviewing, or configuring CI for Playwright tests.

  • Tdd

    vincendiary/agents/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 17 other repositories

  • Api contract testing

    agent-packs/registry/skills/api-contract-testing Skill

    no license0★ repo

    Verify API correctness through contract tests, integration tests, and schema validation. Use when building or consuming REST or GraphQL APIs, or when integrating services that must agree on a shared interface.

  • Browser testing with devtools

    agent-packs/registry/skills/browser-testing-with-devtools Skill

    no license0★ repo

    Use browser and DevTools evidence to verify frontend behavior, inspect runtime state, console logs, network traces, and performance.

  • Load testing

    agent-packs/registry/skills/load-testing Skill

    no license0★ repo

    Design and run load, stress, and soak tests to validate system performance under realistic and peak traffic. Use before major releases, after architecture changes, or when setting SLOs.

  • Test driven development

    agent-packs/registry/skills/test-driven-development Skill

    no license0★ repo

    Drive implementation and bug fixes with red-green-refactor testing discipline. Use when changing behavior or adding logic.

  • Preserve the target

    XyraSinclair/ideonomy/skills/preserve-the-target Skill

    0★ repo

    The universal pre-gate that wraps every other skill. Every cognitive move TRANSFORMS the problem — tests it, reframes it, localizes it, names it, formalizes it, dimensionalizes it, persists it — and the sharpest failure is not that the move is non-executable, it is that the move executes CLEANLY on a transformed target that is no longer the one that mattered. The failure it prevents: gate laundering / high-assurance wrongness — an oracle for the wrong claim, a smallest case that misses the phase transition, an MDL-shorter reframe that dropped a constraint, a coined concept that compresses language but not reality, a mechanism equilibrium under the wrong utility, a coverage denominator that omits the real branch, a ledger that preserves yesterday's wrong frame. Run it before and after any skill that changes the problem.

  • Prove the coverage denominator

    XyraSinclair/ideonomy/skills/prove-the-coverage-denominator Skill

    0★ repo

    Whenever you are tempted to say "done", "complete", "fully reviewed", "all sources covered", or "the migration is comprehensive", force the denominator into the open first. State the full space of cases, sources, branches, or entities under discussion, then label every element. The failure it prevents: declaring exhaustiveness because the largest or easiest visible case landed while the rest of the denominator stayed implicit and therefore unjudged. Triggers on audits, corpus ingestion, test coverage, literature reviews, source enumeration, and any completeness claim that could hide an unlabeled remainder.

  • Heading inflation

    Mike-Jenkins-Org/skill-testing/eval/tests/fixtures/heading-inflation Skill

    0★ repo

    Counts widget fixture scenarios for coverage. Use when the user asks to count fixture scenarios, audit tests.md coverage, or verify scenario headings.

  • Stale tests

    Mike-Jenkins-Org/skill-testing/eval/tests/fixtures/stale-tests Skill

    0★ repo

    Refreshes widget fixture baselines on demand. Use when the user asks to refresh fixture baselines, re-verify widget scenarios, or rebaseline gizmo outputs.

  • Test suite forge

    vishnujchandran/.agents/skills/test-suite-forge Skill

    no license0★ repo

    Production-grade test suite engineering skill that designs and builds stack-aware unit, integration, contract, and end-to-end tests with CI gates, flake controls, and risk-weighted coverage targets.

  • Palace walk

    frankxai/mind-palace-agent-skills/skills/palace-walk Skill

    0★ repo

    Walk the palace from memory to self-test recall, score it, and repair weak loci. Use when the user says "test me on my palace", "let me recall the list", "walk my palace", "quiz me", or after a palace is built or due for review. Runs retrieval practice (the testing effect), marks which loci held and which failed, and updates the recall block of palace.json.

  • Browser test

    TheophilusChinomona/idev/skills/browser-test Skill

    0★ repo

    Code-as-action browser testing: verify UI changes and user flows by writing re-runnable Playwright scripts, capturing screenshots/console/network evidence, and producing test reports. Use when verifying a web feature in a real browser, reproducing a UI bug, smoke-testing a flow after changes, or asked to test the site / run browser tests.

  • Test map

    TheophilusChinomona/idev/skills/test-map Skill

    0★ repo

    Claude Code plugin: token-optimized dev workflow — cached project context, pattern scanners, build & wiring verification, session persistence, self-review. 23 skills, 3 agents, 4 commands.

  • Test driven development

    g-shevchenko/agentic-quality-skills/skills/test-driven-development Skill

    0★ repo

    Use when implementing a behavior change, fixing a bug, writing tests, or when the user says use test driven development, use TDD, test first, failing test first, verify red, iron law, fail-to-pass, lock tests, test immutability, no test relaxation, or frontier-only TDD. Requires a verified failing test before implementation, forbids weakening existing tests, and routes strict TDD implementers to frontier-class models.

  • Tdd

    Neznakometz/StackForge/core/skills/tdd Skill

    0★ repo

    The mandatory order for writing code with tests. Apply whenever writing business logic.

  • Flutter testing

    Neznakometz/StackForge/mobile/skills/flutter-testing Skill

    0★ repo

    Testing Flutter + Riverpod 3 — unit/widget/golden, ProviderContainer.test, provider overrides, mocktail. Apply when writing or reviewing tests in a Flutter project.

  • Ai regression testing

    goharabbas321/zeoel/skills/ai-regression-testing Skill

    no license0★ 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.

    The same file is in 6 other repositories

  • Django tdd

    goharabbas321/zeoel/skills/django-tdd Skill

    no license0★ repo

    Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.

    The same file is in 8 other repositories

  • E2e testing

    goharabbas321/zeoel/skills/e2e-testing Skill

    no license0★ repo

    Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.

    The same file is in 9 other repositories

  • Golang testing

    goharabbas321/zeoel/skills/golang-testing Skill

    no license0★ repo

    Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.

    The same file is in 8 other repositories

  • Laravel tdd

    goharabbas321/zeoel/skills/laravel-tdd Skill

    no license0★ repo

    Test-driven development for Laravel with PHPUnit and Pest, factories, database testing, fakes, and coverage targets.

    The same file is in 7 other repositories

  • Laravel verification

    goharabbas321/zeoel/skills/laravel-verification Skill

    no license0★ repo

    Verification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness.

    The same file is in 5 other repositories

  • Python testing

    goharabbas321/zeoel/skills/python-testing Skill

    no license0★ repo

    Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.

    The same file is in 9 other repositories