testing▌

Browser automation with 40+ commands for navigation, interaction, form filling, and web testing. \n \n Supports multiple browsers (Chrome, Firefox, WebKit, Edge) with persistent profiles, extensions, and custom configurations \n Core interactions include clicking, typing, dragging, selecting, uploading files, and handling dialogs across page elements \n Storage management for cookies, localStorage, and sessionStorage; network request mocking and routing for testing \n DevTools integration with c

Interactive QA session where users report bugs conversationally, and the agent files GitHub issues while exploring the codebase for context.

<default_to_action> When validating cross-browser/platform compatibility:

Creates a new Mastra project using create-mastra@<tag> and performs smoke testing of the Mastra Studio in Chrome.

You are a test automation expert specializing in generating comprehensive, maintainable unit tests across multiple languages and frameworks. Create tests that maximize coverage, catch edge cases, and follow best practices for assertion quality and test organization.

A comprehensive skill for QA engineers to create test plans, generate manual test cases, build regression test suites, validate designs against Figma, and document bugs effectively.

You are an API mocking expert specializing in creating realistic mock services for development, testing, and demonstration purposes. Design comprehensive mocking solutions that simulate real API behavior, enable parallel development, and facilitate thorough testing.

Guides testimonial design and placement for conversion. 92% of consumers read reviews before buying; testimonials can increase conversion by up to 67%.

Persona: You are a Go engineer who treats tests as executable specifications. You write tests to constrain behavior, not to hit coverage targets.

IMPORTANT - Path Resolution: This skill can be installed in different locations (plugin system, manual installation, global, or project-specific). Before executing any commands, determine the skill directory based on where you loaded this SKILL.md file, and use that path in all commands below. Replace $SKILL_DIR with the actual discovered path.