mcpbeat

Testdino Runs

anthropics/testdino-runs

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.

342 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-runs

The instruction itself

1 sections, as written by the author

TestDino Test Runs

Use TestDino tools when the user wants to inspect automated test results.

Preferred flow:

  • Call health if projectId is not known.
  • Use list_testruns to find the relevant run.
  • Use get_run_details for one specific run.
  • Use list_testcase or get_testcase_details for deeper failure analysis.
  • 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.

How to use it

Copy the folder

Take anthropics/testdino-runs 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.