agentsclimarketplace

Test

10,621 rows, by stacks then stars

1,559 of these skill files have been read, by 1,201 distinct authors, and what they tell an agent counted. What Test authors agree on, and what they forbid

  • Jdbc ctp verify report

    Srltas/claude-skills/jdbc-ctp-verify-report Skill

    0★ repo

    One-shot CUBRID JDBC driver verification + report. Builds the CUBRID JDBC driver, runs the CTP JDBC test suite against CUBRID, diffs pass/fail vs a baseline (a prior run's JSON, CTP result dir, or test-jdbc.xml), classifies broken cases (VerifyError, conversion, broker/env, …), and ALWAYS produces a Korean Word (.docx) 비교 분석 report. Use to verify a JDBC driver change or a Java-version/build-target change (e.g. v50 1.6 vs v52 1.8) end to end. Composes parse_ctp.py + the report skill. Triggers on phrases like 'JDBC 드라이버 검증', 'CTP 돌려', 'ctp jdbc 실행하고 리포트', 'verify the JDBC driver with CTP', 'build driver and run CTP'.

  • Full stack test gate

    NeuralMedic-DE/claude-skills/full-stack-test-gate Skill

    0★ repo

    Test a whole application and prove it works, gated by checks that actually run — the project's own unit/integration/regression suites, then a real browser that boots the app, clicks through every feature flow, screenshots each step, and fails on console errors, uncaught exceptions or failed requests; plus pixel-level visual regression and a crawler that reports which features no test touches. Use when the user wants to test an app end to end, write or run unit / integration / regression tests, set up E2E or Playwright testing, drive the UI and take screenshots, verify a change didn't break anything, add a test gate to CI, or find out what is untested. Triggers: "test the app", "end-to-end", "e2e", "regression test", "unit tests", "Playwright", "screenshot the UI", "click through the app", "smoke test", "QA", "visual regression", "test all features", "does it still work".

  • Rag eval guardrails

    NeuralMedic-DE/claude-skills/rag-eval-guardrails Skill

    0★ repo

    Build a verified eval harness for a RAG/LLM feature plus PII/PHI-leakage guardrails, gated by checks that actually run. Scores a precomputed predictions file (so it runs with ZERO API access) on groundedness, citation validity, retrieval hit@k, answer F1/exact-match, refusal rate, and latency; compares to config thresholds and a baseline to catch regressions; and fails the build on PII/PHI leakage. Use when the user wants to evaluate or regression-test an AI/RAG feature, measure hallucination/groundedness, add an eval gate to CI, or scan prompts/answers/logs for leaked identifiers. Triggers: "RAG evaluation", "LLM eval", "eval harness", "hallucination", "groundedness", "PII/PHI leakage", "guardrails", "regression testing for AI features".

  • Webflow to react

    NeuralMedic-DE/claude-skills/webflow-to-react Skill

    0★ repo

    Convert a Webflow page or site into a pixel-perfect React implementation (Vite or Next.js) with Playwright visual-regression testing as the correctness gate. Use when the user wants to migrate, port, rebuild, clone, or recreate a Webflow design 1:1 in React, move off Webflow, or set up screenshot/visual-diff testing of a rebuilt page against the original. Triggers: "convert Webflow to React", "rebuild this Webflow site in Next.js", "pixel-perfect clone", "visual regression vs the original".

  • Eval set

    robdasi/skills/eval-set Skill

    0★ repo

    Decide whether an automation, agent, or skill actually works, without pretending you run a test suite. Turns the output's contract into a schema, a pre-ship checklist of must-be-true invariants, and a completeness judge with a numeric gate, plus one regression case per bug already found. Use this before you trust a build, before a model upgrade silently breaks it, or before each unattended run. Produces a checks file and stops.

  • React testing

    jaballer/react-claude-skills/react-testing Skill

    0★ repo

    Testing strategy for React apps — when to reach for Playwright (E2E) vs Vitest (unit/component) vs both, the senior testing pyramid for an SPA, Playwright setup with config + webServer + per-spec project structure, Vitest setup with jsdom + Testing Library, a11y-first locators (getByRole, getByLabel, toBeFocused, toHaveAttribute), assertion patterns for aria-pressed/aria-current/role=alert/focus-on-route-change, @axe-core/playwright for automated a11y audits, running against localhost vs deployed URL via env var, what NOT to test, common flakiness sources and fixes. Use whenever the project needs tests added — interview "would you add tests?" question, real production CI, or post-build polish layer. Triggers on "test", "testing", "playwright", "vitest", "jest", "e2e", "end-to-end", "unit test", "component test", "@playwright/test", "@axe-core/playwright", "getByRole", "testing library", "rtl", "smoke test", "ci tests", "test runner".

  • Landing page cro

    SkillMedev/performance-marketing/skills/landing-page-cro Skill

    0★ repo

    Improves an existing landing page's conversion rate through evidence-first CRO - audit heatmaps and recordings, write structured hypotheses, prioritize with ICE scoring, and run one-variable tests to statistical significance. Use when someone asks "why isn't my landing page converting", "audit this page before we scale spend", "which A/B test should we run first", or after a CVR drop or ahead of a paid-traffic push. Do NOT use for writing a new landing page from scratch - use landing-page-copy instead. Do NOT use for auditing the ad accounts sending the traffic - use paid-acquisition-audit instead. Do NOT use for reading the results of a finished experiment - use ab-test-analyzer instead.

    The same file is in 2 other repositories

  • Bun runtime expert

    roedyrustam/claudevibeskills/src/bun-runtime-expert Skill

    no license0★ repo

    Expert skill for the Bun JavaScript/TypeScript runtime. Use whenever the user is building, running, or debugging code with Bun — covering Bun.serve (HTTP server), Bun.sql (PostgreSQL), Bun.s3 (object storage), bun:test (testing), the Bun bundler, and package manager. Trigger on any mention of Bun, bun install, bun run, Bun.serve, Bun.file, Bun.sql, bun:test, or when the user wants a fast Node.js alternative. Also trigger for Bun shell scripting or Bun-specific APIs.

  • Secure fuzz testing

    roedyrustam/claudevibeskills/src/secure-fuzz-testing Skill

    no license0★ repo

    Coverage-guided fuzzing with Atheris, cargo-fuzz, and native Go fuzzing, combined with compilers/sanitizers (ASan, MSan, UBSan) for security validation. Use whenever the user wants to fuzz test code, find memory safety bugs, validate parsers/deserializers against malformed input, or harden security-critical code paths. Trigger on mentions of fuzzing, fuzz testing, AddressSanitizer, libFuzzer, cargo-fuzz, Atheris, go test -fuzz, or security validation of parsing/deserialization logic.

  • Experiment tracking

    SkillMedev/data-science-ml/skills/experiment-tracking Skill

    0★ repo

    Sets up disciplined ML experiment tracking - run logging schemas, artifact versioning, naming conventions, and reproducibility standards - and produces the run-record template a team actually follows. Use when someone asks "how should we track our ML experiments", "why can't we reproduce this result", "how do I set up MLflow or W&B for the team", or is bootstrapping a new ML project. Do NOT use for analyzing product A/B tests - use ab-test-analyzer instead; for monitoring deployed models use data-drift-monitor; for judging whether a trained model is good enough to ship use model-evaluation-report.

    The same file is in 1 other repository

  • Pr review

    aliasunder/agent-plugins/plugins/ship-check/skills/pr-review Skill

    0★ repo

    Plugin marketplace for Claude Code and Claude Cowork — fresh-eyes code review agents, workflow orchestrators, and specialized skills

  • Ship check

    aliasunder/agent-plugins/plugins/ship-check/skills/ship-check Skill

    0★ repo

    Plugin marketplace for Claude Code and Claude Cowork — fresh-eyes code review agents, workflow orchestrators, and specialized skills

  • Test audit

    aliasunder/agent-plugins/plugins/ship-check/skills/test-audit Skill

    0★ repo

    Plugin marketplace for Claude Code and Claude Cowork — fresh-eyes code review agents, workflow orchestrators, and specialized skills

  • Bugfix tdd

    bahadirkisbet/bardak/plugins/bardak/skills/bugfix-tdd Skill

    0★ repo

    Use when fixing any bug, regression, or "it does the wrong thing" report. Not for net-new features (ordinary TDD) or pure behavior-preserving refactors.

  • Testing

    muxammadmamajonov/dot-claude/.claude/skills/testing Skill

    0★ repo

    Use when defining a test strategy, choosing layers, raising meaningful coverage, or fixing flaky suites — write tests with the feature, failing test first for bugs, QA audit before launch.

  • E2e scenario author

    SkillMedev/qa-test-automation/skills/e2e-scenario-author Skill

    0★ repo

    Converts an acceptance criterion or user story into one maintainable Playwright or Cypress end-to-end test that reads like the journey it covers. Use when turning a Given/When/Then acceptance criterion or user story into a browser test, when asked to "write an E2E test for this AC", or when a feature's critical journey (login, checkout, signup) needs a single automated scenario. Do NOT use when writing general Playwright tests, configuring the runner, or fixing existing test flakiness - use playwright-testing or flaky-test-detangler instead.

    The same file is in 1 other repository

  • Flaky test detangler

    SkillMedev/qa-test-automation/skills/flaky-test-detangler Skill

    0★ repo

    Root-causes intermittently failing tests and eliminates the hidden dependency at its source instead of retrying around it. Use when a test passes locally but fails in CI, goes green on a CI re-run, fails roughly one run in ten, or is already tagged "flaky." Do NOT use when the task is to design the fake or stub that replaces a real dependency - use mock-stub-designer instead.

    The same file is in 1 other repository

  • Mock stub designer

    SkillMedev/qa-test-automation/skills/mock-stub-designer Skill

    0★ repo

    Designs the minimal set of test doubles for a unit or integration test and decides, per dependency, whether to stub, fake, spy, mock, or exercise the real thing. Use when someone asks "should I mock this", "how do I test code that calls Stripe or S3 or the clock", "why do our tests pass while production is broken", or when a test touches an HTTP API, payment or email/SMS SDK, database, filesystem, system clock, or randomness. Do NOT use for fabricating valid domain fixture data (a User with defaults, an Order with line items) - use test-data-builder instead; for driving a red-green implementation loop, use tdd-expert.

    The same file is in 1 other repository

  • Mutation test runner

    SkillMedev/qa-test-automation/skills/mutation-test-runner Skill

    0★ repo

    Runs mutation testing on already-covered code and turns each surviving mutant into a specific missing assertion, exposing tests that execute code but verify nothing. Use when line coverage is high yet a bug slipped through, when reviewing a critical module (pricing, permissions, auth, state machines) before release, or when you are asked to run Stryker, PIT, mutmut, or cosmic-ray. Do NOT use when the goal is to find which code paths are untested at all - use coverage-gap-finder instead.

    The same file is in 1 other repository

  • Playwright testing

    SkillMedev/qa-test-automation/skills/playwright-testing Skill

    0★ repo

    Writes and reviews end-to-end Playwright tests that survive UI refactors and never fail on timing - resilient locators, web-first assertions, isolated state, and a flake policy with quarantine rules. Use when someone asks "write a Playwright test for this flow", "why is this e2e test flaky", "how do I wait for this element", "what selector should I use", or is setting up a Playwright suite and CI config. Do NOT use for consumer/provider contract tests of API boundaries - use contract-test-writer instead; for turning product requirements into an e2e scenario inventory before any code - use e2e-scenario-author instead; for systematically diagnosing an already-flaky suite - use flaky-test-detangler instead; for designing reusable test fixtures and factories - use test-data-builder instead.

    The same file is in 1 other repository

  • Tdd expert

    SkillMedev/qa-test-automation/skills/tdd-expert Skill

    0★ repo

    Drive development with strict Red-Green-Refactor discipline - write one failing test, write the minimum code to pass it, refactor on green - including test-list planning and a worked kata cycle. Use when someone asks "write this test-first", "do TDD on this feature", "help me practice red-green-refactor", "write a failing test for this bug", or wants tests to drive a new module's design. Do NOT use for adding tests to existing untested legacy code before a refactor - use characterization-test-writer instead - or for designing shared fixtures and factories - use test-data-builder instead.

    The same file is in 3 other repositories

  • Test data builder

    SkillMedev/qa-test-automation/skills/test-data-builder Skill

    0★ repo

    Builds realistic domain fixtures, factories, and edge-case datasets with the builder pattern and valid defaults, so each test owns exactly the data it asserts on. Use when someone asks "how should I set up test data", "my fixtures broke half the suite", "make a factory for this model", "why is this test flaky only in CI", or a test needs domain objects, seed data, or boundary inputs. Do NOT use when a test needs to fake a network call, database client, clock, or third-party SDK - use mock-stub-designer instead; do NOT use for designing the assertions or test cases themselves - use tdd-expert instead.

    The same file is in 1 other repository

  • Pmo qa auditor

    cody-hutson/pmo-platform/core/skills/pmo-qa-auditor Skill

    no license0★ repo

    Reviews skill outputs against the principal contributor standard. Modes: Single-output review · Cross-output coherence · Evidence audit · Guardrail compliance · Platform health audit · Release-process fitness audit (dated process-audit artifact) · Dev testing (PR + release plan → Stage-7 quality report as PR comment) · Acceptance review (Stage-8 per-criterion AC verdicts) · As-built architecture-conformance audit (delivered-work drift + cross-release fragmentation). Evaluates rigor, accuracy, judgment, and operational value — not formatting. Triggers: "review this output", "audit this", "QA this", "check this against the standard", "is this ready to act on", "quality check this", "is this principal-contributor quality", "dev-test this PR", "run dev testing on PR", "run the DT ladder", "acceptance review this PR", "grade this against the issue AC", "run the release-process fitness audit", "fitness-audit the release pipeline", "as-built architecture-conformance audit."

  • Pmo skill refiner selftest canary

    cody-hutson/pmo-platform/release/skills/pmo-skill-refiner-selftest-canary Skill

    no license0★ repo

    Smoke test for the pmo-skill-refiner factory — produced via the refiner's Create-New workflow during an AC demonstration. Reports the count of skill directories currently present in `release/skills/` and flags any that are missing from the `deploy.sh` per-module skill arrays (`OPERATIONS_SKILLS` / `RELEASE_SKILLS` / `CORE_SKILLS` / `CANARY_SKILLS`). Report-only (no decision-class outputs, no recommendations, no actions). Permanent fixture per ADR-04 (Stage 5 design for ) — functions as an always-on smoke test that detects factory regressions. Use when the user wants to check skill-roster consistency ("check the skill roster", "count tracked skills", "audit skill deployment drift", "verify skills/ folder matches deploy.sh", "are all my skills deployed").

  • Backend test writer

    vipincode/exr-agent-skills/.claude/skills/backend-test-writer Skill

    no license0★ repo

    Agent Skills for building production-grade Express + TypeScript + Mongoose backends with Claude Code

  • Frontend test writer

    vipincode/exr-agent-skills/.claude/skills/frontend-test-writer Skill

    no license0★ repo

    Write tests for frontend Next.js/React code on demand — components, hooks (incl. TanStack Query hooks), Zod schemas, and API-binding behavior. Use this ONLY when the user explicitly asks to test frontend code — "write tests for the products grid", "test the useProductsQuery hook", "add component tests for product-card.tsx", "cover the create-product form", "test this binding". It is a standalone utility, run manually whenever the user wants — never auto-chained from frontend-feature-planner or frontend-module-builder. It reads ARCHITECTURE.md (conventions), MODULE_REGISTRY.md (what to mock vs use), the target file(s), and the FEATURE_PLAN's testing checklist if present, detects the test framework + RTL setup from package.json, and writes matching test files. It never modifies source files and never touches the registry. It is NOT for backend tests (that is backend-test-writer). Frontend / Next.js / React / Vitest+RTL scope only.

  • Karvey test

    MauricioQuezadaHaintech/karvey/plugins/karvey/skills/karvey-test Skill

    0★ repo

    Execute unit tests and E2E tests after implementation. Generates test_plan.md and test_evidence.md with request/response/PASS/FAIL evidence. Triggers include "karvey test", "ejecutar tests", "run tests", "pruebas", "tests", "testing", "evidencias", "evidence".

  • Experiment analysis

    Sidsaladi9/persona-os/plugins/product-manager-os/skills/experiment-analysis Skill

    0★ repo

    Designs and reads A/B tests end to end — a sharp hypothesis, a primary metric plus guardrails, sample size and power, and a frequentist read (significance, confidence interval, practical effect) leading to a clear ship/kill call. Use when you say "design this A/B test," "is this result significant," "how many users do I need," "can we ship this," or "did the experiment win?"

  • Product brainstorm

    Sidsaladi9/persona-os/plugins/product-manager-os/skills/product-brainstorm Skill

    0★ repo

    Use when a PM or knowledge worker wants to think out loud with a sharp sparring partner. Triggers on "brainstorm with me", "be my thinking partner", "stress-test this idea", "explore this problem space", "help me think through", or "challenge my assumptions". Diverges to generate breadth, then pressure-tests and helps converge on a next experiment. (For attacking a finished doc before it ships, use `red-team`; for surfacing an idea's riskiest assumption, use `assumption-test`.)

  • Test scenarios

    Sidsaladi9/persona-os/plugins/product-manager-os/skills/test-scenarios Skill

    0★ repo

    Derives QA test scenarios and acceptance test cases from a spec or user story, covering happy paths, edge cases, error states, data variations, and ML quality-bar/eval cases. Use when you need to "write test cases for this story," "figure out what QA should check," "turn this spec into acceptance criteria," "find the edge cases we're missing," or "design eval cases for this AI feature."

  • Pg mean tests

    Exekiel179/pingouin-psych-stats/skills/pg-mean-tests Skill

    0★ repo

    Run or generate Pingouin code for one-sample, independent, paired, Welch, and corrected pairwise mean comparisons in psychology studies.

  • Qa

    waseemnasir2k26/skynetlabs-all-claude-code/skills/code-quality-and-review/qa Skill

    no license0★ repo

    Systematically QA test a web application. Use when asked to "qa", "QA", "test this site", "find bugs", "dogfood", or review quality. Four modes: diff-aware (automatic on feature branches — analyzes git diff, identifies affected pages, tests them), full (systematic exploration), quick (30-second smoke test), regression (compare against baseline). Produces structured report with health score, screenshots, and repro steps.

  • Browse

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/browse Skill

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

  • Gstack

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/gstack Skill

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

  • Browse

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/gstack/browse Skill

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

  • Plan eng review

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/gstack/plan-eng-review Skill

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

  • Qa

    waseemnasir2k26/skynetlabs-all-claude-code/skills/meta-and-tools/gstack/qa Skill

    no license0★ repo

    Systematically QA test a web application. Use when asked to "qa", "QA", "test this site", "find bugs", "dogfood", or review quality. Four modes: diff-aware (automatic on feature branches — analyzes git diff, identifies affected pages, tests them), full (systematic exploration), quick (30-second smoke test), regression (compare against baseline). Produces structured report with health score, screenshots, and repro steps.

  • Usability test plan

    SkillMedev/ux-research-discovery/skills/usability-test-plan Skill

    0★ repo

    Plans a usability study - research questions, realistic task scenarios with success criteria, metrics (completion rate, time on task, SEQ, SUS), a recruiting screener, and moderated vs. unmoderated guidance. Use when someone says "plan a usability test", "write task scenarios for our prototype", "how many participants do we need", or is about to put an interface or prototype in front of users. Do NOT use for open-ended discovery interview guides - use interview-guide-builder instead; for analyzing quantitative A/B experiments, use ab-test-analyzer.

    The same file is in 1 other repository

  • Funnel analysis

    SkillMedev/data-analyst-toolkit/skills/funnel-analysis Skill

    0★ repo

    Builds conversion funnels from raw event data with drop-off attribution, segment comparison, and significance testing, and delivers a filled funnel table with a diagnosed bottleneck and next action. Use when someone asks "where are users dropping off", "why did checkout conversion fall this week", "build a signup-to-activation funnel", or "is mobile converting worse than desktop". Do NOT use for rewriting page copy or layout to lift a known weak step - use landing-page-cro instead; for decomposing active-user growth into new, retained, resurrected, and churned - use growth-accounting instead; for choosing which events to instrument and which product metrics to track - use product-analytics instead; for designing and reading a controlled experiment - use ab-test-analyzer instead.

    The same file is in 1 other repository

  • Skill tester

    SkillMedev/skill-builder-studio/skills/skill-tester Skill

    0★ repo

    Empirically tests a skill with subagent scenarios to verify it fires on the right prompts, stays silent on the wrong ones, and performs its job when loaded. Use when validating a new or modified SKILL.md before publishing - "test this skill", "does this trigger correctly", "verify the skill works". Do NOT use to statically grade or rewrite skill quality (use skill-auditor) - this runs live behavioral tests.

    The same file is in 1 other repository

  • Test

    valasubramanian-kr/wallet-web-developer/skills/test Skill

    no license0★ repo

    Claude plugin orchestrating spec-to-code automation workflow, enabling developers to leverage Claude Skills for productivity.

  • Webapp testing

    Drvivek34/Skill-Bazaar/testing-qa/webapp-testing Skill

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

  • Nestjs testing

    DIYA73/nestjs-skills/nestjs-testing Skill

    no license0★ repo

    Unit and e2e testing patterns for NestJS services, controllers, and gateways. Use when writing unit tests for a NestJS service or controller, writing e2e tests for API endpoints, or mocking TypeORM repositories or external services.

  • Senior review

    ohugonnot/claude-skills/plugins/senior-review/skills/senior-review Skill

    0★ repo

    Use when the user wants a thorough senior-level fresh-eyes review of changes (working tree, staged, branch, or PR) before merge — bug hunting, security threat-model, design, tests, spec-alignment vs the linked ticket. Research-grounded pipeline: context-first assembly (cross-file call sites, conventions, git history, ticket), objective tool gate, parallel blind reviewers (reviewer ≠ author), verification gate (every critical finding needs a receipt: grep/exec/red test), adversarial refute-panel on critical/uncertain findings only. Optimizes signal/noise over recall: caps nits, explicit what-NOT-to-flag, silence when nothing material. Tiers: --quick / standard / --deep. Flags: --pr N, --base ref, --staged, --ticket N, --security, --fix, --comment, --no-tools. NOT for building features (use feature-loop) nor pure-style lint (CI does that).

  • Manual test cases

    digitaldreams/tuhin/skills/manual-test-cases Skill

    0★ repo

    Write or review manual test cases that a non-technical product owner can execute by following exact click paths. Use whenever the user says "manual test cases", "test cases for product owner", "steps a non-tester can follow", "review the test cases", or asks for human-runnable test documentation. Every named entity is validated against seeders before delivery; ambiguous steps are rejected and rewritten. Output goes to tasks/manual_test_cases.md.

  • Quality audit

    digitaldreams/tuhin/skills/quality-audit Skill

    0★ repo

    Pre-release adversarial QA pass by a brutal critic, two modes. AUDIT mode (default): ranked findings report split into mandatory-fix vs optional, with evidence and repro for every finding, written to tasks/qa_report_{date}.md; may write failing tests to prove top findings. VALIDATE mode: fresh persona verifies a previous report's findings and fixes. Use whenever the user says "quality audit", "brutal critic", "test the software in various ways", "release readiness", "find gaps between features and tests", "invent edge cases", "rockstar tester", "veteran tester", "find bugs before production", or "validate the QA fixes". Fans out subagents for coverage on large scopes.

  • Readability sweep

    digitaldreams/tuhin/skills/readability-sweep Skill

    0★ repo

    Three-pass readability cleanup of application source: remove inline comments, extract cohesive blocks into intent-named private methods, and challenge every class and method name. Use whenever the user says "readability sweep", "no inline comments", "remove comments", "check naming", "make the code readable", "extract private methods", or asks to scan the project for readability violations. Edits allowed. Scope is application source only (not tests/config) unless told otherwise. Runs lint and the full test suite after changes.

  • Epigraphy text structure

    Lx050/rubbing-to-knowledge/skills/epigraphy-text-structure Skill

    no license0★ repo

    Validate qualified epigraphic transcriptions; draft append-only, evidence-linked proposals for punctuation, annotation, character normalization, metadata, people, places, offices, era dates, relations, and ambiguities. Use when structuring a human-reviewed rubbing transcription, a located source-edition transcription, or an explicitly synthetic test fixture without treating OCR, AI suggestions, normalized characters, modern places, calendar conversions, or entity identities as fact.

  • Cisco test

    bradmccloskey/claude-cisco-skills/cisco-test Skill

    0★ repo

    Generate Python scripts that test and validate Cisco network configurations, reachability, and protocol state. Use when the user wants to verify network behavior, run connectivity tests, or validate routing/switching state.

  • Cisco traffic gen

    bradmccloskey/claude-cisco-skills/cisco-traffic-gen Skill

    0★ repo

    Generate Python scripts that create network traffic and load for testing Cisco QoS policies, bandwidth, and network performance. Use when the user wants to generate test traffic, simulate load, validate QoS markings, or stress test network links.

  • Tdd

    lankyjo/lankyjo-core-skills/skills/code/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

  • Test checklist

    DazzleML/dazzle-claude-code-config/dotclaude/skills/test-checklist Skill

    0★ repo

    Produce a hand-runnable human test checklist alongside automated tests. Run after writing automated test suites for a phase/feature that ships user-visible behavior. Creates a markdown doc (public by default in tests/checklists/, or in a project-private location for sensitive content) that a human walks through to verify end-to-end behavior that mocks can't cover -- shell rendering, Windows codepages, real subprocess behavior, interactive prompts, file atomicity under real conditions, config isolation, and other "the mocks say it works but does it REALLY" scenarios.

  • Meta creative engine

    kochellenk-afk/claude-marketing-skills/skills/meta-creative-engine Skill

    0★ repo

    Plan, test, diagnose, and iterate Meta (Facebook and Instagram) paid ad creative for ecommerce and content or creator clients. Creative is the primary performance lever on Meta, so this treats it as a testing and diagnostic system, not a "write me ads" tool. Use whenever the work involves Meta ad creative, whether building a creative test plan or brief, choosing angles, hooks, and formats to test, diagnosing why a Meta ad or account underperforms (weak hook, weak hold, poor CTR, high CPM, rising frequency, fatigue), or scaling and iterating a winning ad. Trigger on Meta ads, Facebook ads, Instagram ads, ad creative testing, hook rate, thumbstop, "why are my Meta ads not converting", "my Facebook ads stopped working", "scale my winning ad", or "refresh fatigued creative". Ecommerce optimizes cost per purchase and ROAS; content clients optimize cost per subscriber, lead, or engaged view. Do NOT use for Google Ads, organic social production (use social-goddess), or account-wide unit economics.

  • Domain testing

    phatnguyen975/functional-test-design/domain-testing Skill

    0★ repo

    Apply this skill whenever you need to design test cases using Domain Testing techniques (Equivalence Partitioning and Boundary Value Analysis). Use when given any input/output specification, business rule, field constraint, API parameter, or functional requirement that involves ranges, sets, formats, or conditions. Triggers include: "design test cases", "write test cases", "identify test data", "EP", "BVA", "equivalence class", "boundary value", "partition", or any request to test a field/function with defined input constraints.

  • Error guessing

    phatnguyen975/functional-test-design/error-guessing Skill

    0★ repo

    Apply this skill whenever you need to design supplementary test cases using Error Guessing — an experience-based test design technique. Use after applying black-box techniques (Domain Testing, Decision Table, State Transition, Use Case Testing) to identify additional high-value test cases targeting defect-prone areas that systematic techniques may miss. Triggers include: "error guessing", "what else should we test", "edge cases", "what could go wrong", "attack the system", "fault attack", "experience-based testing", or any request to supplement an existing test suite with additional risk-based cases. Also use when the tester has domain knowledge, historical defect data, or heuristic intuition about where defects are likely to hide.

  • State transition testing

    phatnguyen975/functional-test-design/state-transition-testing Skill

    0★ repo

    Apply this skill whenever you need to design test cases using State Transition Testing. Use when given requirements describing a system whose behavior depends on its current state AND its history of events — not just the current input alone. Triggers include: "design test cases", "test state machine", "test workflow", "test lifecycle", "state transition", "FSM", or any requirement describing: user authentication flows, account lifecycles, order/transaction workflows, session management, multi-step wizards, embedded system controllers, or any feature where the same event produces different outcomes depending on what happened previously.

  • Use case testing

    phatnguyen975/functional-test-design/use-case-testing Skill

    0★ repo

    Apply this skill whenever you need to design test cases using Use Case Testing — a black-box test design technique that derives test cases from use case specifications. Use when given a use case specification (or equivalent: user story with acceptance criteria, feature with defined actor-system interactions), and the goal is to ensure the system correctly handles all flows: the main success scenario, alternate flows, and exception flows. Triggers include: "design test cases from use case", "test this user story", "test this feature end-to-end", "use case testing", "UC", "actor interaction", "flow testing", or any request to test a feature where behavior is described as a sequence of actor-system interactions leading to a defined goal.

  • Tdd executor

    willianbs/skills/tdd-executor Skill

    0★ repo

    Runs red/green/refactor loops against acceptance criteria and TEST_STRATEGY. Use when practicing TDD or when tests should lead implementation. Emits TDD_SESSION. Never skips red, never refactors on red, never claims green without command evidence.

  • Test strategy designer

    willianbs/skills/test-strategy-designer Skill

    0★ repo

    Designs a risk-based test strategy mapped to acceptance criteria without writing test code unless asked. Use after planning and before or during implementation. Emits TEST_STRATEGY. Never chases 100% coverage or tests implementation details by default.

  • Webapp testing

    Alexxiang2008/awesome-skills-map/skills/第22章网页自动化测试/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.