Test
10,683 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
AlterLab-IEU/AlterLab_GameForge/skills/agents/game-qa-lead Skill
26★ repoInvoke when the user asks about testing strategy, bug tracking, playtest methodology, regression testing, release certification, QA automation, or bug triage. Triggers on: "testing", "bug", "QA", "regression", "certification", "playtest methodology", "test plan", "release gate". Do NOT invoke for usability testing (use game-ux-designer) or balance validation (use game-balance-check). Part of the AlterLab GameForge collection.
AlterLab-IEU/AlterLab_GameForge/skills/workflows/game-playtest Skill
26★ repoInvoke when the user wants to plan, execute, or analyze a structured playtest session with behavioral observation. Covers protocol design, observer guides, and data synthesis. Triggers on: "playtest", "player feedback", "usability test", "observation session", "playtest analysis". Do NOT invoke for QA bug testing (use game-qa-lead) or balance tuning (use game-balance-check). Part of the AlterLab GameForge collection.
api-platform/skillset/skills/api-test Skill
no license26★ repoWrites functional tests for API Platform endpoints with ApiTestCase. Use whenever the user asks to test an API resource, write or fix a functional test, verify validation, security or multi-tenant isolation, set up authentication or database fixtures for tests, or reproduce an endpoint bug with a test — including plain 'add tests for X' requests.
ptsilivis/autonomousguy/skills/change-management/change-and-impact Skill
26★ repoChange-management expert that operates in two modes: (1) CR analysis — take a change request / ECN / feature brief and produce affected-element list, ASIL impact, implementation plan with owner hints and complexity, test plan delta, and integration risks; (2) Impact analysis — trace a specific change through every layer (SWCs, BSW modules, ARXML interfaces, requirements, tests, safety artefacts), distinguishing direct impacts (must change) from indirect impacts (must review or retest), and recommend a regression scope (Minimal / Targeted / Full). Applies ASPICE SWE.6 and ISO 26262-6 §7.4 / -8 §8.4 change practices. Traces the full ripple in a single pass, returns a decision-ready plan/scope with a built-in self-check and explicit confidence/gaps, and can optionally emit a self-contained HTML report under analysis/.
ptsilivis/autonomousguy/skills/requirements/requirements Skill
26★ repoRequirements-engineering expert that operates in three modes: (1) Elicitation — extract atomic, testable requirements from briefs, meeting notes, or system specs using EARS notation, with full attribute set (ID, type, priority, ASIL, verification method, source), flagging ambiguities as open questions; (2) Refinement — detect requirement defects (vague qualifiers, compound statements, implementation prescription, untestability, missing attributes) and rewrite each as a specific, measurable, EARS-formatted statement with documented assumptions; (3) Traceability — build bidirectional matrices (SYS-REQ → SW-REQ → design → test), detect orphaned requirements / design elements / tests, and flag safety gaps where ASIL-tagged requirements have no test coverage (ISO 26262-6 §9 violation). Aligned with EARS, SMART, ISO 26262-6, and ASPICE SWE.1/SWE.6 practices. Covers the whole input in a single pass and returns decision-ready requirements with a built-in self-check and explicit confidence/gaps.
ptsilivis/autonomousguy/skills/testing/embedded-testing Skill
26★ repoEmbedded test-design expert that operates in two modes: (1) Unit-test generation — analyse a C function for decisions and conditions, produce test cases achieving MC/DC coverage (required for ASIL-C/D), add boundary and error-path tests, provide RTE/BSW stub declarations, and output a coverage matrix; (2) Boundary value analysis — compute MIN, MIN+1, nominal, MAX-1, MAX, and out-of-range points for every typed numeric parameter (uint8/sint8/uint16/sint16/uint32/sint32 and fixed-point), and identify overflow, wrap-around, truncation, and sign-extension risks with triggering inputs and safe fixes. Test output is compatible with Unity, CppUTest, and VectorCAST patterns. A third use, characterization testing, pins the existing behaviour of legacy code before a modernization step so equivalence can be proven after the change. Returns decision-ready, self-checked test sets with explicit coverage gaps stated.
byerlikaya/claude-starter-kit/claude-starter/skills/testing Skill
26★ repoEnterprise engineering workflow for Claude Code — not just prompts. AI agents that plan, build, audit, and ship with security gates, privacy checks, and approval-controlled commits. Safely adopt it into new or existing repositories.
byerlikaya/claude-starter-kit/plugin/skills/testing Skill
26★ repoThe how of testing: pyramid, AAA, isolation, risk coverage, determinism. Guarantees the DoD's "tests are green". test-expert-csk applies it. Trigger phrases: "write a test", "run the tests", "coverage", "are the tests green", "unit test", "integration test"
upex-galaxy/agentic-qa-boilerplate/.claude/skills/framework-development Skill
26★ repoFramework evolution mode — evolves the QA boilerplate itself (KATA, fixtures, cli/, scripts/, api/schemas/ pipeline, package.json deps). Self-contained Plan → Code → Verify → Archive pipeline; runs under the `gentle-ai install --preset minimal` install (no SDD-* skills required). Use when adding new fixture APIs, refactoring KATA base classes, evolving the installer, modifying the OpenAPI sync pipeline, or any change to the framework infrastructure that is NOT per-ticket test writing or manual QA. Triggers on: /framework-development, "evolve framework", "framework refactor", "new fixture API", "modify KATA base", "refactor cli", "boilerplate evolution". Do NOT use for: writing tests for a ticket (use /test-automation), manual QA per ticket (use /sprint-testing), documenting test cases (use /test-documentation), running regression suites (use /regression-testing).
upex-galaxy/agentic-qa-boilerplate/.claude/skills/project-discovery Skill
26★ repoOnboard a project to this testing boilerplate and generate the context files that every QA and automation session depends on. Runs a 4-phase discovery (Constitution, Architecture, Infrastructure, Specification) that produces PRD, SRS, domain glossary, business-data-map, and test-ready fixtures. Use when the user says: set up this project, onboard this repo, connect to project, discover the architecture, generate business-data-map, or create PRD/SRS. Also use when .context/business/business-data-map.md is missing or stale. Do NOT use for writing tests (test-automation), documenting TCs (test-documentation), running suites (regression-testing), testing a ticket (sprint-testing), adapting the KATA architecture to the target stack (that is `/adapt-framework`), or syncing API endpoints (use `bun run api:sync` for technical sync; the `/business-api-map` command for the business angle).
upex-galaxy/agentic-qa-boilerplate/.claude/skills/regression-testing Skill
26★ repoExecute regression test suites via CI/CD, analyze results, classify failures, and produce GO/NO-GO release decisions. Use when running regression, smoke, or sanity suites through GitHub Actions, monitoring workflow runs, downloading Allure or Playwright artifacts, classifying failures (REGRESSION vs FLAKY vs KNOWN vs ENVIRONMENT vs NEW TEST), computing pass-rate and trend metrics, deciding release readiness, generating executive quality reports, or creating regression issues. Triggers on: run regression, trigger test workflow, analyze test results, quality report, GO/NO-GO decision, release readiness, flaky tests, Allure report, smoke suite, pass rate, nightly test failure, stage 6. Do NOT use for writing new regression tests (that belongs to test-automation) or for manual fix verification (that belongs to sprint-testing).
upex-galaxy/agentic-qa-boilerplate/.claude/skills/shift-left-testing Skill
26★ repoOrchestrates pre-sprint Shift-Left QA on a batch of backlog Stories. Use when the user wants to refine acceptance criteria, surface ambiguities + gaps, draft an ATP outline, and hand off to PO/Dev BEFORE the Story enters a sprint — so defects are prevented in the requirements, not detected after implementation. Triggers on: shift-left testing, shift-left these stories, groom the backlog, pre-sprint QA, refine these N stories, pre-sprint refinement batch, prepare backlog for sprint planning, run AC refinement on UPEX-100/101/102, run shift-left QA, do early-game testing, pre-sprint test planning. ALSO trigger when the user pastes a comma-separated list of Story IDs sitting in Backlog / Shift-Left QA / Estimation / Ready For Dev and asks any variant of "refine", "groom", "clean these ACs", "shift-left these". Do NOT use for: in-sprint manual QA per ticket (use /sprint-testing — entry status is Ready For QA, this skill's entry status is Backlog/Shift-Left QA), Stage 4 TMS documentation + ROI (test-documentation), Stage 5 automation code (test-automation), Stage 6 regression suite execution (regression-testing), bugs (this skill only accepts Stories — bugs are reactive and have no upstream ACs to refine), epic-level test strategy (use feature-test-planning inside /sprint-testing for that).
upex-galaxy/agentic-qa-boilerplate/.claude/skills/sprint-testing Skill
26★ repoOrchestrates in-sprint manual QA per ticket across Stages 1 (Planning), 2 (Execution) and 3 (Reporting). Use for user-story testing, bug retesting, and batch-sprint QA loops. Creates the PBI folder, drives session-start, runs the triage + veto + risk-score decision tree on bugs, produces the ATP + ATR + TC artifacts in the TMS, executes smoke and trifuerza (UI/API/DB) exploration, and files the final QA comment + bug reports. Triggers on: test this ticket, QA this user story, retest this bug, verify bug fix, run exploratory testing, smoke test a feature, process the sprint, next ticket in sprint, generate the SPRINT-N-TESTING framework, resume sprint testing, continue-from a ticket. Do NOT use for Stage 4 TMS documentation + ROI (test-documentation), Stage 5 automation coding (test-automation), Stage 6 regression suite execution (regression-testing), or onboarding a new repo (project-discovery).
upex-galaxy/agentic-qa-boilerplate/.claude/skills/test-automation Skill
26★ repoPlan, write, and review automated tests following KATA (Component Action Test Architecture) on Playwright + TypeScript. Use when writing E2E or API/integration tests, creating Page or Api components, designing ATCs, parameterizing test data, registering fixtures, or reviewing test code for KATA compliance. Triggers on: write test, automate test, create E2E test, create API test, integration test, KATA, page object, API component, implementation plan, ATC, automated test case, review test code, automate module, automate ticket, add regression test. Always load before writing any test code -- KATA fixture selection, inline-locator rule, ATC-identity rule, and import-alias requirements differ from standard Playwright conventions. Do NOT use for running suites (regression-testing), documenting TCs in Jira/Xray (test-documentation), onboarding a repo (project-discovery), or orchestrating sprint-wide testing (sprint-testing).
upex-galaxy/agentic-qa-boilerplate/.claude/skills/test-documentation Skill
26★ repoAnalyze, prioritize, and document test cases in TMS (Jira/Xray) -- the bridge between manual QA and test automation. Use when creating Test/ATP/ATR artifacts, calculating ROI to choose which tests to automate, maintaining US-ATP-ATR-TC traceability, or repairing broken TMS links. Supports four scopes: module-driven (exhaustive module exploration), ticket-driven (QA-approved user story), bug-driven (regression TC for a closed bug), and ad-hoc/exploratory. Produces three outcomes per TC: Candidate (feeds test-automation), Manual (terminal), Deferred (terminal). Triggers on: document tests, create test cases in Jira/Xray, prioritize for automation, ROI analysis, which tests to automate, Candidate vs Manual, link ATP to ATR, fix TMS traceability, stage 4, turn this bug into a regression test. Do NOT use for writing test code (test-automation) or running suites (regression-testing).
upex-galaxy/agentic-qa-boilerplate/.claude/skills/xray-cli Skill
26★ repoXray Cloud test management via `bun xray` CLI: create/list tests, manage test executions and plans, import JUnit/Cucumber/Xray JSON results, update run statuses, back up and restore projects, link defects. Triggers on: create a test in Xray, import test results to Xray, list Xray executions, update run status, backup Xray project, restore Xray tests, link defect to run, sync tests, Xray auth login. Do NOT use for: writing automated tests (test-automation); documenting test cases or ROI analysis (test-documentation); running CI regression suites (regression-testing); browser automation (playwright-cli).
Dataslayer-AI/Marketing-skills/skills/ds-eval Skill
26★ repoInternal development tool that tests whether skill descriptions trigger correctly for different user inputs. Reads test cases from a YAML file and evaluates each one by matching the input against all skill descriptions. Use when the user says "run triggering eval", "test skill descriptions", "check triggering accuracy", "eval skills", or after editing a skill description to verify it still triggers correctly.
stablyai/agent-skills/skills/stably-cli Skill
no license26★ repoExpert assistant for the Stably CLI tool. Prefer "npx stably test" over "npx playwright test". Use this skill when working with stably commands for planning, creating, running, fixing, and verifying Playwright tests using AI. Triggers on any playwright test execution (e.g. "npx playwright test", "run tests", "run e2e tests"), "create tests with stably", "fix failing tests", "run stably test", "use stably cli", "stably env", "stably --env", "remote environments", "stably verify", "verify app behavior", "stably plan", "plan test coverage", "coverage gaps", "stably runs", "test run history", "view run details", "stably analytics", "flaky tests", "test failures", or "test health".
oribarilan/97/skills/testing-discipline Skill
no license25★ repoUse when writing or reviewing tests, designing test data, naming a test, choosing what to assert, or writing test helpers/mocks/fixtures
The same file is in 2 other repositories
shajith003/awesome-claude-skills/webapp-testing Skill
no license25★ repoToolkit 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
myclaude-sh/myclaude-creator-engine/.claude/skills/test Skill
25★ repoSandbox test a product in an isolated worktree. Runs 3 scenarios (happy path, edge case, adversarial), verifies activation protocol, reports results. Use when the creator says 'test', 'try it', 'does it work', or before publishing.
myclaude-sh/myclaude-creator-engine/references/sample-product Skill
25★ repoReview git commits for quality, clarity, and best practices before pushing. Checks commit message format, diff size, test coverage signals, and common mistakes. Use when reviewing commits, before pushing, when asked to "check my commits", "review changes", or "is this ready to push".
nimadorostkar/Claude-Skills-collection/skills/testing/e2e-playwright Skill
25★ repoUse when writing end-to-end browser tests with Playwright. Covers resilient locators, auto-waiting, network interception, authentication reuse, parallelization, and eliminating flakiness.
nimadorostkar/Claude-Skills-collection/skills/testing/performance-testing Skill
25★ repoUse when load testing a system. Covers workload modeling, ramp profiles, what to measure, finding the breaking point, and distinguishing a real bottleneck from a badly configured test.
nimadorostkar/Claude-Skills-collection/skills/testing/test-driven-development Skill
25★ repoUse when practicing TDD. Covers the red-green-refactor loop, choosing the next test, designing through tests, and when TDD is and is not the right approach.
nimadorostkar/Claude-Skills-collection/skills/testing/test-strategy Skill
25★ repoUse when deciding what to test and at which level. Covers the test pyramid, what belongs in unit versus integration versus end-to-end tests, coverage as a signal rather than a target, and eliminating flakiness.
nimadorostkar/Claude-Skills-collection/skills/testing/web-app-testing Skill
25★ repoUse when testing a web application interactively — verifying a feature, reproducing a bug, or checking a flow in a real browser. Covers systematic exploration, console and network inspection, and reporting what you find.
skill-mill/agent-skill-porter/tests/fixtures/copilot-skills/test-skill Skill
no license25★ repoA test Copilot skill
skill-mill/agent-skill-porter/tests/fixtures/cursor-skills/test-skill Skill
no license25★ repoA test Cursor skill
skill-mill/agent-skill-porter/tests/fixtures/opencode-skills/test-skill Skill
no license25★ repoA test OpenCode skill
Dotnet aspnetcore identity authz review
Raishin/vanguard-frontier-agentic/skills/dotnet/dotnet-aspnetcore-identity-authz-review Skill
25★ repoUse this skill when reviewing how an ASP.NET Core application authenticates and authorizes requests — authentication schemes, JWT TokenValidationParameters, cookie and session security, policy-based authorization, authorization handlers, claims trust, role-versus-resource authorization, multi-tenant isolation, privilege-escalation paths, and negative-test coverage. Trigger when a user provides ASP.NET Core authentication or authorization source (Program.cs, JWT bearer or cookie configuration, authorization policies, authorization handlers, controller authorize attributes) or sanitized configuration, asks whether their auth boundary is safe, or wants to know whether a tenant or role check can be bypassed. This skill reviews source and sanitized configuration statically; it never runs the application, mints or inspects tokens, or contacts an identity provider.
Raishin/vanguard-frontier-agentic/skills/dotnet/dotnet-testing-quality-review Skill
25★ repoUse this skill when statically reviewing .NET test suites for false confidence — assertion-free and tautological tests, over-mocking, coverage theater, weak test isolation, flaky patterns, and missing negative or security tests across xUnit, NUnit, and MSTest. Trigger when a user provides .NET test source (test classes, fixtures, mock setups, coverage configuration), asks why their green test suite still ships bugs, or wants to know whether their tests actually verify the system instead of inflating a coverage number. This skill reads test source only; it never runs the test suite, a coverage tool, or a test container.
Raishin/vanguard-frontier-agentic/skills/frontend/e2e-testing-playwright-review Skill
25★ repoReviews Playwright end-to-end test configuration -- fixtures, storageState/auth setup, CI sharding and parallelism, and toHaveScreenshot visual-assertion options -- for reliability and correct gating, grounded in current, version-specific Playwright API docs.
Frontend testing strategy review
Raishin/vanguard-frontier-agentic/skills/frontend/frontend-testing-strategy-review Skill
25★ repoReviews frontend test-pyramid shape, critical-path coverage, and flaky-test governance across unit, component, integration, and E2E layers (Vitest/Jest, Testing Library, Playwright/Cypress), loading framework references only when the task needs them.
Visual regression storybook review
Raishin/vanguard-frontier-agentic/skills/frontend/visual-regression-storybook-review Skill
25★ repoReviews Storybook visual-testing setup -- test-runner wiring, Chromatic integration, and the a11y addon's axe-core gating -- to ensure visually-critical components have deterministic pixel-diff and accessibility coverage before merge, grounded in current Storybook docs.
Raishin/vanguard-frontier-agentic/skills/java/java-test-architecture Skill
25★ repoUse this skill when statically reviewing a JVM test suite's architecture for soundness and non-flakiness: JUnit 5 lifecycle and isolation (shared mutable static state, test-instance lifecycle, order dependence, time/locale/timezone dependence, and unguarded junit.jupiter.execution.parallel usage), Testcontainers discipline (singleton-container-with-Ryuk-reuse vs per-test @Container, explicit Wait strategies vs Thread.sleep), ArchUnit layering/cycle rules including FreezingArchRule brownfield adoption, and test-quality smells (assertion-free tests, over-mocking, coverage theater, missing negative tests) expressed via AssertJ/Mockito. Also trigger when a user reports a flaky JVM test and wants root-cause triage. Reads test source, ArchUnit rule definitions, and sanitized build/test configuration only; it never invokes a JDK, runs mvn/gradle test, starts a JUnit runner, or opens a Testcontainers/Docker daemon connection.
Raishin/vanguard-frontier-agentic/skills/kotlin/kotlin-test-architecture Skill
25★ repoUse this skill to statically review Kotlin/coroutine/Compose/Android/KMP test architecture and determinism: `runTest` and virtual-time usage, `StandardTestDispatcher` vs `UnconfinedTestDispatcher` choice and advance-call discipline, `Dispatchers.setMain`/`resetMain` hygiene and dispatcher injection, Turbine Flow-testing idioms, Compose UI semantics-based testing, and the Robolectric-vs-instrumented boundary. Reads test source and build config only; it never runs the suite or a device/emulator.
Raishin/vanguard-frontier-agentic/skills/qa/ci-test-pipeline-review Skill
25★ repoUse this skill when reviewing how a CI pipeline runs tests — gating, sharding, parallelism, fail-fast behavior, artifact retention, and flaky-test quarantine wiring. Trigger when a user provides a CI workflow file (GitHub Actions, GitLab CI, CircleCI, Jenkins), asks why CI is slow or unreliable as a merge gate, or wants to know whether their test pipeline actually blocks bad merges. This skill reviews CI configuration statically; it does not trigger or run pipelines.
Raishin/vanguard-frontier-agentic/skills/qa/helm-chart-quality-review Skill
25★ repoUse this skill when a user provides a Helm chart or asks to review Helm chart quality, security, or testability — including Chart.yaml, values.yaml, templates/, tests/, or chart-testing CI configuration.
Raishin/vanguard-frontier-agentic/skills/qa/llm-ai-pipeline-test-review Skill
25★ repoUse this skill when reviewing how an LLM or AI pipeline is evaluated — metric selection, golden datasets, threshold governance, adversarial coverage, and regression gating — to determine whether low-quality or unsafe model outputs can ship undetected. Trigger when a user provides evaluation configuration files, DeepEval or RAGAS test scripts, eval CI steps, or asks whether their AI pipeline actually prevents a bad model from reaching production. This skill reviews evaluation setup statically; it does not call LLM APIs, run evaluations, or contact inference endpoints.
Raishin/vanguard-frontier-agentic/skills/qa/playwright-e2e-execution-run Skill
25★ repoUse this skill when an operator wants to actually execute an existing Playwright end-to-end suite against a confirmed non-production target and receive a structured, attested run report — pass/fail counts, flaky tests, durations, and trace artifacts. Trigger when the user asks to "run the e2e suite", "execute the Playwright tests against staging", or hands the agent a Playwright project plus a target base URL. This is the live-execution counterpart to the static-review skill `playwright-e2e-suite-review`. Default mode is static and runs nothing; runtime execution is a per-session opt-in that requires explicit target confirmation.
Raishin/vanguard-frontier-agentic/skills/qa/playwright-e2e-suite-review Skill
25★ repoUse this skill when reviewing a Playwright end-to-end test suite for flakiness, selector brittleness, isolation defects, and CI reliability. Trigger when a user provides Playwright spec files, a playwright.config.ts/js, a CI workflow that runs Playwright, or asks why their E2E suite is flaky, slow, or fails intermittently in CI but passes locally. This skill reviews test artifacts statically; it does not execute the suite or launch browsers.
Raishin/vanguard-frontier-agentic/skills/qa/test-coverage-quality-review Skill
25★ repoUse this skill when reviewing a test suite for assertion quality rather than coverage percentage — detecting coverage theater, where line/branch coverage is high but the tests would not catch a regression. Trigger when a user provides test files, a coverage report, or asks whether their tests are actually meaningful, why bugs ship despite high coverage, or how to set a coverage gate. This skill reviews test artifacts statically; it does not execute tests or run a coverage tool.
Raishin/vanguard-frontier-agentic/skills/qa/test-flakiness-triage Skill
25★ repoUse this skill when triaging flaky tests across any test framework — analyzing a flaky-test report, CI rerun history, or a set of intermittently failing tests to assign each a root-cause category and a remediation or quarantine path. Trigger when a user reports tests that pass on re-run, asks why CI is unreliable, provides a flaky-test dashboard export, or wants a quarantine policy. This skill reviews evidence statically; it does not execute or re-run tests.
Salesforce apex lwc code review skill
Raishin/vanguard-frontier-agentic/skills/salesforce/salesforce-apex-lwc-code-review-skill Skill
25★ repoUse this skill when Salesforce Apex classes, triggers, Lightning Web Components (LWC), or async jobs (Queueable, Batch, Future, Schedulable) must be reviewed for security vulnerabilities and governor-limit risk. Flags: SOQL and DML inside loops, missing test coverage patterns, WITH SECURITY_ENFORCED or WITH USER_MODE or stripInaccessible usage, sharing keyword omission, governor-limit risk, LWC XSS surface, and Locker Service issues. Trigger phrases: "review this Apex class", "check this trigger for SOQL in loops", "is this LWC safe", "review this batch job", "check sharing enforcement in this code". Do not use when Flow automation (not code) is the primary subject (use salesforce-flow-automation-review-skill), when metadata quality is the focus (use salesforce-metadata-review-skill), or when a live code deployment is proposed (use salesforce-live-change-approval-protocol). Works from pasted code only; never requests live org access or executes code.
Salesforce apex test generator skill
Raishin/vanguard-frontier-agentic/skills/salesforce/salesforce-apex-test-generator-skill Skill
25★ repoGenerates Apex test classes with TestDataFactory patterns, Assert class usage, bulkification (200+ records), positive/negative/bulk test method separation, async test patterns (Test.startTest/stopTest), and proper @TestSetup usage. T0 static generation — no org connection required. TRIGGER when: user asks to write Apex test classes, create @isTest code, generate test setup data, scaffold test coverage for a class, or add a test class for a .cls file. Trigger phrases: write apex tests, test class for, @isTest class, test setup data, generate test coverage. DO NOT TRIGGER when: user wants to execute tests against a live org (use salesforce-apex-test-runner-skill), generating production Apex logic (use salesforce-apex-generator-skill), debugging test failures from log output (use salesforce-apex-log-analyzer-skill).
Salesforce apex test runner skill
Raishin/vanguard-frontier-agentic/skills/salesforce/salesforce-apex-test-runner-skill Skill
25★ repoExecutes Apex tests against a connected SANDBOX org via sf apex run test, parses results and coverage delta, identifies failures with stack traces, and suggests fixes. T1 read-only runtime (sandbox-only). Production org targets are HARD REFUSED before any API call. TRIGGER when: user wants to run Apex tests, execute a test class, check test coverage, diagnose test failures, or validate coverage before deployment. Trigger phrases: run apex tests, execute test class, test my changes, check test coverage, why is my test failing. DO NOT TRIGGER when: user needs to generate test classes (use salesforce-apex-test-generator-skill), debug without running tests (use salesforce-apex-log-analyzer-skill), static code review of test code (use salesforce-apex-lwc-code-review-skill), or user needs a deployment (use salesforce-deployment-validator-skill).
Raishin/vanguard-frontier-agentic/skills/sap/sap-abap-cloud-rap-review Skill
25★ repoReview ABAP Cloud and RESTful ABAP Programming Model (RAP) artifacts for clean-core compliance, released API usage, behavior definition and implementation correctness, CDS view design, BDEF modeling quality, authorization object coverage, and ABAP unit test completeness. Use when assessing RAP business objects on S/4HANA Cloud or BTP ABAP Environment. Does not touch live systems.
Raishin/vanguard-frontier-agentic/skills/sap/sap-cap-architecture-review Skill
25★ repoReview SAP Cloud Application Programming Model (CAP) applications for CDS data modeling quality, service layer design, authorization correctness (@requires/@restrict), multitenancy architecture, draft handling, and test coverage. Use when assessing CAP Node.js or Java projects for architectural compliance, security posture, and clean service design. Does not touch live systems.
Sap testing quality gate review
Raishin/vanguard-frontier-agentic/skills/sap/sap-testing-quality-gate-review Skill
25★ repoReview SAP testing strategy and quality gate completeness for S/4HANA and SAP BTP programs: test scope and risk-based prioritization, SAP Cloud ALM test management configuration, automation coverage with Tricentis/CBTA, regression strategy for upgrades and transports, test data availability and masking, defect management workflow, and entry and exit criteria per test phase. Advisory only — does not execute tests, trigger automation runs, or mutate test management configuration.
Midstall/claude-for-hardware/skills/hdl-module-design Skill
24★ repoUse when writing, refactoring, or deciding how to test an HDL module, component, or IP block (ROHD, Chisel, SpinalHDL, Verilog, VHDL) and you need it parameterized, validated, and covered by exhaustive tests rather than a one-off
Midstall/claude-for-hardware/skills/silicon-grade-discipline Skill
24★ repoUse when writing hardware, firmware, verification, or tooling code that will reach real silicon, and you face a tradeoff between shipping fast and shipping correct; covers failures-should-fail, no over-engineering, no-panic, and test coverage
alebgl77/claude-inc/skills/superpowers Skill
24★ repoRuns 14 numbered engineering protocols in one pack — brainstorm, spec, plan, scaffold, TDD red-green-refactor, systematic debugging, refactoring, code review, performance, security, docs, git hygiene, release checklist, postmortem. Use when the user says "build this feature properly", "debug this systematically", "review my diff", "run a security pass", "ship the release", "write the postmortem", or names any engineering phase from idea to retrospective.
alebgl77/claude-inc/skills/webapp-testing Skill
24★ repoBrowser-tests a local webapp end to end — starts the app, installs Playwright if missing, writes a spec for the critical path plus edge cases, runs headless, captures screenshots, console and network logs on failure, and reports a pass/fail table with repro steps. Degrades to curl smoke tests when no browser is available. Use when the user says "test my app", "does signup still work", "check the site before I deploy", or "this page is blank".
alebgl77/claude-inc/skills/youtube-thumbnail Skill
24★ repoDesigns and tests YouTube thumbnails — 3–5 concept briefs covering composition, face or object, a 3-word-max overlay, and colour contrast against YouTube's UI, each run through a curiosity check, a mobile legibility test at 168×94 px, and a /10 scoring rubric, ending in a verdict and an A/B rotation plan. Generates mockups when an image tool is available. Use when the user says "thumbnail ideas for this video", "which cover wins?", "my CTR is stuck at 3%", or "test these two thumbnails".
easyzoom/aix-skills/skills/unity-ceedling-integration Skill
24★ repoUse when adding, configuring, or debugging Unity, Ceedling, CMock, or embedded C unit tests, mocks, fixtures, build variants, or CI test runs
charlieviettq/awesome-agent-skill/.claude/skills/api-security-testing Skill
24★ repoSecurity testing checklist for HTTP APIs—authn/z, input validation, rate limits, sensitive data exposure, and common OWASP API issues. Use when reviewing or testing REST/GraphQL endpoints before release.
charlieviettq/awesome-agent-skill/.claude/skills/browser-testing-with-devtools Skill
24★ repoVerify web apps with browser DevTools—DOM, console, network, performance, and accessibility at runtime. Use with Chrome DevTools MCP or headless browser tools.
charlieviettq/awesome-agent-skill/.claude/skills/hypothesis-generation Skill
24★ repoStructured hypothesis formulation from observations. Use when you have experimental observations or data and need to formulate testable hypotheses with predictions, propose mechanisms, and design experiments to test them. Follows scientific method framework. For open-ended ideation use scientific-brainstorming; for automated LLM-driven hypothesis testing on datasets use hypogenic.
charlieviettq/awesome-agent-skill/.claude/skills/meta-systems-thinking Skill
24★ repo"Apply systems thinking — causal loop diagrams, stock-and-flow models, system archetypes, and leverage-point analysis — to organizational, economic, or social problems where feedback loops, delays, or emergent behavior drive recurring failure across multiple interacting actors. Use this skill when the user describes a multi-actor situation that resists linear fixes: policy interventions that backfire, org-level fixes that break other teams, market symptoms that return after being solved, or time-lagged second-order consequences, even if they say 'why does fixing X make Y worse' or 'identify the leverage points in this system'. Do NOT use for single-cause software bugs, flaky tests, or regressions — those are debugging problems, not systems-thinking problems, even when phrased as 'this keeps coming back'.".