testdino-runs
Use when the user wants to inspect automated test runs, list failed or flaky tests, debug a failing testcase with historical context, or filter runs by branch, commit, author, environment, browser, status, or tags. Includes list_testruns, get_run_details, list_testcase, get_testcase_details, and debug_testcase.
git clone --depth 1 https://github.com/anthropics/claude-plugins-community /tmp/testdino-runs && cp -r /tmp/testdino-runs/testdino/skills/testdino-runs ~/.claude/skills/testdino-runsSKILL.md
# TestDino Test Runs Use TestDino tools when the user wants to inspect automated test results. Preferred flow: 1. Call `health` if `projectId` is not known. 2. Use `list_testruns` to find the relevant run. 3. Use `get_run_details` for one specific run. 4. Use `list_testcase` or `get_testcase_details` for deeper failure analysis. 5. Use `debug_testcase` when the user wants historical debugging context for a failing test. Good requests for this skill: - show failed runs on a branch - inspect flaky tests - summarize one test run - debug a failing testcase with history Common filters from the docs: - branch - time interval - author - commit - environment - status - browser - error category - tags Use `list_testruns` first when the user does not already know the exact run ID or counter. Use `debug_testcase` when the user wants root-cause analysis and recommendations across historical runs, not just a single-run snapshot. Use `health` at the start of a session when the project is still ambiguous.
Explain a topic like I'm a 5 year old. Use when the user types /eli5 <topic> or asks for a dead-simple picture explainer of how something works.
Use the `quickdesign` CLI to generate AI media — UGC promo videos, image edits, product creatives, video upscales — through Seedance, Kling, Sora2, Nano Banana, and GPT Image. Invoke this skill whenever the user asks for a talking-avatar video, multi-segment ad / promo / explainer, image edit (object swap, angle change, state change), product photoshoot, or video upscale via QuickDesign.
Use only when the user explicitly asks for a TestDino audit of Playwright automated test code. Routes through the audit tools the TestDino MCP server exposes (get_audit_report + submit_audit_report, or the legacy test_audit). For generic code review or non-Playwright targets, do a normal review instead.
Use when the user wants to check TestDino connection status, validate their PAT, discover available organizations and projects, or find the right projectId. Always call this first when the project context is ambiguous before any other TestDino tool.
Use when the user wants to manage a manual execution run or update case-level results inside a run — listing runs, creating runs for a release, inspecting a run, assigning cases, or marking case results (passed/failed/blocked/skipped/retest/untested). Accepts counter-style IDs like RUN-12 and TC-156.
Use when the user wants to create, update, or browse manual QA test cases and suites in TestDino — not execution runs. Covers list_manual_test_suites, list_manual_test_cases, get_manual_test_case, create_manual_test_case, update_manual_test_case, create_manual_test_suite.
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers list_releases, get_release, create_release, and update_release. Accepts counter-style IDs like MS-12.
Use when the user wants to browse, inspect, create, or update exploratory testing sessions in TestDino — by state, status, session type, assignee, release, or tags. Covers list_sessions, get_session, create_session, and update_session. Accepts counter-style IDs like SES-12.