mcpbeat Sign in

Testdino Audit Skill for Claude

by anthropics

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.

543 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
336
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/anthropics/claude-plugins-community --skill testdino-audit

The instruction itself

1 sections, as written by the author

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:

  • 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: get_audit_report with action: "context".
  • Legacy: test_audit with action: "analyze" and no score.
  • Review the local Playwright target using the returned context and write findings to a local markdown file (e.g. TEST-AUDIT.md).
  • Submit the completed report (score + markdown report).
  • New tools: submit_audit_report.
  • Legacy: test_audit with action: "analyze" plus score and markdownReport.
  • 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

Other skills for the same job

different authors, same section of the catalogue
Review
by ComeOnOliver

>- Review Playwright tests for quality. Use when user says "review tests", "check test quality", "audit tests", "improve tests", "test code review", or "playwright best practices check".

773 tokens
Selector Drift Recovery
by petrkindlmann

>- Bulk-regenerate broken test selectors after a UI refactor or redesign. Detects drift between old and new DOM with an aria-snapshot diff, maps old locators to new equivalents using role-first + region scoping, validates against the new build, and produces a single PR with grouped per-file selector updates and per-change evidence. Assumes Playwright >= 1.50 (trace viewer DOM-snapshot "redesign broke tests," "bulk update selectors," "regenerate selectors after after a framework switch (Selenium to Playwright) — use test-migration.

9k tokens
Receiving Code Review
by ZhanlinCui
×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens
Notebooklm
by ZhanlinCui
×6

Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.

26k tokens scripts
Requesting Code Review
by ZhanlinCui
×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

2k tokens
Playwright Skill
by lackeyjb
×4

Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.

12k tokens scripts
Git Commit
by github
vendor ×3

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

799 tokens
Github Code Review
by ComeOnOliver
×3

Comprehensive GitHub code review with AI-powered swarm coordination

13k tokens

How to use it

Copy the folder

Take anthropics/testdino-audit from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.