testdino-runs Skill
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 listtestruns, getrundetails, listtestcase, gettestcasedetails, and debugtestcase. Published by anthropics in claude-plugins-community.
What is testdino-runs Skill?
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 listtestruns, getrundetails, listtestcase, gettestcasedetails, and debugtestcase. 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
- Documentation
- Data analysis
- Browser automation use cases
Technical details
- Install or run with Copy skill directory
When to use testdino-runs Skill
- Use it for browser automation.
- Use it for testing.
- Use it for documentation.
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/claude-plugins-community
- Skill file: testdino/skills/testdino-runs/SKILL.md
What it does
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 listtestruns, getrundetails, listtestcase, gettestcasedetails, and debugtestcase.
Skill instructions
TestDino Test Runs Use TestDino tools when the user wants to inspect automated test results. Preferred flow: 1. Call health if projectId is not known. 2. Use listtestruns to find the relevant run. 3. Use getrundetails for one specific run. 4. Use listtestcase or gettestcasedetails for deeper failure analysis. 5. Use debugtestcase when the user wants historical debugging context for a failing test. Good requests for this skill: - show failed runs on a branch - inspect flaky tests - summarize one test run - debug a failing testcase with history Common filters from the docs: - branch - time interval - author - commit - environment - status - browser - error category - tags Use listtestruns first when the user does not already know the exact run ID or counter. Use debugtestcase when the user wants root-cause analysis and recommendations across historical runs, not just a single-run snapshot. Use health at the start of a session when the project is still ambiguous.
Explore related resources
Frequently asked questions
What is testdino-runs?
testdino-runs is a open-source AI agent skill with Copy skill directory. 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.
Who is testdino-runs best for?
testdino-runs is best for reusing agent instructions, scripts, and references, browser automation workflows, testing workflows, documentation workflows.
How do I install testdino-runs?
Install or run testdino-runs using Copy skill directory. Check testdino-runs for the latest setup command.
Is testdino-runs actively maintained?
testdino-runs may need a closer maintenance check before production use.
Auto-fetched from GitHub.
