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

  • Coverage data file under pytest cache

    kjuhwa/skills-hub/skills/build/coverage-data-file-under-pytest-cache Skill

    0★ repo

    Move coverage data files into .pytest_cache/.coverage so pytest-xdist worker fragments (.coverage.<host>.<pid>.<random>) end up inside the already-gitignored cache dir instead of polluting the repo root.

  • Github actions parallel test matrix

    kjuhwa/skills-hub/skills/ci/github-actions-parallel-test-matrix Skill

    0★ repo

    GitHub Actions workflow uses a strategy.matrix over OS × toolchain to run all tests in parallel, with continue-on-error for nightly so unstable toolchains don't block merges.

  • Gstack

    kjuhwa/skills-hub/skills/cli/gstack Skill

    0★ repo

    Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

  • Browse

    kjuhwa/skills-hub/skills/cli/gstack/browse Skill

    0★ repo

    Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence. Use when asked to "open in browser", "test the site", "take a screenshot", or "dogfood this". (gstack)

  • Plan eng review

    kjuhwa/skills-hub/skills/cli/gstack/plan-eng-review Skill

    0★ repo

    Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

  • Qa only

    kjuhwa/skills-hub/skills/cli/gstack/qa-only Skill

    0★ repo

    Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".

  • Qa

    kjuhwa/skills-hub/skills/cli/gstack/qa Skill

    0★ repo

    Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".

  • Playwright inspector codegen

    kjuhwa/skills-hub/skills/debug/playwright-inspector-codegen Skill

    0★ repo

    Enable Playwright Inspector / codegen from a running Java app by setting PWDEBUG env vars before Playwright.create() and exposing an mvn codegen invocation for the user

  • Docker smoke test loop

    kjuhwa/skills-hub/skills/devops/docker-smoke-test-loop Skill

    0★ repo

    Run a one-shot docker container, tail its logs for a readiness sentinel, then fire an integration test against the exposed port - with layered fallbacks when the CLI is unavailable.

  • Make check verification loop

    kjuhwa/skills-hub/skills/devops/make-check-verification-loop Skill

    0★ repo

    Single make check command that runs typecheck + TS tests + Go tests + Playwright E2E for agents and CI, only starting services that aren't already running.

  • Playwright java dockerfile

    kjuhwa/skills-hub/skills/devops/playwright-java-dockerfile Skill

    0★ repo

    Multi-stage Dockerfile that builds a Java/Maven app in a JDK image and runs it on the official Playwright Java runtime image, avoiding manual browser installation

  • Test driven development

    kjuhwa/skills-hub/skills/engineering/test-driven-development Skill

    0★ repo

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

  • Test helpers

    kjuhwa/skills-hub/skills/engineering/test-helpers Skill

    0★ repo

    Generate engine-specific test helper libraries for the project's test suite. Reads existing test patterns and produces tests/helpers/ with assertion utilities, factory functions, and mock objects tailored to the project's systems. Reduces boilerplate in new test files.

  • Test setup

    kjuhwa/skills-hub/skills/engineering/test-setup Skill

    0★ repo

    Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.

  • Jest test file naming test only

    kjuhwa/skills-hub/skills/frontend/jest-test-file-naming-test-only Skill

    0★ repo

    Use .test.ts naming (not .spec.ts) and explicitly import jest globals; .spec.ts is excluded from the runner

  • Localize

    kjuhwa/skills-hub/skills/meta/localize Skill

    0★ repo

    Full localization pipeline: scan for hardcoded strings, extract and manage string tables, validate translations, generate translator briefings, run cultural/sensitivity review, manage VO localization, test RTL/platform requirements, enforce string freeze, and report coverage.

  • Skill improve

    kjuhwa/skills-hub/skills/meta/skill-improve Skill

    0★ repo

    Improve a skill using a test-fix-retest loop. Runs static checks, proposes targeted fixes, rewrites the skill, re-tests, and keeps or reverts based on score change.

  • Skill test

    kjuhwa/skills-hub/skills/meta/skill-test Skill

    0★ repo

    Validate skill files for structural compliance and behavioral correctness. Three modes: static (linter), spec (behavioral), audit (coverage report).

  • Team qa

    kjuhwa/skills-hub/skills/production/team-qa Skill

    0★ repo

    Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.

  • Qa plan

    kjuhwa/skills-hub/skills/qa/qa-plan Skill

    0★ repo

    Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprint begins or when starting a major feature.

  • Regression suite

    kjuhwa/skills-hub/skills/qa/regression-suite Skill

    0★ repo

    Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementing a bug fix or before a release gate.

  • Smoke check

    kjuhwa/skills-hub/skills/qa/smoke-check Skill

    0★ repo

    Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.

  • Soak test

    kjuhwa/skills-hub/skills/qa/soak-test Skill

    0★ repo

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

  • Test evidence review

    kjuhwa/skills-hub/skills/qa/test-evidence-review Skill

    0★ repo

    Quality review of test files and manual evidence documents. Goes beyond existence checks — evaluates assertion coverage, edge case handling, naming conventions, and evidence completeness. Produces ADEQUATE/INCOMPLETE/MISSING verdict per story. Run before QA sign-off or on demand.

  • Test flakiness

    kjuhwa/skills-hub/skills/qa/test-flakiness Skill

    0★ repo

    Detect non-deterministic (flaky) tests by reading CI run logs or test result history. Aggregates pass rates per test, identifies intermittent failures, recommends quarantine or fix, and maintains a flaky test registry. Best run during Polish phase or after multiple CI runs.

  • Migrate to shoehorn

    kjuhwa/skills-hub/skills/refactor/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.

  • Pypi testpypi release coordination

    kjuhwa/skills-hub/skills/release/pypi-testpypi-release-coordination Skill

    0★ repo

    Release pipeline tags python-test-v* for TestPyPI dry runs and python-v* for PyPI; the workflow validates tag-vs-pyproject version, builds wheels, smoke-tests on TestPyPI, then promotes to PyPI.

  • Comprehensive gpu kernel testing harness

    kjuhwa/skills-hub/skills/testing-gpu/comprehensive-gpu-kernel-testing-harness Skill

    0★ repo

    Test GPU kernels by running random-shape sweeps against a FP32 reference, using tolerance-aware diff metrics that account for quantization noise, plus TFLOPS/bandwidth bench.

  • Artifact integration test framework bats

    kjuhwa/skills-hub/skills/testing/artifact-integration-test-framework-bats Skill

    0★ repo

    Validate .deb, .rpm, and AppImage artifacts after build using BATS. Test file existence, permissions, desktop entry syntax, and module-level Node.js behavior (load a script via node -e with an inline preamble that imports the module under test).

  • Browse

    kjuhwa/skills-hub/skills/testing/browse Skill

    0★ repo

    Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence. Use when asked to "open in browser", "test the site", "take a screenshot", or "dogfood this". (gstack)

  • Bun mock module isolation

    kjuhwa/skills-hub/skills/testing/bun-mock-module-isolation Skill

    0★ repo

    Split per-package Bun tests into multiple `bun test` invocations to avoid irreversible `mock.module()` cache pollution.

  • Cross binding feature extraction parity testing

    kjuhwa/skills-hub/skills/testing/cross-binding-feature-extraction-parity-testing Skill

    0★ repo

    Generate reference feature vectors from one canonical implementation, store as JSONL, and assert byte-for-byte equality from every other binding (Rust↔Python↔JS↔Go).

  • Deterministic coverage verification

    kjuhwa/skills-hub/skills/testing/deterministic-coverage-verification Skill

    0★ repo

    Run LLVM-instrumented tests multiple times and verify identical coverage reports — catches compiler/env non-determinism that can mask real bugs.

  • E2e default login helper

    kjuhwa/skills-hub/skills/testing/e2e-default-login-helper Skill

    0★ repo

    Reusable Playwright loginAsDefault helper that authenticates via API (send-code + verify-code), injects the token into localStorage, and navigates to a workspace-scoped URL.

  • Effect ts test integration with vitest

    kjuhwa/skills-hub/skills/testing/effect-ts-test-integration-with-vitest Skill

    0★ repo

    Test effect-based services by composing layers with Vitest, using drain() instead of sleep for deterministic async

  • Gstack qa only

    kjuhwa/skills-hub/skills/testing/gstack-qa-only Skill

    0★ repo

    Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".

  • Gstack qa

    kjuhwa/skills-hub/skills/testing/gstack-qa Skill

    0★ repo

    Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA".

  • Llm integration test failure diagnosis

    kjuhwa/skills-hub/skills/testing/llm-integration-test-failure-diagnosis Skill

    0★ repo

    Wire an LLM-based diagnosis step into your CI for integration-test failures — summarize noisy logs, identify probable root cause, post findings to the code-review/PR UI. Based on Google's Auto-Diagnose system (90%+ accuracy on 71-case study, adopted across 52k tests).

  • Model regression test with csv fixture

    kjuhwa/skills-hub/skills/testing/model-regression-test-with-csv-fixture Skill

    0★ repo

    Lock down a model's deterministic output by committing input+expected-output CSVs and re-running with a generator script when intentionally changing behavior.

  • Playwright api fixtures cleanup

    kjuhwa/skills-hub/skills/testing/playwright-api-fixtures-cleanup Skill

    0★ repo

    Self-contained Playwright E2E tests using a TestApiClient fixture that creates entities over HTTP and tears them down in afterEach — no shared DB seed, no cross-test pollution.

  • Synchronized multi language test data directory

    kjuhwa/skills-hub/skills/testing/synchronized-multi-language-test-data-directory Skill

    0★ repo

    Single tests_data/ tree with one subdir per content type, shared across every language test suite, plus reference outputs and known-failure buckets.

  • Synthetic rca scenario pytest marker

    kjuhwa/skills-hub/skills/testing/synthetic-rca-scenario-pytest-marker Skill

    0★ repo

    Use a custom pytest marker (e.g. "synthetic") to gate non-deterministic LLM-based tests away from CI test-cov, while still enabling them via opt-in pytest -m synthetic and Makefile targets.

  • Tdd

    kjuhwa/skills-hub/skills/testing/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.

  • Test suite validation with env isolation

    kjuhwa/skills-hub/skills/testing/test-suite-validation-with-env-isolation Skill

    0★ repo

    Run test suite with isolated environment (NODE_ENV=test, specific env vars, no bridge)

  • Vitest per package environments

    kjuhwa/skills-hub/skills/testing/vitest-per-package-environments Skill

    0★ repo

    Per-package Vitest configs in a monorepo — node env for logic packages, jsdom env for UI packages, framework-specific mocks only in app packages.

  • Plan eng review

    kjuhwa/skills-hub/skills/workflow/plan-eng-review Skill

    0★ repo

    Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

  • Desktop test with report

    tnagatomi/skills/skills/desktop-test-with-report Skill

    no license0★ repo

    Drive computer-use desktop automation (screenshot + click + type) to exercise the features a pull request changes in a native desktop app, then post an evidence-only findings report back to the PR. Sibling of agent-test-with-report — use THAT one for browser and Electron apps (they expose CDP, so agent-browser drives them); use THIS one for native, non-Chromium apps — Cocoa/SwiftUI/AppKit, Qt, Win32, and native-webview frameworks like Wails or Tauri on macOS (WKWebView), where agent-browser can't attach. Use when the user wants an agent to manually test a desktop-app PR on the real desktop and leave a report, with phrases like "agent-test this desktop app PR", "computer-use test the native app and comment on the PR", "run exploratory testing on the desktop build and post a report". macOS-local and interactive — not a CI gate. Collects evidence (operations, screenshots, findings, unverified scope); never a pass/fail verdict.

  • Ref sp dev playwright cli

    swiftpostlabs/agentic-tools/.agents/skills/ref-sp-dev-playwright-cli Skill

    0★ repo

    Automate browser interactions, test web pages, and work with Playwright tests via the playwright-cli terminal tool. Use when: driving a real browser from the command line (open/goto/click/fill/snapshot), debugging a page's console/network/DOM, running or debugging Playwright tests, recording video or traces of a session, or asking the user for live UI/design feedback.

  • Ref sp py python

    swiftpostlabs/agentic-tools/.agents/skills/ref-sp-py-python Skill

    0★ repo

    Shareable skills and tools for AI agents

  • Swarm forge skill

    fxckcode/skills-kit/skills/swarm-forge-skill Skill

    0★ repo

    Sets up or refines repository AI workflow context across multiple CLI targets and four development patterns: TDD, BDD, ATDD, and SDD. Use when the user says things like "set up this repo for Claude Code", "set up this repo for Codex", "prepare the agent workflow", "add a TDD setup", "make this BDD-friendly", "set up ATDD", "set up spec driven development", or "review this project and scaffold the context files". It inspects the repo, chooses or confirms suitable CLI targets, setup patterns, and one of the four supported development patterns, asks only missing setup questions, runs bundled scaffold scripts when needed, and safely merges into existing project context files.

  • Towow eng test

    floccose-burner9185/wow-harness/reference/towow-snapshot/.claude/skills/towow-eng-test Skill

    0★ repo

    通爻测试与验证专才。负责测试设计、质量验证和协议正确性保障。

  • Bdd

    LuchoC-Dev/agent-kits/skills/bdd Skill

    no license0★ repo

    Disciplina de especificación de comportamiento — definir el comportamiento esperado como escenarios legibles (Given/When/Then) antes de implementar. Trigger cuando el proyecto tiene `bdd` en las disciplinas activas, o el usuario pide "escribir escenarios", "Gherkin", "criterios de aceptación", "Given When Then", o quiere especificar comportamiento antes de codear.

  • Environment setup

    LuchoC-Dev/agent-kits/skills/environment-setup Skill

    no license0★ repo

    Configure and manage development, staging, production, and test environments. Use when setting up environment variables, managing configurations, or separating environments. Handles .env files, .env.test, config management, and environment-specific settings. Always use this skill when the user mentions env files, environment variables, .env.test, test environment config, or wants to separate environments — even if they just ask to "add a test env" or "configure testing variables".

  • Tdd

    LuchoC-Dev/agent-kits/skills/tdd Skill

    no license0★ repo

    Disciplina de ejecución Test-Driven Development — ciclo red → green → refactor. Escribir el test que falla antes que el código que lo hace pasar. Trigger cuando el proyecto tiene `tdd` en las disciplinas activas, o el usuario pide "hacer TDD", "test primero", "red green refactor", o está por implementar lógica con tests.

  • Testing strategy

    LuchoC-Dev/agent-kits/skills/testing-strategy Skill

    no license0★ repo

    Define la estrategia de testing — capas de test (unit, integration, e2e), contract testing entre servicios, estrategia de test data y targets de cobertura. Es estrategia, no metodología test-first (eso vive en el pack implementation). Trigger cuando el usuario quiera "estrategia de testing", "qué probar", "tests de integración", "contract testing", "test data", "cobertura" o necesite cerrar cómo se prueba el backend antes de implementar.

  • Flaky ci forensics

    oceanfsdfsvfdsvs/practical-agent-skills/flaky-ci-forensics Skill

    0★ repo

    Analyze flaky CI/test failures from JUnit XML, test history, and CI logs. Use when a team needs to distinguish true regressions from flakes, estimate rerun cost, choose quarantine versus fix-now actions, or produce a prioritized triage plan for GitHub Actions, CircleCI, Buildkite, Jenkins, Playwright, pytest, Jest, RSpec, Go test, or similar pipelines.

    The same file is in 1 other repository

  • Image analysis

    rbr7/MedClawMini/skills/image-analysis Skill

    0★ repo

    Production-ready microscopy image analysis and quantitative imaging data skill for colony morphometry, cell counting, fluorescence quantification, and statistical analysis of imaging-derived measurements. Processes ImageJ/CellProfiler output (area, circularity, intensity, cell counts), performs Dunnett's test, Cohen's d effect size, power analysis, Shapiro-Wilk normality tests, two-way ANOVA, polynomial regression, natural spline regression with confidence intervals, and comparative morphometry. Supports CSV/TSV measurement tables, multi-channel fluorescence data, colony swarming assays, and neuron counting datasets. Use when analyzing microscopy measurement data, colony area/circularity, cell count statistics, swarming assays, co-culture ratio optimization, or answering questions about imaging-derived quantitative data.

  • Charm tui qa

    peternicholls/Charm-Skills/charm-tui-qa Skill

    0★ repo

    Verify, record, and polish Charm terminal user interfaces with automated and manual terminal UX checks. Use when Codex needs to test Bubble Tea update/view behavior, run Go tests, capture screenshots or videos with VHS, inspect terminal rendering at multiple sizes, validate keyboard-only workflows, accessibility/plain-output paths, error/loading/empty states, or produce completion evidence for Charm CLI/TUI work.

  • Charm wish ssh apps

    peternicholls/Charm-Skills/charm-wish-ssh-apps Skill

    0★ repo

    Build, secure, test, and polish SSH-accessible terminal applications with Charm Wish. Use when Codex needs to serve Bubble Tea apps over SSH, compose Wish middleware, handle SSH key authentication, access control, PTY dimensions, per-session app state, logging middleware, local SSH testing, or deployment guidance for Go SSH apps.

  • Spec driven tdd

    mohammaddaoudfarooqi/agent-engineering-skills/skills/spec-driven-tdd Skill

    0★ repo

    Spec-driven test-driven development for AI coding agents. Transforms ambiguous requests into verified implementations through structured specs, derived tests, and strict TDD. Verifies on two axes: coverage and realism (smoke tier, mock-parity, boundary inventory, phase-end demo). Handles greenfield, brownfield, refactors, and complex bug fixes. Use when the user requests a new feature, module, refactor, API, CLI tool, or system with multiple requirements, edge cases, or unclear specs, or for complex bug fixes needing root cause analysis. Triggers on phrases like "add a feature", "implement", "refactor", "fix this bug", "write tests for", "TDD", "test-first", "spec this out", or "mock parity", and when modifying code with adjacent test files or test config. Also triggers on mentions of edge cases, invariants, acceptance criteria, or EARS. Do NOT use for one-line fixes, cosmetic changes, formatting, renames, dependency bumps, or tasks already fully specified with tests provided.