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.
Install
With your agent
Install OMGSkills skill "testdino-hq/testdino-plugins:skills/testdino-audit" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/testdino-hq/TestDino-Plugins /tmp/TestDino-Plugins && ln -s /tmp/TestDino-Plugins/skills/testdino-audit ~/.claude/skills/testdino-auditFrom README
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 getauditreport and submitauditreport are available, prefer those (the current split tools). If only the legacy testaudit 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: Call health if projectId is not known. Fetch the audit context (read-only). Do not write findings, score, or headings before this returns. New tools: getauditreport with action: "context".
More from this repo
testdino-health
Used when the user wants to check TestDino connection status, validate their PAT, discover available organizations and...
testdino-manual-runs
Used when the user wants to manage a manual execution run or update case-level results inside a run — listing runs,...
testdino-manual-tests
Used when the user wants to create, update, or browse manual QA test cases and suites in TestDino — not execution runs.