Download for macOS
Skill

testdino-runs

@testdino-hq Updated 2026-06-23

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.

ai-testingautomationci-cddeveloper-toolsmcpplaywrightplaywright-testingqa

Install

With your agent

Install OMGSkills skill "testdino-hq/testdino-plugins:skills/testdino-runs" into this agent's normal skills directory: use the OMGSkills MCP get_skill tool, install only the pinned_install commit and path, verify SKILL.md against pinned_install.skill_md_sha, and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/testdino-hq/TestDino-Plugins /tmp/TestDino-Plugins && ln -s /tmp/TestDino-Plugins/skills/testdino-runs ~/.claude/skills/testdino-runs

From README

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 listtestruns to find the relevant run. Use getrundetails for one specific run. Use listtestcase or gettestcasedetails for deeper failure analysis. 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.