All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 31,095
- 1,296
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse testing & qa skills
Showing 3,121–3,144 of 31,095 skills
- Sumo Qa Triaging Test FailuresUse after sumo-qa-deciding-approach routes here, when a test is failing or flaky and the cause is not yet known — e.g. 'this test keeps failing', 'red in CI but passes locally', 'this test is flaky', 'a test failed, what now?'. Reads the failure output, classifies the likely cause, and names the smallest next isolation step BEFORE any fix. Diagnosis only — it does not patch; it routes to a fixing skill only once a concrete product-behaviour gap is confirmed.Votes: 0GitHub stars: 7
- Sumo Qa Suggesting External SkillUse when sumo-qa-deciding-approach routes here (no native sumo-qa sub-skill fits a QA surface) OR when an ingestion source needs converting to markdown before it can be ingested. Finds, installs, and executes an external skill for any capability sumo-qa lacks natively, through sumo-qa MCP tools, with [y/N] confirmation before each install and fallback to the next candidate on failure. Never invoked cold — always via the deciding-approach fallback or the ingestion conversion entry.Votes: 0GitHub stars: 7
- Sumo Qa Strengthening TestsUse after sumo-qa-deciding-approach picks strengthen-test-coverage. Mutation-testing follow-up, raise-coverage tasks, killing weak assertions. Walks survivor → tautology check → technique → strengthening test, one mutant at a time with confirmation gates. Production code STAYS UNCHANGED.Votes: 0GitHub stars: 7
- Sumo Qa StrategisingUse after sumo-qa-deciding-approach routes here, for repo-wide / policy-shaped asks — "audit our test coverage", "design our QA strategy from scratch", "where should we invest QA effort first", "design our test pyramid". Walks the repo with the host's file tools first.Votes: 0GitHub stars: 7
- Sumo Qa Security TestingUse after sumo-qa-deciding-approach routes here, when explicit security testing or a grounded security gap needs deeper evidence selection.Votes: 0GitHub stars: 7
- Sumo Qa Reviewing Before MergeUse after sumo-qa-deciding-approach routes here, when the user asks "review my changes" / "is this safe to merge" / "what could break". Refuses to claim safe-to-merge without fresh verification evidence.Votes: 0GitHub stars: 7
- Sumo Qa Preparing For WorkUse after sumo-qa-deciding-approach routes here, when the user asks to plan QA for a story, ticket, or piece of work before coding starts. Lighter-weight than sumo-qa-creating-test-plan; no formal entry/exit criteria.Votes: 0GitHub stars: 7
- Sumo Qa Planning Qa RolloutUse after sumo-qa-deciding-approach routes here, when you have a chunk of QA work (a story, a PR, a strategy phase) that needs to be turned into a written plan of bite-sized, independently-executable tasks before any test code is written. Produces docs/qa/plans/YYYY-MM-DD-<feature>.md ready for subagent dispatch via sumo-qa-executing-qa-rollout.Votes: 0GitHub stars: 7
- Sumo Qa Measuring CoverageUse after sumo-qa-deciding-approach routes here, when the user wants coverage or mutation numbers in the local QA report — "run coverage", "measure coverage", "run mutation testing", "record the survivors". Runs the repo's configured coverage/mutation tool, reads its output (any format), and persists a compact summary into the .sumo-qa artifacts the report loads.Votes: 0GitHub stars: 7
- Sumo Qa Implementing With TddUse after sumo-qa-deciding-approach picks tdd-scaffold, regression-first, or coverage-first-then-refactor — e.g. "write a regression test for this bug" or "scaffold the failing tests first". Walks plan → name-the-risk-and-test-idea → confirm → red → hand off → green → review, one section per turn with confirmation gates. Don't write the test until the test idea has been agreed.Votes: 0GitHub stars: 7
- Sumo Qa Finishing Qa WorkUse at the end of a QA rollout (after sumo-qa-executing-qa-rollout, or after a manual multi-step QA task) to capture evidence, produce a PR-ready summary, and close the loop. Runs the suite one last time, captures coverage / risk-to-test map / open follow-ups, writes a markdown summary to docs/qa/runs/YYYY-MM-DD-<feature>.md, and offers to draft the PR description.Votes: 0GitHub stars: 7
- Sumo Qa Finding Test DataUse after sumo-qa-deciding-approach routes here, when the user asks about test data — what data to test X, find a known-good record, validate an entry, register new known-good data. Routes between the explain, find, validate and register test-data tools.Votes: 0GitHub stars: 7
- Sumo Qa Executing Qa RolloutUse after sumo-qa-planning-qa-rollout to dispatch a written QA plan task-by-task. Each task runs in a fresh subagent (parallel where independent); each subagent's output goes through a two-stage review (test-correctness → test-quality) before the task is marked done. Continuous execution — no per-task check-ins. Finishes by routing to sumo-qa-finishing-qa-work.Votes: 0GitHub stars: 7
- Sumo Qa Deciding ApproachUse first after using-sumo-qa on any QA intent. Loads classifications + approaches (the two needed to route), then reasons over the user's intent to pick the canonical approach and routes to the matching sub-skill (which loads any further catalogues on demand).Votes: 0GitHub stars: 7
- Sumo Qa Creating Test PlanUse after sumo-qa-deciding-approach routes here, when the user asks for a formal test plan, entry/exit criteria, or a phased QA approach for a piece of work. Heavier than sumo-qa-preparing-for-work; use when the work is tracked or formally reviewed.Votes: 0GitHub stars: 7
- Sumo Qa Closing Qa GapsUse after sumo-qa-deciding-approach routes here, when a review, mutation run, or graded scenario has already named a concrete uncovered behavior gap and the user wants it closed with evidence — e.g. 'close this gap', 'drive this uncovered risk to a regression test', 'fix this surviving mutant end to end'. Drives ONE closed loop per gap, with red and green evidence. Pauses when repo context or evidence is insufficient.Votes: 0GitHub stars: 7
- Sumo Qa Answering Testing QuestionUse after sumo-qa-deciding-approach routes here, when the user asks a generic testing question — "how do I test this?", "what should I check for X?" — that doesn't fit a more specific QA skill. Cites a principle or technique from the loaded catalogue rather than producing generic advice.Votes: 0GitHub stars: 7
- Scaffold Sumo Qa SkillScaffolds a new sumo-qa sub-skill end-to-end — SKILL.md skeleton, matching promptfoo eval YAML, and an approaches.md catalogue entry — through a single bundled script. Use this whenever the user wants to add a new sumo-qa-* skill, even if they describe it as "creating a skill", "adding an approach", "starting a new routing branch", or just "writing skills/sumo-qa-X". Enforces the sumo-qa- name prefix and checks for collisions against both the source tree and the installed MCP server, so a cle...Votes: 0GitHub stars: 7
- Regen Eval BaselineCaptures a promptfoo skill-eval baseline JSON for one sumo-qa skill and snapshots it to docs/qa/runs/eval-baselines/, with an automatic delta against the prior snapshot. Use this whenever the user mentions baselining a skill, capturing a before/after eval, running a single-skill eval, or measuring the effect of a SKILL.md edit, common during token-optimisation rounds. The actual work runs through a bundled script that handles path conventions, the Claude CLI check, and diffing in one go.Votes: 0GitHub stars: 7
- PrPull Request skill for creating well-structured, consistently formatted PRs using the GitHub CLIVotes: 0GitHub stars: 8
- dnb-company-verification使用 D&B China Data（主题化中国数据 CDT）MCP 企业档案 Server（/v1/company）全部 14 个 Tool，对单一企业开展工商登记、简易注销、变更、股东与控股治理、主要人员、受益所有人、实际控制人、对外投资、分支机构、ICP 备案与企业年报的尽调式核验，输出结构化核查底稿与事实包。当用户要求做企业信息核验、工商底稿、主体真实性核查、股权与治理结构核查、UBO/实控人核验、年报与变更追溯、仅查企业档案不下钻风险/评分时触发此 skill。本 skill 只使用企业档案 Server，不输出评级与准入结论。Votes: 0GitHub stars: 45
- VerificationFull-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.Votes: 0GitHub stars: 9
- Twilio Whatsapp Manage SendersCreate, configure, and manage WhatsApp Business senders via Twilio's Channels Senders API. Covers programmatic sender registration, profile setup, webhook configuration, sender lifecycle statuses, and ISV flows. Use this skill to register and manage production WhatsApp senders at scale.Votes: 0GitHub stars: 9
- Twilio Verify Send OtpSend and verify one-time passcodes (OTPs) via Twilio Verify over SMS, RCS, voice, email, or WhatsApp. Covers creating a Verify Service, sending tokens, checking submitted codes, automatic WhatsApp-to-SMS fallback, and service configuration. TOTP is supported via the Factors API (a separate family from channel-based OTP). Use this skill to add phone or email verification or two-factor authentication to any application.Votes: 0GitHub stars: 9