testdino-runs — Claude Code skill: inspect and debug test runs
testdino-runs brings TestDino test-run data into Claude: find failed or flaky tests, read one run's details, and trace a failure through its history.
MIT ★ 4,931 updated 2026-10-24
/plugin marketplace add anthropics/claude-plugins-community
/plugin install testdino@claude-communityWhat testdino-runs does
The skill wires TestDino tools into Claude and gives the agent an order to use them in. list_testruns locates a run, get_run_details opens that one run, and list_testcase or get_testcase_details goes deeper into a single test.
You can narrow the search by branch, author, commit, environment, browser, status, error category, tags and a time interval. When projectId is unclear, the session starts with health; without that call the agent has no project to query.
Use debug_testcase for root-cause work across past runs. A get_run_details call only describes one run. That gap shows up on flaky tests, where a single snapshot hides the pattern.
What it helps with
- find failed runs on a branch
- filter flaky tests by browser or environment
- get root-cause context for a failing test
- summarize a single run
- narrow test cases by author or tag
Example prompts for the agent
- Show me the failed runs on
mainand tell me what broke. - Which tests are flaky in the
stagingenvironment? - Debug
checkout.spec.tsusing its past runs.
How to install testdino-runs
1Plugin marketplace
/plugin marketplace add anthropics/claude-plugins-community/plugin install testdino@claude-communityThis installs the whole testdino plugin with all its skills
2Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill testdino-runs -a claude-code3Manually: put the files in place
~/.claude/skills/testdino-runs/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/testdino-runs/
1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill testdino-runs -a codex2Manually: put the files in place
.agents/skills/testdino-runs/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill testdino-runs -a cursor2Manually: put the files in place
.cursor/skills/testdino-runs/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/claude-plugins-community testdino/skills/testdino-runs2Manually: put the files in place
.github/skills/testdino-runs/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill testdino-runs -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/claude-plugins-community --path testdino/skills/testdino-runsManually: put the files in place
.devin/skills/testdino-runs/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about testdino-runs
How do I install testdino-runs in Claude Code?
Run /plugin marketplace add anthropics/claude-plugins-community, then /plugin install testdino@claude-community.
What does testdino-runs do?
It gives the agent TestDino tools for automated test results: finding runs, reading one run's details, listing test cases and tracing a failure through history.
When should I use debug_testcase instead of get_run_details?
debug_testcase looks across past runs for a root cause and recommendations; get_run_details returns one run as a snapshot.
Source text
SKILL.md · MIT
--- name: testdino-runs description: 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. --- # 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 `list_testruns` to find the relevant run. 3. Use `get_run_details` for one specific run. 4. Use `list_testcase` or `get_testcase_details` for deeper failure analysis. 5. Use `debug_testcase` 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 `list_testruns` first when the user does not already know the exact run ID or counter. Use `debug_testcase` 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.
© TestDino · MIT · anthropics/claude-plugins-community