# Available Skills for the TestDino Plugin: Complete Claude Code Integration Guide

> Explore the seven TestDino plugin skills: testdino-health, testdino-sessions, testdino-runs, testdino-releases, testdino-manual-tests, testdino-manual-runs, and testdino-audit. Manage your testing with Claude Code.

- Repository: [Anthropic/claude-plugins-community](https://github.com/anthropics/claude-plugins-community)
- Tags: how-to-guide
- Published: 2026-08-29

---

**The TestDino plugin exposes seven distinct skills—`testdino-health`, `testdino-sessions`, `testdino-runs`, `testdino-releases`, `testdino-manual-tests`, `testdino-manual-runs`, and `testdino-audit`—that enable Claude Code to manage exploratory sessions, automated test runs, manual QA suites, and Playwright code audits through declarative markdown descriptors.**

The **TestDino plugin** in the `anthropics/claude-plugins-community` repository extends Claude Code with specialized capabilities for test management workflows. Each available skill for the TestDino plugin is defined in a dedicated markdown descriptor file ([`SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/SKILL.md)) that the Claude plugin system reads at runtime, exposing cohesive API operations for interacting with TestDino data. All skills follow a common execution pattern: begin with the **`health`** skill to verify connectivity and obtain your `projectId`, then invoke specific operations to query or mutate testing objects.

## Understanding TestDino Plugin Skill Architecture

The plugin architecture separates concerns into discrete, discoverable units. The entry point metadata resides in [`testdino/.claude-plugin/plugin.json`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/.claude-plugin/plugin.json), which declares the plugin name, description, and repository location. Marketplace registration is handled in [`testdino/.claude-plugin/marketplace.json`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/.claude-plugin/marketplace.json), making the plugin discoverable within the Claude ecosystem.

Each skill is physically isolated in its own directory under `testdino/skills/`. Within these directories, the [`SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/SKILL.md) file defines the **skill name**, **human-readable description**, **available operations**, and the **recommended usage flow**. At runtime, Claude parses these descriptors to surface the appropriate tool calls to the user, requiring no additional configuration beyond plugin installation.

## The Seven Available Skills for the TestDino Plugin

### 1. testdino-health: Connection and Project Discovery

The **`testdino-health`** skill is the mandatory entry point for all TestDino plugin workflows. Defined in [`testdino/skills/testdino-health/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-health/SKILL.md), this skill verifies API connectivity and discovers available organizations and projects.

**Core operations:**
- `health` – Returns connection status and the `projectId` required for subsequent calls.

Always invoke this skill first when the project context is unknown, as the returned `projectId` parameter is required for most other operations.

### 2. testdino-sessions: Exploratory Testing Management

The **`testdino-sessions`** skill manages **exploratory testing sessions**, allowing teams to browse, inspect, create, and update ad-hoc testing activities. The skill descriptor lives at [`testdino/skills/testdino-sessions/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-sessions/SKILL.md).

**Core operations:**
- `list_sessions` – Retrieves all sessions filtered by project and state.
- `get_session` – Fetches detailed metadata for a specific session ID.
- `create_session` – Initializes a new exploratory session with title, assignee, and tags.
- `update_session` – Modifies existing session properties.

### 3. testdino-runs: Automated Test Run Inspection

The **`testdino-runs`** skill provides deep visibility into **automated test executions**, including the ability to debug failing test cases with historical context. This skill is defined in [`testdino/skills/testdino-runs/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-runs/SKILL.md).

**Core operations:**
- `list_testruns` – Lists test runs filtered by project, branch, and status.
- `get_run_details` – Retrieves comprehensive metadata for a specific run.
- `list_testcase` – Enumerates test cases within a run.
- `get_testcase_details` – Fetches detailed information about a specific test case.
- `debug_testcase` – Initiates a debug workflow for failing test cases, including historical failure analysis.

### 4. testdino-releases: Milestone and Release Tracking

The **`testdino-releases`** skill handles **release and milestone management**, enabling teams to track software iterations. The definition is located at [`testdino/skills/testdino-releases/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-releases/SKILL.md).

**Core operations:**
- `list_releases` – Displays all releases for a given project.
- `get_release` – Retrieves details for a specific release.
- `create_release` – Creates a new release or milestone with title, type, and due date.
- `update_release` – Modifies existing release attributes.

### 5. testdino-manual-tests: Manual QA Case Management

The **`testdino-manual-tests`** skill manages **manual QA test cases and suites** without executing them. This skill is distinct from test execution and is defined in [`testdino/skills/testdino-manual-tests/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-manual-tests/SKILL.md).

**Core operations:**
- `list_manual_test_suites` – Enumerates available test suites.
- `list_manual_test_cases` – Lists cases within a specific suite.
- `get_manual_test_case` – Retrieves detailed case specifications including steps.
- `create_manual_test_case` – Defines new test cases with step sequences.
- `update_manual_test_case` – Edits existing case definitions.
- `create_manual_test_suite` – Initializes new test suites for organization.

### 6. testdino-manual-runs: Manual Test Execution Control

The **`testdino-manual-runs`** skill manages **manual execution runs** and updates case-level results. This complements the `testdino-manual-tests` skill by handling the runtime aspect of manual testing. The descriptor is at [`testdino/skills/testdino-manual-runs/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-manual-runs/SKILL.md).

**Core operations:**
- `list_manual_runs` – Shows all manual execution runs.
- `get_manual_run` – Retrieves details of a specific run.
- `create_manual_run` – Initiates a new manual test run based on a suite.
- `update_manual_run` – Modifies run metadata.
- `update_manual_run_case` – Records pass/fail results and notes for individual cases within a run.

### 7. testdino-audit: Playwright Code Analysis

The **`testdino-audit`** skill provides a **Playwright-specific audit flow** for analyzing automated test code quality. This specialized skill is defined in [`testdino/skills/testdino-audit/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-audit/SKILL.md) and targets Playwright test files specifically.

**Core operations:**
- `get_audit_report` – Generates an audit report for a specified Playwright file.
- `submit_audit_report` – Submits audit results (legacy `test_audit` may also be available in older versions).

## Practical Usage: Calling TestDino Plugin Skills

Below are concrete Claude Code invocation patterns demonstrating the standard workflow for utilizing the available skills for the TestDino plugin. These examples assume the `plugin call` syntax illustrative of Claude Code's interface.

First, verify connectivity and establish project context:

```text

# Verify connection and obtain projectId

plugin call testdino-health health

```

Once you have the `projectId`, interact with exploratory sessions:

```text

# List open exploratory sessions

plugin call testdino-sessions list_sessions --projectId <PROJECT_ID> --state open

# Get details for a specific session

plugin call testdino-sessions get_session --sessionId SES-12

# Create a new exploratory session

plugin call testdino-sessions create_session \
  --title "Auth regression" \
  --assigneeUserId alice@example.com \
  --tags '["auth","regression"]'

```

Inspect automated test runs and debug failures:

```text

# List failed test runs on the main branch

plugin call testdino-runs list_testruns --projectId <PROJECT_ID> --branch main --status failed

# Debug a specific failing test case with historical context

plugin call testdino-runs debug_testcase --runId 987 --testcaseId "visual.spec.js"

```

Manage releases and milestones:

```text

# List all releases

plugin call testdino-releases list_releases --projectId <PROJECT_ID>

# Create a new sprint milestone

plugin call testdino-releases create_release \
  --title "Sprint 5" \
  --type milestone \
  --dueDate "2024-10-01"

```

Handle manual testing workflows:

```text

# List available manual test suites

plugin call testdino-manual-tests list_manual_test_suites --projectId <PROJECT_ID>

# Create a structured manual test case

plugin call testdino-manual-tests create_manual_test_case \
  --suiteId 42 \
  --title "Checkout flow" \
  --steps '["Open cart","Enter payment","Submit"]'

# Start a manual execution run

plugin call testdino-manual-runs create_manual_run \
  --suiteId 42 \
  --title "Checkout regression run"

```

Finally, audit Playwright-specific code:

```text

# Generate an audit report for Playwright test code

plugin call testdino-audit get_audit_report --filePath "./tests/checkout.spec.ts"

```

## Summary

The available skills for the TestDino plugin provide comprehensive test management capabilities within Claude Code:

- **`testdino-health`** – Establishes connectivity and discovers project context.
- **`testdino-sessions`** – Manages exploratory testing workflows.
- **`testdino-runs`** – Inspects automated test executions and facilitates debugging.
- **`testdino-releases`** – Tracks software milestones and release cycles.
- **`testdino-manual-tests`** – Defines manual test cases and suites without execution.
- **`testdino-manual-runs`** – Controls manual test execution and result tracking.
- **`testdino-audit`** – Analyzes Playwright test code for quality issues.

Each skill is independently maintained in its respective [`SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/SKILL.md) descriptor within the `testdino/skills/` directory, following the standard Claude plugin specification defined in the `anthropics/claude-plugins-community` repository.

## Frequently Asked Questions

### How do I start using the TestDino plugin skills in Claude Code?

Begin by invoking the **`testdino-health`** skill using `plugin call testdino-health health`. This operation verifies API connectivity and returns the `projectId` required for all subsequent skill operations. According to the source code in [`testdino/skills/testdino-health/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-health/SKILL.md), this health check is the mandatory first step when the project context is unknown.

### What is the difference between testdino-manual-tests and testdino-manual-runs?

The **`testdino-manual-tests`** skill handles the static definition of manual test cases and suites—creating test specifications, steps, and organizational structure without executing them. The **`testdino-manual-runs`** skill manages the dynamic execution phase, including creating run instances, assigning them to testers, and updating individual case results. As implemented in [`testdino/skills/testdino-manual-tests/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-manual-tests/SKILL.md) and [`testdino/skills/testdino-manual-runs/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-manual-runs/SKILL.md), these skills represent the logical separation between test design and test execution.

### Which skill should I use for analyzing Playwright test code?

Use the **`testdino-audit`** skill, specifically the `get_audit_report` operation defined in [`testdino/skills/testdino-audit/SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/skills/testdino-audit/SKILL.md). This skill is purpose-built for Playwright-specific static analysis, accepting a `filePath` parameter pointing to a [`.spec.ts`](https://github.com/anthropics/claude-plugins-community/blob/main/.spec.ts) or similar Playwright test file and returning quality and maintainability insights.

### Where are the TestDino plugin skill definitions located?

All skill definitions reside in the `testdino/skills/` directory within the `anthropics/claude-plugins-community` repository. Each skill maintains its own subdirectory (e.g., `testdino/skills/testdino-sessions/`) containing a [`SKILL.md`](https://github.com/anthropics/claude-plugins-community/blob/main/SKILL.md) markdown descriptor that Claude parses at runtime. The plugin metadata is declared in [`testdino/.claude-plugin/plugin.json`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/.claude-plugin/plugin.json), while marketplace registration is configured in [`testdino/.claude-plugin/marketplace.json`](https://github.com/anthropics/claude-plugins-community/blob/main/testdino/.claude-plugin/marketplace.json).