Loading...
Loading...
Found 22 Skills
Create and maintain Momentic browser E2E tests via the Momentic MCP tools. Use when a user asks to create a new test, scaffold a smoke test, or add/modify/delete steps in an existing test. Do not use for editing Momentic YAML directly.
Launch Oz cloud agents with computer use to reproduce UI-focused bug reports, capture visual evidence, and report reproduction findings. Use when investigating a specific interactive or visual bug from an issue, ticket, support report, or prompt.
Testing strategy and workflow. Tests run in parallel with isolated data per suite. Prioritize Playwright for UI, integration tests for APIs, unit tests for logic.
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
Run e2e tests, fix flake and outdated tests, identify bugs against spec. Use when running e2e tests, debugging test failures, or fixing flaky tests. Never changes source code logic or API without spec backing.
Improve test coverage in the OpenAI Agents Python repository: run `make coverage`, inspect coverage artifacts, identify low-coverage files, propose high-impact tests, and confirm with the user before writing tests.
Write high-quality Rust unit tests following best practices. Use when writing new tests, reviewing test code, or improving test quality. Emphasizes clear naming, AAA pattern, isolation, and deployment confidence.
Executes the project's test suite, analyzes failures, and provides fix recommendations.
Run tests for Keychat packages
Write and run tests for JS/TS projects. Handles unit tests with Vitest and React Testing Library directly. Delegates E2E and browser testing to /webapp-testing. Use when writing tests, adding coverage, debugging test failures, or running test suites.
Playwright E2E testing patterns. Trigger: When writing E2E tests - Page Objects, selectors, MCP workflow.
Browser automation skill for UI testing via Chrome MCP tools. Use when: (1) QA Agent needs to verify UI visually or test interactions, (2) UI/UX Designer needs to check responsive design or component states, (3) Frontend Dev needs quick visual verification during development, (4) Test Writer needs to document user flows with screenshots/GIFs, (5) Any agent needs to test web interfaces, record demos, or debug UI issues. Capabilities: screenshots, interaction testing, accessibility checks, GIF recording, responsive testing, console/network debugging.