create-test-runlisted

Create a Kobiton test run from a test case or suite, then offer to monitor it. When the user gives only partial details (or just a test case id), fill the rest with sensible defaults that match the createTestRun schema, show a summary of what will run, and ask to proceed or customize before creating. After the run is created, offer monitoring in a single prompt — monitor + auto-open live remediation (only when the org's live-remediation flag is ON), monitor only, or don't monitor — and hand off to the monitor-test-run skill if chosen. Use when the user asks to "create / kick off / start / run a test run", "run test case X on N devices", or similar. Wraps the createTestRun MCP tool (and getOrgSettings / listDevices for defaults); delegates the watch to monitor-test-run.
kobiton/automate · ★ 12 · AI & Automation · score 78

Install: claude install-skill kobiton/automate

## Prerequisites **Needs only an authenticated Kobiton MCP connection** — no local filesystem, no credentials file, no binary, no shell. It is the plugin's only pure-MCP skill, so it is the only one that works where the host supplies nothing else. **The monitoring hand-off in Step 5 is the exception**: `monitor-test-run` runs a local poller, so where you can't run a local command at all, create the run and report its id instead of offering to watch it (Step 5 carries the wording). Where you *can*, hand off and let that skill check its own credentials and streaming options — it degrades rather than refusing. See the Skill compatibility matrix in `CLAUDE.md`. ## Overview Turn a "run this" request into a created test run with as little friction as the user wants, then offer to watch it. Two phases: 1. **Build + confirm the run.** Resolve what to run (test case or suite), on which devices, with what app — filling any unspecified field with a documented default — then show a one-screen summary and create on confirmation. 2. **Offer monitoring once.** After creation, present the monitor choice in a single prompt and delegate to `monitor-test-run` if the user wants it. > **Tool naming.** Kobiton MCP tools are referenced by bare name (`createTestRun`, > `getOrgSettings`, `listDevices`, `getTestCase`, `getTestSuite`). The host > resolves the prefix (`mcp__plugin_automate_kobiton__createTestRun`, > `mcp__kobiton__createTestRun`, etc.). ## Inputs | Input | Required | Not