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

/testdino-manual-runs

@163301d
Run it yourself

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.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈81 tokens for metadata: the name and description. ≈336 when used: this file.

Description uses 4.0% 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 ≈324 characters, or 4.0%.

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 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 alice@example.com
  • mark TC-156 as passed in RUN-12

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 safe instructions for managing manual test runs within the TestDino environment. No security risks were identified.

  • 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-manual-runs