Test
10,628 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
codingSamss/all-my-ai-needs/platforms/claude/skills/apifox-test-case Skill
no license14★ repoApifox 接口测试用例:test-case 与 test-data 的查询、创建、更新、删除、分类和运行;处理测试步骤、断言、提取变量、前后置处理器、数据集,以及“CLI 创建后前端测试步骤无法展示”等问题。
codingSamss/all-my-ai-needs/platforms/claude/skills/playwright Skill
no license14★ repoUse when the task requires automating a real browser. This skill is MCP-only and uses `playwright-ext` (`@playwright/mcp --extension`) to attach to the browser extension session.
codingSamss/all-my-ai-needs/platforms/codex/skills/apifox-test-case Skill
no license14★ repoApifox 接口测试用例:test-case 与 test-data 的查询、创建、更新、删除、分类和运行;处理测试步骤、断言、提取变量、前后置处理器、数据集,以及“CLI 创建后前端测试步骤无法展示”等问题。
codingSamss/all-my-ai-needs/platforms/codex/skills/playwright Skill
no license14★ repoUse only when the user explicitly asks for Playwright Extension / real-browser debugging, or when HTTP, in-app Browser, and Codex Chrome plugin cannot complete an interaction-heavy workflow. This skill requires manually enabled `playwright-ext` (`@playwright/mcp --extension`).
Mahashwetha/Job-search-email-system-claude/.claude/skills/test-run Skill
14★ repoThis skill should be used when the user wants to manually trigger, test, or run the job search scripts — either the daily job search email or the remote job search email. Triggers on phrases like "run daily jobs", "test the remote search", "trigger the job email", "run it manually", "send the job digest now", "test remote job search".
Amey-Thakur/AI-SKILLS/skills/accessibility/screen-reader-testing Skill
14★ repoTest with real screen readers, verifying announcements, live regions, and navigation, not just automated checks. Use when validating accessibility of UI that automated tools cannot fully assess.
Amey-Thakur/AI-SKILLS/skills/big-tech-roles/qa-engineer-role Skill
14★ repoOperate as a QA engineer who owns test strategy, automation coverage, and the release quality signal. Use when asked to build a test approach, decide what to automate, or give a defensible go or no-go on a release.
Amey-Thakur/AI-SKILLS/skills/code-quality/assertion-density Skill
14★ repoPlace assertions where invariants are established or must hold: constructors, public boundaries, and loop bodies. Use when hardening code whose silent violations would otherwise surface far from their cause.
Amey-Thakur/AI-SKILLS/skills/debugging/flaky-test-diagnosis Skill
14★ repoTurn a test that fails at random into one that fails on demand by controlling the seed, order, and clock. Use when a test passes on re-run, fails only in CI, or blocks a merge for reasons no one can reproduce.
Amey-Thakur/AI-SKILLS/skills/machine-learning/train-test-discipline Skill
14★ repoSplit data before looking at it, respect time and groups, and quarantine the test set so scores mean something. Use when setting up ML evaluation or auditing why offline metrics did not survive production.
Amey-Thakur/AI-SKILLS/skills/product-management/ab-test-design Skill
14★ repoDesign product experiments with real hypotheses, honest sample-size math, guardrails, and peeking discipline. Use when validating a change by experiment or reviewing a test before believing its result.
Amey-Thakur/AI-SKILLS/skills/python/pytest-mastery Skill
14★ repoStructure pytest suites with fixtures, parametrize, and markers so tests stay fast, isolated, and readable. Use when writing Python tests or untangling a slow, fixture-heavy suite.
Amey-Thakur/AI-SKILLS/skills/security/penetration-test-prep Skill
14★ repoPrepare for a penetration test by fixing scope, rules, and access up front, then turn its findings into tracked, verified remediation. Use when commissioning an external pentest or acting on the report one delivered.
Amey-Thakur/AI-SKILLS/skills/testing/api-testing Skill
14★ repoTest an HTTP API at its boundary so status codes, response schemas, error bodies, and auth paths all hold under real requests. Use when adding or reviewing tests for a service that other clients call over HTTP.
Amey-Thakur/AI-SKILLS/skills/testing/approval-testing Skill
14★ repoAssert hard-to-specify output by reviewing a human-readable snapshot once, approving it, then failing on any later diff. Use when the correct result is easy to recognize but tedious to write as explicit assertions.
Amey-Thakur/AI-SKILLS/skills/testing/assertion-libraries Skill
14★ repoPick an assertion style and write checks that fail with a message you can diagnose without a debugger. Use when test failures read as "expected true, got false" and you cannot tell what actually broke.
Amey-Thakur/AI-SKILLS/skills/testing/bdd-scenarios Skill
14★ repoWrite given-when-then scenarios in domain language so stakeholders can read and confirm the behavior each test protects. Use when drafting acceptance criteria or Gherkin features for a user-facing rule.
Amey-Thakur/AI-SKILLS/skills/testing/browser-matrix Skill
14★ repoChoose which browsers, versions, and devices to test from real usage data instead of habit or a vendor's full grid. Use when cross-browser testing time or budget is finite and the matrix needs to reflect who actually visits.
Amey-Thakur/AI-SKILLS/skills/testing/chaos-testing Skill
14★ repoInject failures like killed instances and network latency on purpose to verify a system degrades gracefully instead of collapsing. Use when validating the resilience of a distributed system that claims to tolerate faults.
Amey-Thakur/AI-SKILLS/skills/testing/concurrency-testing Skill
14★ repoForce the thread interleavings that expose races by using barriers, stress loops, and linearizability checks instead of hoping the scheduler hits them. Use when testing locks, shared state, or lock-free code where a bug appears once in a thousand runs.
Amey-Thakur/AI-SKILLS/skills/testing/contract-testing Skill
14★ repoVerify a service boundary with a consumer-driven contract that records the payload the caller actually reads and that both sides check in CI. Use when two services deploy independently and an unannounced response change would silently break the consumer.
Amey-Thakur/AI-SKILLS/skills/testing/coverage-strategy Skill
14★ repoRead coverage as a map of untested risk that steers the next test, rather than enforcing a percentage target. Use when deciding what to test next or when a team is tempted to mandate a coverage number.
Amey-Thakur/AI-SKILLS/skills/testing/database-testing Skill
14★ repoExercise data-access code, migrations, and transactions against the real database engine so constraints, rollbacks, and schema changes are proven rather than assumed. Use when tests for queries or migrations run on SQLite while production runs Postgres.
Amey-Thakur/AI-SKILLS/skills/testing/e2e-testing Skill
14★ repoWrite end-to-end tests that earn their cost by covering complete user journeys against stable selectors. Use when protecting a critical path like signup or checkout across the full stack.
Amey-Thakur/AI-SKILLS/skills/testing/exploratory-testing Skill
14★ repoRun structured unscripted testing with charters, tours, and timeboxed sessions to find bugs scripted tests never imagined. Use when probing a new or risky feature for problems no one thought to write a test for.
Amey-Thakur/AI-SKILLS/skills/testing/fuzz-testing Skill
14★ repoFuzz a parser or protocol handler with a coverage-guided fuzzer, seed the corpus with real inputs, and triage crashes to unique root causes. Use when code consumes untrusted or complex bytes and hand-written cases cannot reach the states that break it.
Amey-Thakur/AI-SKILLS/skills/testing/integration-testing Skill
14★ repoTest the seams between modules with real dependencies where they are cheap and containerized ones where they are not. Use when verifying that components wired together honor the contracts unit tests assume in isolation.
Amey-Thakur/AI-SKILLS/skills/testing/load-testing Skill
14★ repoSimulate realistic multi-user load with ramp profiles, think time, and pacing, then find where the system saturates. Use when validating capacity or headroom for a service before a launch or expected traffic spike.
Amey-Thakur/AI-SKILLS/skills/testing/mocking-time Skill
14★ repoControl the clock in tests through an injectable time source so "now" is frozen and timezone behavior is explicit. Use when code reads the wall clock and a flaky or time-dependent test needs deterministic results.
Amey-Thakur/AI-SKILLS/skills/testing/mutation-testing Skill
14★ repoMeasure how strong a test suite is by mutating the code and checking the tests notice, exposing assertions that never actually fail. Use when coverage is high but you doubt the tests would catch a real regression.
Amey-Thakur/AI-SKILLS/skills/testing/performance-testing Skill
14★ repoBenchmark code so the numbers mean something: warm up, fix inputs, report variance, and gate regressions in CI. Use when measuring the speed of a function or comparing two implementations.
Amey-Thakur/AI-SKILLS/skills/testing/property-based-testing Skill
14★ repoGenerate many inputs to test invariants that must hold across a whole domain, and let shrinking reduce failures to a minimal case. Use when a rule should hold for all inputs, not just the few examples you would think to write.
Amey-Thakur/AI-SKILLS/skills/testing/regression-tests Skill
14★ repoPin every fixed bug with a test that fails before the fix and passes after, kept beside the code it guards. Use when closing a bug so the same defect cannot return silently through a later refactor or merge.
Amey-Thakur/AI-SKILLS/skills/testing/seed-data-management Skill
14★ repoVersion and share seed datasets so they stay small, realistic, and reproducible across a team. Use when tests or local environments depend on fixture data that is drifting, ballooning, or diverging between developers.
Amey-Thakur/AI-SKILLS/skills/testing/smoke-tests Skill
14★ repoDefine the short, stable suite of critical-path checks that runs after every deploy and blocks promotion the instant it fails. Use when a deploy has no fast gate and breakage is found by users instead of the pipeline.
Amey-Thakur/AI-SKILLS/skills/testing/snapshot-testing Skill
14★ repoUse snapshot tests for serialized output only, with disciplined review of every diff and hard limits on snapshot size. Use when pinning stable rendered output like markup or an API response shape.
Amey-Thakur/AI-SKILLS/skills/testing/tdd-rhythm Skill
14★ repoRun red-green-refactor honestly with the smallest failing test first, refusing test-after backfill dressed up as TDD. Use when building code with a clear behavioral spec and you want the tests to drive the design.
Amey-Thakur/AI-SKILLS/skills/testing/test-data-builders Skill
14★ repoConstruct test objects through builders and factories with valid defaults so each test states only the fields it cares about. Use when shared fixture files couple unrelated tests and drift as the schema grows.
Amey-Thakur/AI-SKILLS/skills/testing/test-doubles Skill
14★ repoChoose stubs, fakes, and mocks deliberately and default to verifying state over interaction so tests survive refactors. Use when a test needs to stand in for a slow, external, or nondeterministic dependency.
Amey-Thakur/AI-SKILLS/skills/testing/test-environment-parity Skill
14★ repoClose the gaps between test and production by matching versions, data shape, and configuration paths so a passing suite actually predicts prod behavior. Use when tests are green but production breaks in ways staging never showed.
Amey-Thakur/AI-SKILLS/skills/testing/test-flakiness-budget Skill
14★ repoCap flaky tests with a measured budget, quarantine them off the merge gate, and burn them down under named owners and deadlines. Use when re-runs are how the team gets green and no one owns the flakes.
Amey-Thakur/AI-SKILLS/skills/testing/test-isolation Skill
14★ repoMake tests order-independent by resetting state, banning shared globals, and giving each worker its own resources. Use when tests pass in one order but fail when reordered, sharded, or run in parallel.
Amey-Thakur/AI-SKILLS/skills/testing/test-maintenance Skill
14★ repoRefactor test code with the same care as production: extract helpers, remove duplication, and delete tests that no longer earn their place. Use when the test suite has become slow to change, repetitive, or full of tests nobody trusts.
Amey-Thakur/AI-SKILLS/skills/testing/test-naming Skill
14★ repoName tests as full behavior sentences so the suite reads as a specification of what the system guarantees. Use when naming a new test or renaming vague tests like test1 or testWorks.
Amey-Thakur/AI-SKILLS/skills/testing/test-pyramid-audit Skill
14★ repoRebalance a top-heavy test suite toward fast unit tests without dropping the coverage the slow tests provide. Use when end-to-end tests dominate the suite and CI is slow, flaky, or expensive to run.
Amey-Thakur/AI-SKILLS/skills/testing/test-review Skill
14★ repoReview tests with the same rigor as production code, checking that assertions truly constrain behavior, that error and edge cases exist, and that no safety was quietly deleted. Use when reviewing a pull request that adds, changes, or removes tests.
Amey-Thakur/AI-SKILLS/skills/testing/test-speed Skill
14★ repoKeep the suite fast enough to run on every change by measuring the slow tests, shaping the pyramid, cutting IO from the fast tier, and sharding. Use when the suite is slow enough that developers skip it or batch changes to avoid the wait.
Amey-Thakur/AI-SKILLS/skills/testing/test-tagging Skill
14★ repoTag tests by speed and scope so CI can run the right slice at the right time. Use when the suite is one undifferentiated blob and you need fast feedback on pull requests without dropping slow coverage.
Amey-Thakur/AI-SKILLS/skills/testing/testing-in-production Skill
14★ repoVerify changes against real traffic without risking users, using canaries, shadow traffic, and feature gates with automatic rollback. Use when a behavior cannot be trusted from staging alone and needs production load or data to prove out.
Amey-Thakur/AI-SKILLS/skills/testing/testing-strategy Skill
14★ repoDecide what to test, at which level, and what to skip, so tests catch real regressions without freezing the design. Use when writing tests or planning coverage for a change.
Amey-Thakur/AI-SKILLS/skills/testing/unit-test-design Skill
14★ repoWrite unit tests that document behavior through explicit arrange-act-assert phases and a single assertion of intent. Use when writing or repairing a unit test that has grown hard to read.
Amey-Thakur/AI-SKILLS/skills/testing/visual-regression-testing Skill
14★ repoCatch unintended UI changes by diffing rendered screenshots against approved baselines with tuned thresholds and flake control. Use when protecting a component or page from visual drift across code changes.
Amey-Thakur/AI-SKILLS/skills/ui-ux/usability-testing Skill
14★ repoWatch real users attempt real tasks to find where a design fails, with few participants and honest tasks. Use when validating a design or diagnosing why users struggle, before or after building.
ngocsangyem/MeowKit/.claude/skills/ask-me Skill
14★ repoUse when answering factual or explanatory questions about the current project — codebase, architecture, conventions, workflows, constraints — with minimal cited evidence. Triggers on "how does X work here", "what does X mean", "why is X structured this way", "is this claim true in the repo", "explain X with sources". NOT for brainstorming or comparing approaches (mk:brainstorming), trade-off decisions (mk:party), debugging/root cause (mk:investigate), code review (mk:review), plans (mk:plan-creator), security audits (mk:cso), visual explanations/diagrams (mk:preview --explain), test-coverage gaps (mk:nyquist), library docs (mk:docs-finder), or workflow navigation (mk:help).
ngocsangyem/MeowKit/.claude/skills/lint-and-validate Skill
14★ repoAutomatic quality control, linting, and static analysis after code modifications. Triggers on: lint, format, check, validate, types, static analysis. NOT for full build verification (see mk:verify); NOT for test coverage (see mk:testing).
ngocsangyem/MeowKit/.claude/skills/nyquist Skill
14★ repoTest-to-requirement coverage mapping. Reads plan acceptance criteria and test files, produces a coverage gap report showing which requirements have no tests. Use during Phase 2 (Test) or Phase 4 (Review) to verify test completeness. Named after the Nyquist sampling theorem — sufficient test coverage prevents aliased (missed) requirements. NOT for running tests (see mk:testing); NOT for structural code review (see mk:review).
ngocsangyem/MeowKit/.claude/skills/playwright-cli Skill
14★ repoSession-persistent browser automation via Playwright CLI — form filling, screenshots, data extraction, multi-step flows. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information across multiple requests. NOT for AI-driven long-autonomous flows (see mk:agent-browser); NOT for generating .spec.ts E2E code (see mk:qa-manual).
ngocsangyem/MeowKit/.claude/skills/qa-manual Skill
14★ repoSpec-driven manual QA testing and Playwright E2E code generation. Orchestrates browser skills to navigate apps like a human tester, producing structured test reports or production-ready .spec.ts files. Always prompts user for credentials — never guesses or stores auth. Use for QA testing, E2E generation, login flow testing, or exploratory testing from a URL. NOT for AI-autonomous flows (see mk:agent-browser).
ngocsangyem/MeowKit/.claude/skills/qa Skill
14★ repoSystematically 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.
ngocsangyem/MeowKit/.claude/skills/testing Skill
14★ repoUse when writing tests, running validation scripts, or (in TDD mode) enforcing red-green-refactor cycle. Activates during Phase 2 (Test) and Phase 3 (Build). NOT for coverage gap mapping (see mk:nyquist); NOT for sprint contract negotiation (see mk:sprint-contract).