testdino-audit Skill
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 (getauditreport + submitauditreport, or the legacy testaudit). For generic code review or non-Playwright targets, do a normal review instead. Published by anthropics in claude-plugins-community.
What is testdino-audit Skill?
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 (getauditreport + submitauditreport, or the legacy testaudit). For generic code review or non-Playwright targets, do a normal review instead. Published by anthropics in claude-plugins-community. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Testing
- Security review
- Writing
- Browser automation use cases
Technical details
- Install or run with Copy skill directory
When to use testdino-audit Skill
- Use it for browser automation.
- Use it for testing.
- Use it for security review.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/claude-plugins-community
- Skill file: testdino/skills/testdino-audit/SKILL.md
What it does
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 (getauditreport + submitauditreport, or the legacy testaudit). For generic code review or non-Playwright targets, do a normal review instead.
Skill instructions
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: 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: getauditreport with a
Explore related resources
Frequently asked questions
What is testdino-audit?
testdino-audit is a open-source AI agent skill with Copy skill directory. Use only when the user explicitly asks for a TestDino audit of Playwright automated test code.
Who is testdino-audit best for?
testdino-audit is best for reusing agent instructions, scripts, and references, browser automation workflows, testing workflows, security review workflows.
How do I install testdino-audit?
Install or run testdino-audit using Copy skill directory. Check testdino-audit for the latest setup command.
Is testdino-audit actively maintained?
testdino-audit may need a closer maintenance check before production use.
Auto-fetched from GitHub.
