Loading...
Loading...
Found 422 Skills
Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead.
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
NeuroForge QA is a QA/UX review system grounded in the 30 Laws of UX and QA engineering standards. Works with ANY framework, language, or software — React, Vue, iOS, Android, APIs, wireframes, or plain descriptions. On activation it scans the project and creates (or reads existing) files in a /neuroforge/ folder: project analysis, UX audit, risk register, accessibility audit, and test cases in /neuroforge/test-cases/. Treats these files as single source of truth, updating incrementally. Trigger on: "review my UI", "audit this design", "write test cases", "check my UX", "QA this flow", "critique my wireframe", "write tests for", "find bugs in", any screenshot shared for feedback, or any request for QA or UX analysis of a product, screen, flow, or codebase. When in doubt, trigger.
Interactive QA session where users report bugs or issues through conversation, and the agent creates GitHub issues. Explore the codebase in the background to obtain context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
E2E testing and browser automation with qa-use CLI. Use when the user needs to run tests, verify features, automate browser interactions, or debug test failures.
Expert-level quality assurance, testing strategies, automation, and QA processes
Comprehensive quality assurance and testing workflow that orchestrates test strategy design, automated testing implementation, performance testing, and quality metrics. Handles everything from unit testing and integration testing to end-to-end testing, performance testing, and quality assurance automation.
Ejecuta pruebas E2E y QA manual usando Playwright MCP para verificar la ultima tarea completada en la conversacion. Usar cuando se necesite: (1) Probar un flujo recien implementado, (2) Verificar que una funcionalidad funciona correctamente, (3) Hacer QA manual de una nueva feature, (4) Testear formularios, flujos de autenticacion, o cualquier interaccion de usuario. El skill busca credenciales en CREDENTIALS.md, intenta conectar al puerto 5173 por defecto, y pide confirmacion antes de ejecutar las pruebas.
Reviews finished and in-progress digital products to assess adherence to design specifications and discover potential issues. Use when user says "design review", "design QA", "QA review", "check implementation", "visual bugs", "compare to design", "match the specs", "review the build", "before launch", "pre-launch review", "implementation review", "verify design", "design validation", "spacing issues", "visual discrepancies", "accessibility review", "WCAG compliance", or "responsive testing". Validates implementation against design intent, identifies visual and interaction discrepancies, and provides actionable feedback. Do NOT use when still designing concepts (use design-concepts), need to understand users (use design-research), or nothing has been built yet.
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
Expert in quality assurance and testing. Responsible for bug detection, edge case validation, test planning, and automated test creation to ensure software reliability.
Use before launching sequences to validate content, data, compliance, and monitoring.