testdino-audit
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.
git clone --depth 1 https://github.com/anthropics/claude-plugins-community /tmp/testdino-audit && cp -r /tmp/testdino-audit/testdino/skills/testdino-audit ~/.claude/skills/testdino-auditSKILL.md
# TestDino Audit Use the TestDino audit flow only when the user explicitly asks for a TestDino audit. Rules: - If the user asks for a generic review or audit, do a normal review in chat. - If the user explicitly asks for a TestDino audit and the target is Playwright code, use the audit tools below. - If the user names TestDino but the target is not Playwright code, explain that the TestDino audit flow is for Playwright automated tests and offer a normal review instead. Tool selection — use whichever audit tools the TestDino MCP server exposes: - If `get_audit_report` and `submit_audit_report` are available, prefer those (the current split tools). - If only the legacy `test_audit` tool is available, use it instead (it takes an `action` parameter). - Do not invent a tool that is not in the available tool list. Preferred flow: 1. Call `health` if `projectId` is not known. 2. Fetch the audit context (read-only). Do not write findings, score, or headings before this returns. - New tools: `get_audit_report` with `action: "context"`. - Legacy: `test_audit` with `action: "analyze"` and no `score`. 3. Review the local Playwright target using the returned context and write findings to a local markdown file (e.g. `TEST-AUDIT.md`). 4. Submit the completed report (score + markdown report). - New tools: `submit_audit_report`. - Legacy: `test_audit` with `action: "analyze"` plus `score` and `markdownReport`. 5. Browse or retrieve previously submitted audits. - New tools: `get_audit_report` with `action: "list"` or `action: "get"`. - Legacy: `test_audit` with `action: "list"` or `action: "get"`. Important: - keep generic reviews as normal chat reviews - use the TestDino audit flow only for explicit TestDino audit requests - keep this flow centered on Playwright automated test code
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 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 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.