testdino-manual-runs — Claude Code skill: install
Manage TestDino manual runs and case-level results from Claude Code. Use it to create runs, inspect their contents, assign cases, or record outcomes.
MIT ★ 4,931 updated 2026-10-24
/plugin marketplace add anthropics/claude-plugins-community
/plugin install testdino@claude-communityWhat testdino-manual-runs does
This skill handles TestDino manual execution runs. It can find runs by name, state, release, environment, or tags; create one for a release; and inspect its metadata together with rollup figures. It also lists the cases attached to a run, assigns them to users, and changes a case result or elapsed time.
The workflow uses health, list_manual_runs, get_manual_run, create_manual_run, update_manual_run, list_run_test_cases, and update_run_test_case. Run references may be internal IDs or values such as RUN-12; a case row accepts its row ID, a key such as TC-156, or the underlying case ID. Results include passed, failed, blocked, skipped, retest, and untested. Send tags and linkedIssues as JSON arrays.
When projectId is not known, the workflow starts with health. That requirement affects the first request the skill makes.
What it helps with
- find manual runs by release or environment
- create a run for a release
- inspect the cases in
RUN-12 - assign
TC-156to a user - record a
passedresult for a case
Example prompts for the agent
- List the manual runs for release
MS-12. - Create a manual run for release
MS-12. - Assign
TC-156inRUN-12to[email protected]and mark itpassed.
How to install testdino-manual-runs
1Plugin marketplace
/plugin marketplace add anthropics/claude-plugins-community/plugin install testdino@claude-communityThis installs the whole testdino plugin with all its skills
2Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill testdino-manual-runs -a claude-code3Manually: put the files in place
~/.claude/skills/testdino-manual-runs/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/testdino-manual-runs/
1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill testdino-manual-runs -a codex2Manually: put the files in place
.agents/skills/testdino-manual-runs/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill testdino-manual-runs -a cursor2Manually: put the files in place
.cursor/skills/testdino-manual-runs/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/claude-plugins-community testdino/skills/testdino-manual-runs2Manually: put the files in place
.github/skills/testdino-manual-runs/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill testdino-manual-runs -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/claude-plugins-community --path testdino/skills/testdino-manual-runsManually: put the files in place
.devin/skills/testdino-manual-runs/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about testdino-manual-runs
How do I install testdino-manual-runs in Claude Code?
Add the marketplace with /plugin marketplace add anthropics/claude-plugins-community, then install the plugin with /plugin install testdino@claude-community.
What does testdino-manual-runs do?
It manages TestDino manual runs: discovering and creating runs, viewing their rollups, assigning test cases, and changing case outcomes.
Which references and outcomes can the skill handle?
A run can be addressed with an internal ID or a value such as RUN-12. A case can use TC-156, its run-row ID, or the underlying case ID, with outcomes such as passed, failed, blocked, skipped, retest, and untested.
Source text
SKILL.md · MIT
--- name: testdino-manual-runs description: 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. --- # 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: - `runId` accepts an internal ID or a counter-style ID like `RUN-12`. - `rtcRef` can be the run test case row ID, case key like `TC-156`, or the underlying test case ID. - `updates.assigneeUserId` can be a user ID or email address. - `updates.result` accepts display form or canonical form, but canonical values like `passed`, `failed`, `blocked`, `skipped`, `retest`, and `untested` are safest. - For create and update payloads, `tags` and `linkedIssues` must be JSON arrays. Good requests for this skill: - list manual runs for a release - create a manual run for sprint MS-12 - show all test cases in run RUN-12 - assign TC-156 in RUN-12 to [email protected] - mark TC-156 as passed in RUN-12
© TestDino · MIT · anthropics/claude-plugins-community