ClaudeSuperPower
SubmitLog in

testdino-manual-runs

Skill

Use when the user wants to manage a manual execution run or update case-level results inside a run — listing runs, creating runs for a release, inspecting a run, assigning cases, or marking case results (passed/failed/blocked/skipped/retest/untested). Accepts counter-style IDs like RUN-12 and TC-156

0Other

Install

git clone https://github.com/anthropics/claude-plugins-community.git ~/.claude/skills/testdino-manual-runs

What is testdino-manual-runs?

Use when the user wants to manage a manual execution run or update case-level results inside a run — listing runs, creating runs for a release, inspecting a run, assigning cases, or marking case results (passed/failed/blocked/skipped/retest/untested). Accepts counter-style IDs like RUN-12 and TC-156.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~75 tokens of context used while enabled, before you invoke anything

Documentation

README · ~1 min read

TestDino Manual Runs

Use TestDino manual-run tools when the user wants to manage a manual execution run or update case-level results inside a run.

Preferred flow:

  1. Call health if projectId is not known.
  2. Use list_manual_runs to discover runs by name, state, release, environment, or tags.
  3. Use get_manual_run to inspect one run's metadata and rollup stats.
  4. Use create_manual_run or update_manual_run for run-level metadata changes.
  5. Use list_run_test_cases before changing any individual case in a run.
  6. Use update_run_test_case to assign a case, change its result, or update elapsed time.

Important details:

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.