Browse Skills — Page 291
32,501 public skills · showing 29,001–29,100
- 100/100
test-evidence-review
striderZA/OpenCodeGameStudios
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.
- 100/100
test-execution
SteelMorgan/1c-agent-based-dev-framework
Запуск и анализ тестов (Test Execution). Навык учит агента **запускать тесты YaxUnit, анализировать результаты и связывать падения тестов с кодом**.
- 100/100
test-first-bugs
jamditis/claude-skills-journalism
This skill should be used when the user reports a bug, describes unexpected behavior, says something is "broken", "not working", "failing", mentions an "error", "issue", or "problem" in code, or asks to "fix" something. Enforces test-driven bug fixing workflow.
- 100/100
test-fix
liferay/liferay-portal
Resolve a single Liferay test failure end-to-end.
- 100/100
test-fixing
mhattingpete/claude-skills-marketplace
Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.
- 100/100
test-fixing-v2
diegosouzapw/awesome-omni-skills
Test Fixing workflow skill. Use this skill when the user needs Systematically identify and fix all failing tests using smart grouping strategies. Use when explicitly asks to fix tests (\\\"fix these tests\\\", \\\"make tests pass\\\"), reports test failures (\\\"tests are failing\\\", \\\"test suite is broken\\\"), or completes implementation and wants tests passing and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
- 100/100
test-fixing-v3
diegosouzapw/awesome-omni-skills
Test Fixing workflow skill. Use this skill when the user needs Systematically identify and fix all failing tests using smart grouping strategies. Use when explicitly asks to fix tests (\\\"fix these tests\\\", \\\"make tests pass\\\"), reports test failures (\\\"tests are failing\\\", \\\"test suite is broken\\\"), or completes implementation and wants tests passing and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
- 100/100
test-flakiness
striderZA/OpenCodeGameStudios
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.
- 100/100
test-gap-analysis
microsoft/testfx
>-
- 100/100
test-gap-audit
github/awesome-copilot
Run a read-only audit for missing, weak, stale, or mis-scoped test coverage. If the user does not name a scope, audit the full repository and identify important code paths, routes, features, services, workflows, and contracts that lack proper tests. If the user names a feature, PR, branch, route, workflow, service, bug fix, API, security-sensitive path, or risky code change, focus only on that specific scope. Use when the user asks what tests are missing, whether coverage is enough, what regression tests to add, or how to prove a change is safe. This is not a general bug audit and not a security review; it evaluates whether behavior is covered by tests.
- 100/100
test-gen
SethGammon/Citadel
Generate and verify tests — happy path, edge cases, error paths — using the project's own framework and patterns
- 100/100
test-generator
laolaoshiren/claude-code-skills-zh
依据真实代码契约生成并验证单元测试或集成测试。用于用户要求为函数、类、接口或缺陷补测试、提高覆盖率、生成回归用例或完善测试策略时;先读取现有测试与调用方,不猜测空值、异常或超时行为,不自动安装框架或访问生产依赖。
- 100/100
test-helpers
striderZA/OpenCodeGameStudios
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.
- 100/100
test-implement
shinpr/claude-code-workflows
Test implementation patterns and conventions. Use when implementing unit tests, integration tests, or E2E tests, including RTL+Vitest+MSW component testing and Playwright E2E testing.
- 90/100
test-local
microsoft/agent365-skills
>
- 100/100
test-management
microsoft/aspire
Quarantines or disables flaky/problematic tests using the QuarantineTools utility
- 100/100
test-master
Jeffallan/claude-skills
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation frameworks; analyzing coverage gaps; performance testing with k6 or Artillery; security testing with OWASP methods; debugging flaky tests; or working on QA, regression, test automation, quality gates, shift-left testing, or test maintenance.
- 100/100
test-model
pollinations/pollinations
Test any model (text, image, video, audio) locally and via enter integration tests
- 100/100
test-patterns
rohitg00/skillkit
Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end tests; structuring test cases or test suites; applying TDD or BDD practices; working with mocks, stubs, spies, or fakes; improving test coverage or reducing flakiness; or needs guidance on test organization, naming conventions, or assertions in frameworks like Jest, Vitest, pytest, or similar.
- 100/100
test-plan
liferay/liferay-portal
Generate a targeted local test plan for branch changes. Use when the user wants to know which tests to run before merging, asks for a test plan, wants to validate changes locally, or mentions running tests for their branch. This skill analyzes commits on top of master and produces a runnable shell script covering Unit, Integration, Playwright, and Poshi tests within a 20-minute local budget.
- 100/100
test-plan-draft
Significant-Gravitas/skills-catalog
Plan tests for a change from risk, with cases, data, and what stays uncovered.
- 100/100
test-quality
techygarg/lattice
Apply test quality principles when generating or reviewing test code. Enforces Arrange-Act-Assert structure, one behavior per test, assertion quality, test isolation, meaningful naming, and test data management. Use when writing tests, reviewing test code, or when the user mentions 'write tests', 'test this', 'test quality', 'test review', 'improve tests', or 'test structure'. This skill governs the craft of writing individual test cases -- not what to test (that is driven by the code being implemented) but how to write tests that are reliable, readable, and maintainable.
- 90/100
test-quality-inspector
bobmatnyc/claude-mpm-skills
Test quality inspection framework for reviewing test coverage, identifying gaps, and ensuring comprehensive validation
- 100/100
test-reviewer
TestAny-io/testany-agent-skills
Review test design and readiness, 测试评审。Use when: Test Spec/Test Case Package 完成后,需要审查独立测试范围内的覆盖、追溯、执行证据与遗留风险,作为发布准备前的测试门禁。
- 100/100
test-scenarios
phuryn/pm-skills
Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.
- 100/100
test-setup
striderZA/OpenCodeGameStudios
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.
- 100/100
test-site
microsoft/power-platform-skills
>-
- 100/100
test-skill
serpro69/claude-toolbox
A test skill
- 80/100
test-smell-detection
microsoft/testfx
>
- 100/100
test-spec-gen
anombyte93/atlas-session-lifecycle
Universal test specification generator that explores codebases, researches best practices, and generates comprehensive test specs via multi-agent orchestration. Outputs Hermes-style test specification documents with TC-XXX formatting, area segmentation, and optional Trello card conversion.
- 100/100
test-spec-writer
TestAny-io/testany-agent-skills
Write test spec, 测试规格/测试用例包撰写。Use when: LLD 完成且测试策略已确认后,需要产出独立测试范围内完整的 test case package、追溯矩阵与执行说明。
- 100/100
test-strategy-doc
mohitagw15856/pm-claude-skills
Write a test strategy document from a feature spec, PRD, or system description. Use when asked to create a test plan, write a test strategy, define QA approach, or plan testing for a feature or release. Produces a complete test strategy with scope, risk assessment, test types, coverage targets, and a prioritised test case outline.
- 100/100
test-strategy-reviewer
TestAny-io/testany-agent-skills
Review test strategy, 测试策略评审。Use when: 测试策略写完后,需要审查风险覆盖、独立测试分层、阶段化执行规则、环境策略与入口/出口标准是否成立。
- 100/100
test-strategy-writer
TestAny-io/testany-agent-skills
Write test strategy, 测试策略撰写。Use when: PRD、API Contract、HLD 基线明确后,需要定义独立测试范围、独立测试层次、阶段化执行规则、环境策略、入口/出口标准。
- 100/100
test-suite
Kastalien-Research/thoughtbox
Run behavioral smoke tests against the live Thoughtbox Code Mode MCP server. Verifies the public `/mcp` surface (`thoughtbox_search`, `thoughtbox_execute`, `thoughtbox_peer_notebook`) plus the main execution paths behind it.
- 100/100
test-tagging
microsoft/testfx
>
- 100/100
test-the-docs
supabase/supabase
>-
- 100/100
test-triage
openai/plugins
Triage macOS tests across Xcode and SwiftPM. Use when narrowing failures, explaining assertions or crashes, or separating setup from regressions.
- 100/100
test-value-evidence
microsoft/testfx
>-
- 100/100
test-writer
partme-ai/full-stack-skills
"Generates unit, integration, and end-to-end tests using frameworks like pytest, Jest, JUnit, and Playwright. Use when the user needs to write tests for existing code, create test suites for a module, add edge-case coverage, or set up a testing framework from scratch."
- 100/100
test-writing
SteelMorgan/1c-agent-based-dev-framework
Написание тестов YaxUnit (BSL). Навык учит агента создавать тестовые модули для фреймворка YaxUnit — регистрация тестов, утверждения, мокирование, тестовые данные.
- 100/100
testability-obstacle
microsoft/testfx
>-
- 100/100
testany-case
TestAny-io/testany-agent-skills
Testany platform case 注册与 CRUD - 将已准备好的 platform case package 注册到平台,并管理 metadata、脚本与生命周期
- 100/100
testany-case-writing
TestAny-io/testany-agent-skills
Testany platform case 编写助手 - 将传统测试场景拆解为 Testany platform cases,并生成可注册的 case packages
- 100/100
testany-debug
TestAny-io/testany-agent-skills
分析 Testany 测试失败原因 - 排查问题、查看日志、定位根因
- 100/100
testany-execution
TestAny-io/testany-agent-skills
Testany execution 观测与管理 - 查看进度、查询历史、刷新状态、取消未开始执行、将失败执行交给 debug
- 100/100
testany-guide
TestAny-io/testany-agent-skills
Testany 平台核心概念和配置参考
- 100/100
testany-import-git
TestAny-io/testany-agent-skills
Testany Git 导入:把 Git 仓库里的测试脚本批量注册成 Testany platform cases,并持续同步、切 commit、演化 binding、配 webhook
- 100/100
testany-pipeline
TestAny-io/testany-agent-skills
Testany pipeline 编排与 CRUD - 基于 automation design 或现有 case keys 创建执行与编排单元
- 100/100
testany-sync-case-env-from-source
TestAny-io/testany-agent-skills
从 OpenAPI 生成的 Testany case 源代码中自动识别入参和出参,并同步到 case 的环境变量列表中。适用于源代码存储在需要认证的 Git 仓库(如 Bitbucket)的场景。
- 80/100
testany-trigger
TestAny-io/testany-agent-skills
Testany 执行入口与单次触发 - 为 pipeline 配置 Plan、Manual Trigger、Gatekeeper,或立即执行一次
- 100/100
testany-workspace
TestAny-io/testany-agent-skills
管理 Testany 工作空间 - 成员管理、权限配置、团队组织
- 100/100
testcontainers
TerminalSkills/skills
When the user wants to run integration tests with real dependencies using Docker containers managed by Testcontainers. Also use when the user mentions "testcontainers," "integration testing with Docker," "database integration tests," "containerized tests," or "test with real database." For API mocking without containers, see mockoon or wiremock.
- 100/100
testdino-audit
anthropics/claude-plugins-community
Use only when the user explicitly asks for a TestDino audit of Playwright automated test code. Routes through the audit tools the TestDino MCP server exposes (get_audit_report + submit_audit_report, or the legacy test_audit). For generic code review or non-Playwright targets, do a normal review instead.
- 100/100
testdino-health
anthropics/claude-plugins-community
Use when the user wants to check TestDino connection status, validate their PAT, discover available organizations and projects, or find the right projectId. Always call this first when the project context is ambiguous before any other TestDino tool.
- 100/100
testdino-manual-runs
anthropics/claude-plugins-community
Use when the user wants to manage a manual execution run or update case-level results inside a run — listing runs, creating runs for a release, inspecting a run, assigning cases, or marking case results (passed/failed/blocked/skipped/retest/untested). Accepts counter-style IDs like RUN-12 and TC-156.
- 100/100
testdino-manual-tests
anthropics/claude-plugins-community
Use when the user wants to create, update, or browse manual QA test cases and suites in TestDino — not execution runs. Covers list_manual_test_suites, list_manual_test_cases, get_manual_test_case, create_manual_test_case, update_manual_test_case, create_manual_test_suite.
- 100/100
testdino-releases
anthropics/claude-plugins-community
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers list_releases, get_release, create_release, and update_release. Accepts counter-style IDs like MS-12.
- 100/100
testdino-runs
anthropics/claude-plugins-community
Use when the user wants to inspect automated test runs, list failed or flaky tests, debug a failing testcase with historical context, or filter runs by branch, commit, author, environment, browser, status, or tags. Includes list_testruns, get_run_details, list_testcase, get_testcase_details, and debug_testcase.
- 100/100
testdino-sessions
anthropics/claude-plugins-community
Use when the user wants to browse, inspect, create, or update exploratory testing sessions in TestDino — by state, status, session type, assignee, release, or tags. Covers list_sessions, get_session, create_session, and update_session. Accepts counter-style IDs like SES-12.
- 100/100
tester
webiny/webiny-js
Use when running tests. Shows how to run tests for a single package, including OpenSearch (ddb-os) tests when applicable.
- 100/100
tester-breaker
microsoft/amplifier-bundle-skills
>-
- 100/100
testfx-acceptance-validation
microsoft/testfx
Validate TestFx shipping paths and capable CI execution using packed consumers, package/cache provenance, exact exits and artifacts, and selected-versus-executed test evidence. Use for acceptance regressions, package/MSBuild/launcher/protocol changes, or skipped-only CI results; not for unrelated unit-only or documentation changes.
- 100/100
testfx-localization-validation
microsoft/testfx
Validate generated TestFx localization catalogs, resource IDs, placeholders and locked tokens. Use for RESX/XLF changes, OneLoc PRs, localization build failures, duplicate targets or units, and orphaned translation entries.
- 100/100
testfx-parallel-safety-preflight
microsoft/testfx
Check concurrency and isolation before implementing or refactoring TestFx tests, lifecycle code, helpers, shared-state declarations, or production paths those tests exercise. Use before narrowing DoNotParallelize or ResourceLock, changing parallelization settings, or introducing asynchronous workers; repeat against the final diff.
- 100/100
testfx-test-value-evidence
microsoft/testfx
Apply the vendored test-value-evidence skill with TestFx toolchain, assertion, parallel-safety, packed-consumer, and review conventions. Use when implementing or reviewing behavior-changing TestFx PRs or commits, including source-only changes.
- 100/100
testimonial-collector
BrianRWagner/ai-marketing-claude-code-skills
Systematically gather, score, and format client testimonials. Use when someone needs social proof, wants to collect feedback, needs to turn happy clients into public advocates, or asks for help requesting or drafting a testimonial.
- 100/100
testimonials-generator
kostja94/marketing-skills
When the user wants to add, optimize, or design customer testimonials, reviews, or case study sections. Also use when the user mentions "testimonials," "reviews," "customer quotes," "social proof," "case studies," "testimonial section," "customer reviews," "review schema," "testimonial design," or "social proof section." For case studies page, use customer-stories-page-generator.
- 100/100
microsoft/testing
microsoft/vs-threading
Provides guidance and instructions for writing, running and filtering tests.
- 100/100
NVIDIA/testing
NVIDIA/Megatron-LM
Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.
- 100/100
cloudflare/testing
cloudflare/sandbox-sdk
Use when writing or running tests for this project. Covers unit vs E2E test decisions, test file locations, mock patterns, and project-specific testing conventions. (project)
- 100/100
vercel-labs/testing
vercel-labs/fast-link
Write, change, or review Fast Link tests, choose between specs, browser tests, and real app fixtures, or audit and clean up test suites. Use when assessing test value, duplication, reliability, or coverage in this repository.
- 100/100
obra/Testing Anti-Patterns
obra/superpowers-skills
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
- 100/100
Testing Coach
Community-Access/accessibility-agents
Accessibility testing coach for web applications. Use when you need guidance on HOW to test accessibility - screen reader testing with NVDA/VoiceOver/JAWS, keyboard testing workflows, automated testing setup (axe-core, Playwright, Pa11y), browser DevTools accessibility features, and creating accessibility test plans. Does not write product code - teaches and guides testing practices.
- 100/100
Testing Skills With Subagents
obra/superpowers-skills
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
- 100/100
testing-agents-with-subagents
notque/vexjoy-agent
Test agents via subagents: known inputs, captured outputs, verification.
- 100/100
testing-android-intents-for-vulnerabilities
mukul975/Anthropic-Cybersecurity-Skills
>
- 95/100
rohitg00/testing-anti-patterns
rohitg00/skillkit
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or unreliable test failures, or when the user mentions flaky tests, test smells, brittle tests, test isolation issues, mock overuse, slow tests, or test maintenance problems.
- 100/100
microsoft/testing-anti-patterns
microsoft/FluidFramework
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
- 100/100
testing-api-authentication-weaknesses
mukul975/Anthropic-Cybersecurity-Skills
>
- 70/100
testing-api-for-broken-object-level-authorization
mukul975/Anthropic-Cybersecurity-Skills
>
- 100/100
testing-api-for-mass-assignment-vulnerability
mukul975/Anthropic-Cybersecurity-Skills
>
- 35/100
testing-api-security-with-owasp-top-10
mukul975/Anthropic-Cybersecurity-Skills
Systematically assessing REST and GraphQL API endpoints against the OWASP API Security Top 10 risks using automated and manual testing techniques.
- 100/100
testing-best-practices
AsyrafHussin/agent-skills
Unit testing, integration testing, and test-driven development principles. Use when writing tests, reviewing test code, improving test coverage, or setting up testing strategy. Triggers on "write tests", "review tests", "testing best practices", or "TDD".
- 100/100
testing-boss
compozy/agh
Testing doctrine for tests that reveal bugs instead of passing for the wrong reason — spanning software and LLM/AI systems. Use when authoring or reviewing tests, adding a mock, deciding where a test belongs, letting a coding agent generate tests, triaging flaky CI, designing an eval suite for an LLM/agent feature, or rebuilding a brittle suite. Not for general code review, library debugging unrelated to tests, CI pipeline design beyond tests, or production observability.
- 0/100
testing-cors-misconfiguration
mukul975/Anthropic-Cybersecurity-Skills
Identifying and exploiting Cross-Origin Resource Sharing misconfigurations that allow unauthorized cross-domain data access and credential theft during security assessments.
- 100/100
testing-course-samples
microsoft/ai-agents-for-beginners
Use when asked to validate, test, smoke-test, or run the course's notebook and code samples against a live Microsoft Foundry / Azure OpenAI configuration. Covers environment setup (.env, az login, packages), the scripts/validate-notebooks.ps1 runner, interpreting PASS/FAIL results, and which lessons need extra resources (Azure AI Search, GitHub MCP, Foundry Local, Playwright).
- 100/100
testing-dags
astronomer/agents
Complex DAG testing workflows with debugging and fixing cycles. Use for multi-step testing requests like "test this dag and fix it if it fails", "test and debug", "run the pipeline and troubleshoot issues". For simple test requests ("test dag", "run dag"), the airflow entrypoint skill handles it directly. This skill is for iterative test-debug-fix cycles.
- 100/100
testing-data-visualizations
openai/plugins
Test data visualizations and dashboards. Use when the user needs chart or diagram test strategy, screenshot or image diff testing, visual regression, mocked or synthetic chart data, component or unit tests, E2E dashboard QA, interactive UML-like diagram verification, scroll-driven story verification, export verification, or guidance on avoiding brittle over-testing.
- 100/100
testing-e2e
yonatangross/orchestkit
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
- 90/100
testing-ecommerce-and-payment-logic
xalgord/xalgorix
Testing business-logic flaws in e-commerce and payment flows including price/product tampering,
- 100/100
testing-flutter
TheBeardedBearSAS/claude-craft
Testing Flutter 3.44 / BLoC v9 / Riverpod 3 - Stratégie Complète. Use when writing tests, reviewing test coverage, or setting up testing.
- 100/100
testing-for-broken-access-control
mukul975/Anthropic-Cybersecurity-Skills
Systematically testing web applications for broken access control vulnerabilities including privilege escalation, missing function-level checks, and insecure direct object references.
- 100/100
testing-for-business-logic-vulnerabilities
mukul975/Anthropic-Cybersecurity-Skills
Identifying flaws in application business logic that allow price manipulation, workflow bypass, and privilege escalation beyond what technical vulnerability scanners can detect.
- 60/100
testing-for-crlf-injection
xalgord/xalgorix
Testing web applications for CRLF (Carriage Return / Line Feed) injection where unsanitized %0d%0a sequences
- 0/100
testing-for-email-header-injection
mukul975/Anthropic-Cybersecurity-Skills
Test web application email functionality for SMTP header injection vulnerabilities that allow attackers to inject additional email headers, modify recipients, and abuse contact forms for spam relay.
- 0/100
testing-for-host-header-injection
mukul975/Anthropic-Cybersecurity-Skills
Test web applications for HTTP Host header injection vulnerabilities to identify password reset poisoning, web cache poisoning, SSRF, and virtual host routing manipulation risks.
- 80/100
testing-for-json-web-token-vulnerabilities
mukul975/Anthropic-Cybersecurity-Skills
Test JWT implementations for critical vulnerabilities including algorithm confusion, none algorithm bypass, kid parameter injection, and weak secret exploitation to achieve authentication bypass and privilege escalation.
- 0/100
testing-for-open-redirect-vulnerabilities
mukul975/Anthropic-Cybersecurity-Skills
Identify and test open redirect vulnerabilities in web applications by analyzing URL redirection parameters, bypass techniques, and exploitation chains for phishing and token theft.
- 80/100
testing-for-regex-dos-redos
xalgord/xalgorix
Testing web applications for Regular Expression Denial of Service (ReDoS), where crafted input forces a
Page 291 of 326