skills

One-time project setup for mabl. Discover this user's mabl workspace, applications, environments, and credentials over the mabl MCP server, then save everything an AI agent needs to create and run mabl cloud tests where the user wants it — an agent memory file (CLAUDE.md / AGENTS.md / .github/copilot-instructions.md), a rule, or a skill. Fire when the user says "set up mabl", "mabl init", "initialize mabl", "configure mabl for this project", "save my mabl workspace / application / environment / credentials", "add mabl to my CLAUDE.md", or "/mabl-init". Run this once per project, before authoring or running tests. For creating a single test use mabl-test-authoring; for a whole suite use mabl-test-coverage-design.

Use when asked to create MULTIPLE mabl tests / a whole suite for a feature area — "add mabl coverage for X", "cover the X page/feature with mabl tests", "design a mabl test suite for X", "let's create tests for X", "explore X and create tests", or "/mabl-test-coverage-design". For testing a page, screen, form, flow, or feature broadly, not one specific scenario. This skill explores the feature, designs the set of tests, then authors each one in the mabl cloud. For a SINGLE test, use mabl-test-authoring directly.

Diagnose and fix failures detected by mabl end-to-end tests. Forensic inspection of an already-failed run (`mabl agent debug steps`, `mabl agent debug artifact`) plus an interactive live session that re-runs the test step-by-step in a real Chrome attached to the agent via CDP (`mabl agent debug session …`). Fire when the user mentions a mabl test failure, gives a test run ID (`*-jr`) or plan run ID (`*-pr`), asks to investigate / debug / fix / reproduce a failing test, or pairs "mabl" with words like "failing", "broken", "regression", "step through".

Create a SINGLE mabl browser and API tests through conversational planning and cloud authoring. Plan one test with an AI agent, refine the plan iteratively, then initiate cloud (or local) test generation. Fire when the user wants to create one mabl test, asks to "plan a test", "create a test for <one scenario>", "generate a mabl test", "author a test", or mentions testing a single URL / ticket with mabl. For broad coverage of a whole feature / page / flow with MULTIPLE tests, use mabl-test-coverage-design instead — it explores the feature, designs the suite, and calls THIS skill once per test.