agentsclimarketplace

Test

10,627 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

  • Core

    jovd83/restassured-skill/core Skill

    3★ repo

    Use when Codex needs to implement, refactor, debug, or extend Rest Assured API tests with JUnit 5, reusable request and response specifications, authentication helpers, DTOs, contract checks, and service-test best practices.

  • Auto sync

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

    3★ repo

    Use when Codex needs to keep Rest Assured API coverage plans, requirements mappings, and test-case documentation synchronized as scenarios are added, removed, or renamed.

  • Generation

    jovd83/restassured-skill/coverage_plan/generation Skill

    3★ repo

    Use when Codex needs to generate a Rest Assured API test coverage plan from approved requirements, OpenAPI or Swagger contracts, WSDL analysis, and explicit scope constraints.

  • Review

    jovd83/restassured-skill/coverage_plan/review Skill

    3★ repo

    Use when Codex needs to present a generated Rest Assured API coverage plan to the user, request explicit approval, and block implementation until the scope is confirmed.

  • Assertion strength report

    jovd83/restassured-skill/documentation/assertion-strength-report Skill

    3★ repo

    Use when Codex needs to assess whether Rest Assured tests are weak, moderate, or strong based on the assertions they make, the amount of API behavior they verify, and whether they go beyond status-code checks.

  • Coverage gap report

    jovd83/restassured-skill/documentation/coverage-gap-report Skill

    3★ repo

    Use when Codex needs to highlight uncovered, partial, drift-only, or weakly covered API areas so humans can prioritize the next Rest Assured work instead of reading the full traceability report.

  • Documentation sync

    jovd83/restassured-skill/documentation/documentation-sync Skill

    3★ repo

    Use when Codex needs to keep Rest Assured narrative documentation synchronized with endpoint traceability, coverage rows, and executable tests across BDD, TDD, plain-text, mixed, or partially documented API suites.

  • Report bundle

    jovd83/restassured-skill/documentation/report-bundle Skill

    3★ repo

    Use when Codex needs to generate or refresh a bundled Rest Assured reporting set, including traceability, contract mismatches, coverage gaps, OpenAPI change impact, assertion strength, and the human-friendly HTML portal, with support for BDD, TDD, plain-text, mixed, or absent narrative documentation.

  • Bdd

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

    3★ repo

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

  • Tdd

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

    3★ repo

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

  • Tests

    jovd83/restassured-skill/documentation/tests Skill

    3★ repo

    Use when Codex needs to add human-readable documentation to Rest Assured automation code, including class purpose, role boundaries, shared specs, and scenario intent.

  • Traceability report

    jovd83/restassured-skill/documentation/traceability-report Skill

    3★ repo

    Use when Codex needs to produce a traceability report that maps API endpoints, methods, operations, coverage rows, Rest Assured tests, and narrative documentation references so humans and later agents can see exactly what is covered across BDD, TDD, plain-text, mixed, or absent documentation.

  • Orchestrator

    jovd83/restassured-skill/orchestrator Skill

    3★ repo

    Use when Codex receives a generic Rest Assured or service-testing request and must route the work into planning, implementation, documentation, execution, CI, virtualization, or test-management flows.

  • Imlazy tdd

    hnikoloski/imlazy/skills/imlazy-tdd Skill

    3★ repo

    Test-Driven Development with built-in completion gate — write failing test, watch it fail, write minimal code to pass, verify with evidence before claiming success

  • Z88dk tooling

    feilipu/8085-skills/.grok/skills/z88dk-tooling Skill

    3★ repo

    How to use z88dk host tools to measure, profile, and diagnose 8085 (and related) code in the z88dk tree: z88dk-ticks timing and debugger, hotspots, map/nm/disassembly, suite tests, A/B library swaps, z88dk-copt peephole rules (and what they mean for hand-written library asm vs compiler output), and common measurement pitfalls. Use when optimising library asm, writing or reviewing sccz80/copt-shaped codegen, explaining benchmark deltas, verifying regressions, running +test -clib=8085, or the user runs /z88dk-tooling.

  • Code ultrareview

    coroboros/agent-skills/skills/code-ultrareview Skill

    3★ repo

    Eight-axis judgment code review for the current diff — Correctness, Simplification, Tests, Documentation, Style, Intent, Design/API, Performance (+ Coherence on metadata changes). Five-phase pipeline scope → deterministic tool battery (npx/uvx-preferred, zero-install for the JS + Python majority) → 8 parallel LLM axis reviewers → Haiku validators on sub-80 findings (verbatim rubric, ≥80 threshold) → synthesis with no-silent-drop + Conventional Comments JSONL. Every report closes with "What I did NOT check" (security → /security-review, runtime perf, flaky detection). Opt-in flags `--verify-build`, `--mutation-test`, `--reconcile`, `--apply-safe`. Public-skill posture — zero auto-install, graceful skip on missing native tools. Invoke before a commit or PR — "review my changes", "deep review", "did I miss anything", "check before I commit", "audit this PR", "drift / gaps / blind spots".

    The same file is in 1 other repository

  • Foo

    coroboros/agent-skills/tests/code-ultrareview/fixtures/classify/skills/skills/foo Skill

    3★ repo

    Fixture skill for repo-kind classifier tests.

  • Tdd skill

    lythos-labs/lythoskill/showcase/2026-05-20-head-skill-self-claim-verification/tdd-skill Skill

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

  • Oracle ai research e2e

    Martin-Hausleitner/martins-awesome-skills/skills/software-development/oracle-ai-research-e2e Skill

    3★ repo

    Use when validating Oracle 0.13 with ai-research-browser, workflow-run, GitHub public-safe proof, local Hermes skill installation, guarded ChatGPT/Gemini browser E2E, or reattach/status/session evidence.

  • Test driven development

    Martin-Hausleitner/martins-awesome-skills/skills/software-development/test-driven-development Skill

    3★ repo

    Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.

    The same file is in 1 other repository

  • Dwi lean

    thienhoc/dwi-by-thienhoc/modules/dwi-lean Skill

    3★ repo

    Keep planning, implementation, and testing proportionate to the actual coding task. Use when work is expanding into speculative architecture, broad exploration, repeated review, or excessive tests. Do not use to skip required safety, migration, release, or acceptance evidence.

  • Dojo

    AndreRatzenberger/dojo/skills/dojo Skill

    3★ repo

    Use when an Agent Skill needs behavioral evaluation, hardening, trigger tuning, isolation auditing, or evidence before release, or when the user explicitly asks to create a skill through Dojo. Runs coverage-scaled baseline and skilled scenarios, pressure-tests discipline skills, holds out graduation cases, checks routing collisions, and records proof under ~/.dojo. Responds to "dojo", "test this skill", "prove this skill works", "skill evals", "harden this SKILL.md", and "why is this skill triggering". Does not own ordinary first-draft skill creation unless Dojo is explicitly requested.

  • Improve

    nbialk/quiver-cli/template/.agents/skills/code/improve Skill

    3★ repo

    Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

    The same file is in 5 other repositories

  • Produce video

    AlexAnsart/demo-studio/skills/produce-video Skill

    3★ repo

    End-to-end production of a narrated, captioned demo video for any web app — chains narration generation (narrate), silent Playwright recording (film-demo, smart zooms + guardrails), and narration sync with burned captions (sync-narration) into one final .mp4. Use when the user asks to produce, make, or film a demo/product/tutorial video end to end, "with voice and subtitles", or "from A to Z".

  • Pentest

    angad-kandhari/deliberate/skills/pentest Skill

    3★ repo

    Penetration-testing discipline for authorized security assessment. Load to audit a codebase or system you own (or are explicitly authorized to test) for vulnerabilities - then fix them with secure. Also covers scoped engagements: red-team exercises, CTFs, bug-bounty targets. Covers confirming authorization and scope first, mapping the attack surface, testing methodically against a threat model, proving findings with safe repro, controlling blast radius, reporting for the defender, and closing the find-fix-confirm loop with secure and verify. This is offensive testing to make systems safer; it is the counterpart to secure (writing safe code).

  • Test

    angad-kandhari/deliberate/skills/test Skill

    3★ repo

    Testing discipline. Load when writing tests, deciding what to test, or auditing a test suite. Covers testing behavior not implementation, picking the right layer, mocking sparingly and honestly, one reason to fail, covering failure paths, staying deterministic, and not chasing coverage.

  • Systematic debugging

    lawzava/megapowers/plugins/megapowers/skills/systematic-debugging Skill

    3★ repo

    Skills, plugins, and hooks that change how coding agents work — Claude Code, Codex, OpenCode, Antigravity. Measured, not vibed.

  • Test driven development

    lawzava/megapowers/plugins/megapowers/skills/test-driven-development Skill

    3★ repo

    Skills, plugins, and hooks that change how coding agents work — Claude Code, Codex, OpenCode, Antigravity. Measured, not vibed.

  • Root cause analysis

    static-var/Keystone/skills/root-cause-analysis Skill

    3★ repo

    Project debugging for a concrete failure in a software or product system. Use for a reproducible or evidence-bearing regression, failing test/build, runtime or integration defect, flake, data corruption, or performance anomaly, or when another Keystone skill needs the cause proven.

  • Tdd

    barlevalon/skills/skills/tdd Skill

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

  • Backend testing

    ironbee-ai/ironbee-devtools-skills/skills/backend-testing Skill

    3★ repo

    Skills for IronBee DevTools MCP/CLI

  • Browser testing

    ironbee-ai/ironbee-devtools-skills/skills/browser-testing Skill

    3★ repo

    Automated browser testing, interaction automation, and form testing. Use when the user needs to test web pages, automate browser interactions, fill forms, test validation, run multi-step wizards, or test login/signup flows.

  • Mobile testing

    ironbee-ai/ironbee-devtools-skills/skills/mobile-testing Skill

    3★ repo

    Automated Android app testing on an emulator — connect to an AVD, drive the UI (tap/swipe/type/keys/deep links), read the UI/accessibility tree, capture screenshots/recordings and logcat, capture/mock/intercept the app's HTTP(S) traffic in-process (Frida OkHttp hook — no proxy/CA, pinning bypassed) and pin a W3C trace id, and verify app state. Use for testing Android apps, mobile UI flows, login/checkout on Android, or emulator-based verification. Emulator only (no physical devices, no iOS); network capture/mocking needs a rootable emulator image. For web pages use browser-testing; for server APIs use backend-testing.

  • Terminal testing

    ironbee-ai/ironbee-devtools-skills/skills/terminal-testing Skill

    3★ repo

    Drive and test interactive terminal programs — shells, language REPLs (python/node/psql), full-screen TUIs (vim/htop/less), SSH sessions, and any CLI that prompts — over a pseudo-terminal (PTY). Use to spawn a program attached to a TTY, type commands and keystrokes, wait for expected output before sending more input, read raw scrollback or the rendered screen, send signals, and assert on output. The platform spawns the process itself (no attaching to a pre-existing external process). For one-shot non-interactive commands prefer `pty run`. For web pages use browser-testing; for server APIs use backend-testing.

  • Visual testing

    ironbee-ai/ironbee-devtools-skills/skills/visual-testing Skill

    3★ repo

    Visual testing, UI verification, and design comparison using screenshots and Figma integration. Use when the user wants to verify UI appearance, compare with Figma designs, test responsive layouts, check for visual regressions, or validate design implementation.

  • Test

    marco-souza/skills/.agents/skills/test Skill

    no license3★ repo

    Guide for writing effective tests using best practices: test pyramid, Arrange-Act-Assert pattern, mocking strategies, and coverage guidelines. Use when the user asks to write tests, improve test coverage, refactor tests, or understand testing best practices. Do NOT use when the user wants to run existing tests without modification, or when the focus is on test infrastructure setup (CI/CD, test frameworks installation).

  • Valid skill

    marco-souza/skills/testdata/valid-skill Skill

    no license3★ repo

    A valid test skill for unit testing. Use when: testing the skills CLI. Do NOT use when: running production workloads.

  • Cargo check

    samhcus/skills/skills/cargo-check Skill

    no license3★ repo

    Run cargo fmt, clippy, and tests on a Rust workspace before committing. Catches format failures that break CI. Triggers on "cargo check", "check rust", "run rust tests", "before I commit rust", "fmt and test", "check the workspace", "is the rust build clean".

  • Test driven dev

    Ow1onp/hermes-agent-skills/skills/build/test-driven-dev Skill

    3★ repo

    Use when implementing logic, fixing bugs, or changing behavior. Enforces strict RED-GREEN-REFACTOR cycle with the test pyramid (80/15/5) and Beyonce Rule — tests before code, always.

  • Code quality guardian

    Ow1onp/hermes-agent-skills/skills/verify/code-quality-guardian Skill

    3★ repo

    Use before merging or committing code. Performs six-axis code quality gating — security, complexity, style, test coverage, documentation, and dependency health. Blocks low-quality code from entering the main branch.

  • Frontend testing

    schalkneethling/claude-toolkit/skills/frontend-testing Skill

    3★ repo

    Write tests that start with acceptance criteria, then add implementation tests for robustness. Use when writing unit tests (Vitest), end-to-end tests (Playwright), visual regression tests, or accessibility tests. Emphasizes user-centric testing, semantic locators, accessibility validation, and the balance between acceptance and implementation testing.

  • Crap index assess

    yarlson/yarstack/plugins/yarstack/skills/crap-index-assess Skill

    3★ repo

    Assess method-level change risk with the Change Risk Anti-Patterns (CRAP) index and recommend focused testing or complexity reduction. Use when a repository configures CRAP measurement, cyclomatic complexity and automated test coverage data are available, or a user asks what CRAP means, how to calculate or interpret it, or how to reduce a CRAP score.

  • Test design

    yarlson/yarstack/plugins/yarstack/skills/test-design Skill

    3★ repo

    Design or write reproducible tests matched to behavioral risk before implementation. Use for product behavior and for engineering tooling and infrastructure only when native checks are insufficient and concrete complexity or failure risk warrants proportionate dedicated tests.

  • Test gap review

    yarlson/yarstack/plugins/yarstack/skills/test-gap-review Skill

    3★ repo

    Review whether existing tests and verification credibly prove a scoped behavior contract. Use during validation when evidence may omit important behavior or provide false confidence.

  • Gap analysis e2e

    uzysjung/uzys-agent-harness/.claude/skills/gap-analysis-e2e Skill

    3★ repo

    Two-mode chained gap analysis. DETECT scans the current service end-to-end through three lenses — north-star alignment, correctness (bugs), and user-perspective (UX) — and enumerates concrete, severity-ranked gaps. Then BENCHMARK researches how reference/benchmark services actually solved each high-ranked gap and PROPOSES a closing approach. Use when the user says any of: "북극성 기준으로 부족한 점", "사용자 관점에서 부족한 점", "다른 벤치마크 서비스는 이 부분을 어떻게 해결했는지", "갭분석", "레퍼런스 서비스랑 비교해서 부족한 점 찾아줘" — or the English equivalents: "gap analysis", "what are we missing vs the ideal/north-star", "benchmark against reference services". Fires for both Korean and English phrasing. NOT for a whole-codebase multi-dimension audit (use ultracode-service-audit) or single-artifact prose review (use multi-persona-review) — this is the narrower gap-vs-benchmark loop.

  • E2e testing

    uzysjung/uzys-agent-harness/templates/skills/e2e-testing Skill

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

  • Gap analysis e2e

    uzysjung/uzys-agent-harness/templates/skills/gap-analysis-e2e Skill

    3★ repo

    Two-mode chained gap analysis. DETECT scans the current service end-to-end through three lenses — north-star alignment, correctness (bugs), and user-perspective (UX) — and enumerates concrete, severity-ranked gaps. Then BENCHMARK researches how reference/benchmark services actually solved each high-ranked gap and PROPOSES a closing approach. Use when the user says any of: "북극성 기준으로 부족한 점", "사용자 관점에서 부족한 점", "다른 벤치마크 서비스는 이 부분을 어떻게 해결했는지", "갭분석", "레퍼런스 서비스랑 비교해서 부족한 점 찾아줘" — or the English equivalents: "gap analysis", "what are we missing vs the ideal/north-star", "benchmark against reference services". Fires for both Korean and English phrasing. NOT for a whole-codebase multi-dimension audit (use ultracode-service-audit) or single-artifact prose review (use multi-persona-review) — this is the narrower gap-vs-benchmark loop.

  • Python testing

    uzysjung/uzys-agent-harness/templates/skills/python-testing Skill

    3★ repo

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

    The same file is in 9 other repositories

  • Ui visual review

    uzysjung/uzys-agent-harness/templates/skills/ui-visual-review Skill

    3★ repo

    Captures screenshots of key UI flows after E2E tests pass, runs an agent-side first-pass diff (regressions, console errors, layout shifts), then surfaces a checklist for the user's final approval. Also owns the browser-launch procedure the `playwright-launch` rule delegates here: use it whenever a browser must be opened for a human to drive or for automated capture — manual E2E checks, UX/fidelity comparison against a reference product, or a one-time OAuth login. Use after E2E tests pass on a UI track (csr-*, ssr-*, full).

  • Debug detective

    JayRHa/AgentSkills/debug-detective Skill

    3★ repo

    Systematically root-causes software bugs using a reproduce → isolate → hypothesize → bisect → verify methodology, replacing guess-and-check debugging with a disciplined, evidence-driven investigation. Use this skill when a user reports a bug, a test is failing intermittently or consistently, behavior differs between environments, a regression appeared after a change, something "used to work" and now doesn't, an error/stack trace needs root-causing, or when asked to "debug", "find the root cause", "figure out why X happens", or "track down" a defect. Triggers include crashes, wrong output, flaky tests, hangs/deadlocks, memory leaks, performance regressions, heisenbugs, and works-on-my-machine problems.

  • Unit test author

    JayRHa/AgentSkills/unit-test-author Skill

    3★ repo

    Writes thorough, maintainable unit tests with comprehensive edge cases, table-driven cases, proper mocking/stubbing, and meaningful coverage across languages and frameworks (pytest, Jest/Vitest, Go testing, JUnit, RSpec, xUnit, Rust). Use this skill when the user asks to "write tests", "add unit tests", "improve coverage", "test this function/class/module", "add edge cases", "mock this dependency", "make these tests table-driven", "test error handling", or wants a test plan before implementing. Covers test naming, AAA structure, fixtures, parametrization, mocking strategy, async tests, property-based testing, and avoiding brittle/flaky tests.

  • Debug mode

    hcaiano/skills/skills/debug-mode Skill

    3★ repo

    Evidence debugging for unresolved bugs. Use when the user says 'diagnose' or 'debug this', or when a bug is flaky, environment-specific, production-only, or its root cause survived a normal reproduction/inspection. Build a feedback loop, collect runtime evidence, and fix only after evidence identifies the cause. Do not use for a compiler/type/lint/test error whose cause is in the output, a review finding that already names cause and fix, an already-proven root cause, or from inside an active debug-mode run.

  • Simba testing

    Ahoo-Wang/skills/plugins/ahoo-simba-skills/skills/simba-testing Skill

    3★ repo

    Guide for testing Simba distributed lock and leader-election code. Use when writing or reviewing tests for MutexContender, SimbaLocker, AbstractScheduler, backend TCK conformance via MutexContendServiceSpec, Redis/JDBC/Zookeeper integration tests, timing-sensitive lock behavior, or new Kotlin assertions in Simba-based code.

    The same file is in 1 other repository

  • Simba

    Ahoo-Wang/skills/plugins/ahoo-simba-skills/skills/simba Skill

    3★ repo

    Guide for using the Simba distributed mutex and leader-election library in JVM projects. Use when creating distributed locks, implementing leader-only work, configuring Simba backends (JDBC/MySQL, Redis, Zookeeper), writing MutexContender or AbstractScheduler subclasses, using SimbaLocker, integrating Simba with Spring Boot, choosing backends, or tuning TTL/transition settings. For test-focused work, use the simba-testing skill as well.

    The same file is in 1 other repository

  • Simba testing

    Ahoo-Wang/skills/sources/Simba/skills/simba-testing Skill

    3★ repo

    Guide for testing Simba distributed lock and leader-election code. Use when writing or reviewing tests for MutexContender, SimbaLocker, AbstractScheduler, backend TCK conformance via MutexContendServiceSpec, Redis/JDBC/Zookeeper integration tests, timing-sensitive lock behavior, or new Kotlin assertions in Simba-based code.

  • Simba

    Ahoo-Wang/skills/sources/Simba/skills/simba Skill

    3★ repo

    Guide for using the Simba distributed mutex and leader-election library in JVM projects. Use when creating distributed locks, implementing leader-only work, configuring Simba backends (JDBC/MySQL, Redis, Zookeeper), writing MutexContender or AbstractScheduler subclasses, using SimbaLocker, integrating Simba with Spring Boot, choosing backends, or tuning TTL/transition settings. For test-focused work, use the simba-testing skill as well.

  • Quarkus testing

    kinhluan/rules-quarkus-skills/.agent-skills/quarkus-testing Skill

    3★ repo

    Comprehensive Quarkus testing expertise covering @QuarkusTest, @InjectMock, Testcontainers, Dev Services, and native image testing. Use for all Quarkus testing questions.

  • Debug and test

    hec-ovi/agentickit/.pilot/skills/debug-and-test Skill

    3★ repo

    Run the workspace locally, the test suite, and the todo example. Covers the pnpm workspace layout, the `agentickit` build pipeline (tsup), the Vitest config, and the most common "why is this not working" symptoms. Use when something's broken or a contributor is trying to reproduce a bug.

  • Test generator

    Nembie/claude-code-skills/skills/test-generator Skill

    3★ repo

    Generate unit and integration tests for API routes, utilities, React components, and hooks. Use when asked to generate tests, write unit tests, create integration tests, add test coverage, or test a component/route/function.

    The same file is in 2 other repositories

  • Pev bootstrap playwright

    myksyut/pev-harness/skills/pev-bootstrap-playwright Skill

    3★ repo

    pev-harness を使うプロジェクトに Playwright を導入する自動 bootstrap skill。 npm install / browser binary / playwright.config.ts template / seed test template / `npx playwright init-agents --loop=claude` (Playwright agents 自動生成) の 5 step を 1 操作で完了する。 pev-e2e-verify skill の Preflight が「未setup」と判定した時に自動的に提案される。