Index of every page on this site: llms.txt
All skills
anthropics avatar

/testdino-runs

@163301d
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/anthropics/claude-plugins-community/testdino-runs

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈82 tokens for metadata: the name and description. ≈254 when used: this file.

Description uses 4.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈328 characters, or 4.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    This skill provides instructions for interacting with test run analysis tools. No security issues were detected during the analysis.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: LOW · No issues

Signed by skilld at 163301d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 5 months ago

README badge

README badge for anthropics/claude-plugins-community/testdino-runs