testdino-manual-runs
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.
git clone --depth 1 https://github.com/anthropics/claude-plugins-community /tmp/testdino-manual-runs && cp -r /tmp/testdino-manual-runs/testdino/skills/testdino-manual-runs ~/.claude/skills/testdino-manual-runsSKILL.md
# TestDino Manual Runs Use TestDino manual-run tools when the user wants to manage a manual execution run or update case-level results inside a run. Preferred flow: 1. Call `health` if `projectId` is not known. 2. Use `list_manual_runs` to discover runs by name, state, release, environment, or tags. 3. Use `get_manual_run` to inspect one run's metadata and rollup stats. 4. Use `create_manual_run` or `update_manual_run` for run-level metadata changes. 5. Use `list_run_test_cases` before changing any individual case in a run. 6. Use `update_run_test_case` to assign a case, change its result, or update elapsed time. Important details: - `runId` accepts an internal ID or a counter-style ID like `RUN-12`. - `rtcRef` can be the run test case row ID, case key like `TC-156`, or the underlying test case ID. - `updates.assigneeUserId` can be a user ID or email address. - `updates.result` accepts display form or canonical form, but canonical values like `passed`, `failed`, `blocked`, `skipped`, `retest`, and `untested` are safest. - For create and update payloads, `tags` and `linkedIssues` must be JSON arrays. Good requests for this skill: - list manual runs for a release - create a manual run for sprint MS-12 - show all test cases in run RUN-12 - assign TC-156 in RUN-12 to alice@example.com - mark TC-156 as passed in RUN-12
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 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 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.
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.