---
name: anthropics-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."
license: "Apache-2.0"
metadata:
  decimalai-skill-id: "b997a7fb-f94e-4682-9cc6-9f347f457253"
  decimalai-version-id: "5b1fa474-2c90-46f1-82d7-fda1cf36af24"
  decimalai-version: "1"
  decimalai-body-sha256: "447944a758d2a9316b1b512886905bf8b2373a5937b1b844f12d3779daded096"
  decimalai-name: "anthropics/testdino-runs"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "testing"
  decimalai-source: "https://app.decimal.ai/s/anthropics-testdino-runs@1/SKILL.md"
---
# 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.