All categories
Testing & QA
Unit tests, integration tests, E2E, QA, validation, and test automation
- 31,469
- 1,312
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 4,561–4,584 of 31,469 skills
- Evaluate And Tighten SkillsCompatibility router for semantic skill tightening. Delegate goal recovery, authority, semantic conservation, evaluation contracts, and instruction optimization to Skill Lapidary rather than duplicating that system in Plugin Creator.Votes: 0GitHub stars: 67
- Perl ValidateThis skill should be used when the user asks to "validate Perl script", "check Perl syntax", "verify Perl code", "/perl-validate", or mentions script validation, compile check, security review, or best practice compliance for Perl code.Votes: 0GitHub stars: 67
- Perl TestingThis skill should be used when the user asks to write Perl tests, test Perl code, use Test More, run prove, create test suite, mock Perl, or mentions Perl testing, TAP, Test Class, Test Deep, or test-driven development in Perl.Votes: 0GitHub stars: 67
- Fastmcp Python TestsWrite and evaluate effective Python tests using pytest. Use when writing tests, reviewing test code, debugging test failures, or improving test coverage. Covers test design, fixtures, parameterization, mocking, and async testing.Votes: 0GitHub stars: 67
- Verify DoneRigorous self-assessment checklist before marking any task as complete. Use when about to claim task completion, before final commit, when user asks "is it done?", or when transitioning from implementation to reporting. Prevents premature completion claims by requiring evidence for every assertion.Votes: 0GitHub stars: 67
- Validation ProtocolScientific validation protocol for verifying fixes work through observation, not assumption. Use when claiming a bug fix, code change, refactoring, or implementation is complete — enforces reproduce-broken-state then define-success-criteria then apply-fix then verify-outcome. Success means observing intended behavior, not absence of errors.Votes: 0GitHub stars: 67
- Test Failure MindsetUse when investigating failing tests or deciding whether to change the test or product. Validate test expectations against authoritative intent, trace product and test boundaries, and require evidence for the correction rather than automatic code fixes or test dismissal.Votes: 0GitHub stars: 67
- PlanningUse when Stage 1 Discovery is complete and design must begin — transforms the ARTIFACT:DISCOVERY into an actionable ARTIFACT:PLAN via RT-ICA prerequisite verification. Produces approach, components, success criteria, acceptance tests, and risks. Blocks on missing prerequisites before design proceeds.Votes: 0GitHub stars: 67
- Multi Perspective ReviewUse when a diff needs four parallel perspective reviewers (Security, Performance, Quality, Accessibility). Creates an ephemeral SAM plan, collects structured verdicts, synthesizes them into one deduplicated cross-referenced punch list, prints one summary line per perspective, and exits non-zero if any perspective returns REJECT. SKIP is a passing outcome.Votes: 0GitHub stars: 67
- Final VerificationCertifies that a feature achieves its original objectives via goal-backward verification (SAM Stage 7). Use when all tasks pass forensic review — starts from expected outcomes, works backwards to verify each was achieved, and returns CERTIFIED or NOT_CERTIFIED with specific gaps.Votes: 0GitHub stars: 67
- Complete ImplementationUse when all tasks for a feature are marked COMPLETE — runs holistic quality gates including code review, feature verification, integration check, documentation drift audit and update, and context refinement. Creates follow-up plans when issues are found.Votes: 0GitHub stars: 67
- Code Review PythonProvides Python-specific code review rules for the dh code-reviewer agent. Activates on pyproject.toml or *.py file detection — enforces uv, ruff, ty, pytest, type annotation, error handling, and Python 3.11+ idioms including pathlib, match statements, and modern union syntax.Votes: 0GitHub stars: 67
- Add New FeatureSAM-style feature initiation workflow — discovery through codebase analysis, architecture spec, task decomposition, validation, and context manifest. Use when a user asks to add a feature, plan a feature, or convert an idea into an executable SAM plan.Votes: 0GitHub stars: 67
- Cove Prompt DesignExplains Chain of Verification (CoVe) prompt design — a 4-step pattern separating generation from independent factual verification. Use when designing prompts that require factual accuracy, reducing hallucinations, checking technical standards or APIs, or producing step-by-step procedures where subtle errors are costly.Votes: 0GitHub stars: 67
- Agent BrowserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.Votes: 0GitHub stars: 67
- VerificationVerification tools for compiling, validating, and disproving Lean theoremsVotes: 0GitHub stars: 273
- LlmLLM-assisted tools for informal proofs, proof strategy discussion, and code simplificationVotes: 0GitHub stars: 273
- Pipeline History AuditAudit a MaaFramework/Maa-series project's Git history to learn how Pipeline JSON, interface options, Python AgentServer CustomAction code, and related data tables evolved. Use when asked to review a Maa project from initial commit through a target commit, map `action: Custom` pipeline nodes to `@AgentServer.custom_action(...)` implementations, find pipeline/custom/option patterns or breakages, and produce a report plus skill-improvement recommendations.Votes: 0GitHub stars: 66
- Testing Strategy BuilderCreate a practical test strategy that coding agents can extend consistently. Use when a repo needs unit/integration/e2e conventions, fixtures, test command wrappers, examples, or a bug-fix rule that starts with a failing reproduction test.Votes: 0GitHub stars: 3
- Tdd Playwright WorkflowDrive changes through TDD with unit tests and Playwright e2e tests. Use when a bug fix or feature should start with a failing reproduction, when browser workflows need e2e coverage, or when Playwright setup/test wrappers are needed.Votes: 0GitHub stars: 3
- Subagent Review OrchestratorGenerate and validate project-scoped Codex subagents for explicit read-heavy exploration, review, security, docs research, browser QA, and trajectory auditing. Use when a repo should expose .codex/agents specialists without bundling global agent config or spawning agents automatically.Votes: 0GitHub stars: 3
- Quality Gates InstallerInstall executable quality gates for a repo and normalize validation behind stable scripts. Use when a project needs linting, formatting, type checking, tests, builds, doc checks, boundary checks, CI, or a single scripts/validate command for Codex.Votes: 0GitHub stars: 3
- Openspec SddUse OpenSpec for formal spec-driven development. Use when a feature, refactor, or product change should be proposed, designed, task-planned, validated, synced, or archived through openspec/ artifacts before or during implementation.Votes: 0GitHub stars: 3
- Click Path And Browser QaInventory and validate user-facing browser workflows with click-path evidence, accessible controls, Playwright coverage, console/network checks, and lifecycle verification. Use for UI work, web regressions, shadcn/ui changes, todo-style create/edit/delete flows, or browser acceptance testing.Votes: 0GitHub stars: 3