playwright-browser
Use when automating browsers, testing pages, taking screenshots, checking UI, verifying login flows, or testing responsive behavior
Discover tools testing skills, compare source repositories and read the instructions for each workflow.
Use when automating browsers, testing pages, taking screenshots, checking UI, verifying login flows, or testing responsive behavior
Systematic debugging with hypothesis-driven investigation. Use when something is broken, tests are failing, unexpected behavior occurs, or errors need investigation. Triggers on: "this is broken", "debug", "why...
PowerShell TDD testing framework guidance for Pester v5+. Use when writing, structuring, or debugging PowerShell unit tests; mocking cmdlets, native commands (bash, git, curl), or .NET types; isolating tests wi...
Comprehensive unit testing framework for Bash and POSIX shell scripts using ShellSpec with TDD/BDD best practices. Use when writing tests for shell scripts, debugging test failures, refactoring scripts for test...
Bash Automated Testing System (BATS) for TDD-style testing of shell scripts. Use when: (1) Writing unit or integration tests for Bash scripts, (2) Testing CLI tools or shell functions, (3) Setting up test infra...
Manages ServiceNow testing. Use for running test suites. Triggers - ATF, automated tests.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs. [MAND...
Accumulate evidence (screenshots, videos, logs) under .artifacts// for visual regression and PR documentation workflow. [MANDATORY] Before saying "implementation complete", you MUST use this skill to collect ev...
Multi-agent code verification workflow using a main agent and sub-agent loop. Use when verifying code against requirements, acceptance criteria, or quality standards. Triggers on requests to verify, validate, o...
Analyze existing tests to identify patterns, fixtures, and conventions before writing new tests
Generate comprehensive test coverage reports when reviewing code. Identifies untested code paths and low-coverage areas. Supports Python (pytest-cov), JavaScript (jest), Go (go test -cover), Java (JaCoCo). Use...
Browser automation tool using Playwright - captures screenshots and extracts content from web pages
A tool that echoes its input for testing
Browser automation using Puppeteer or Playwright. Use for web testing, screenshots, form filling, and automated browser interactions.
Performance profiling and optimization. Use for benchmarking code, analyzing performance, running Lighthouse audits, and finding hotspots.
Generate tests using AI and run test suites. Use for generating unit tests, running coverage reports, and mutation testing.
Systematic testing methodology for Go projects using TDD, coverage-driven gap closure, fixture patterns, and CLI testing. Use when establishing test strategy from scratch, improving test coverage from 60-75% to...
Design, implement, and maintain high‑value TypeScript test suites using popular JS/TS testing libraries. Use this skill whenever the user is adding tests, debugging failing tests, or refactoring code that shoul...
Validates Model Context Protocol (MCP) compliance by running official compliance test suite against Pierre server
Executes comprehensive test suite across unit, integration, E2E, database, protocols, and intelligence algorithms
Reliable, composable browser automation using minimal OpenCode Browser primitives.
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check...
Run the complete test suite for connectrpc-axum. Use when the user asks to run tests, verify changes, or check if the code works.
Laravel Dusk - Browser automation and testing API for Laravel applications. Use when writing browser tests, automating UI testing, testing JavaScript interactions, or implementing end-to-end tests in Laravel.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.