testdino-manual-tests — Claude Code skill: setup and features
testdino-manual-tests manages manual QA test cases and suites in TestDino directly from Claude Code. It lets you create tests, update steps, and browse suites without touching execution runs.
MIT ★ 4,931 updated 2026-10-24
/plugin marketplace add anthropics/claude-plugins-community
/plugin install testdino@claude-communityWhat testdino-manual-tests does
The skill connects Claude Code to TestDino manual QA repositories through MCP tools. When projectId is missing, the agent triggers health first, then locates the target suite via list_manual_test_suites. Inspecting existing tests relies on list_manual_test_cases and get_manual_test_case, supporting filters such as priority, severity, tags, automation status, and flaky flags.
Edits and additions use create_manual_test_case, update_manual_test_case, and create_manual_test_suite. The workflow expects confirming the target suite before adding a case. Updates send only modified fields to avoid overwriting existing properties, while tags require structured arrays in the payload.
Test runs stay out of scope. Execution workflows belong to dedicated run tools rather than this case-management skill.
What it helps with
- Create new test suites and test cases in TestDino
- Update preconditions, steps, or postconditions in existing cases
- Filter manual tests by priority, tags, severity, or flaky status
- Add tags and metadata without overwriting untouched fields
Example prompts for the agent
- Create a manual test case for checkout validation in the Billing suite
- List all flaky manual test cases with high priority in TestDino
- Update the steps and preconditions for the authentication test case
How to install testdino-manual-tests
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-tests -a claude-code3Manually: put the files in place
~/.claude/skills/testdino-manual-tests/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/testdino-manual-tests/
1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill testdino-manual-tests -a codex2Manually: put the files in place
.agents/skills/testdino-manual-tests/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill testdino-manual-tests -a cursor2Manually: put the files in place
.cursor/skills/testdino-manual-tests/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/claude-plugins-community testdino/skills/testdino-manual-tests2Manually: put the files in place
.github/skills/testdino-manual-tests/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill testdino-manual-tests -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/claude-plugins-community --path testdino/skills/testdino-manual-testsManually: put the files in place
.devin/skills/testdino-manual-tests/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-tests
How do I install testdino-manual-tests in Claude Code?
Run /plugin marketplace add anthropics/claude-plugins-community in Claude Code, then execute /plugin install testdino@claude-community. Alternatively, install it with npx skills add anthropics/claude-plugins-community --skill testdino-manual-tests -a claude-code.
What does testdino-manual-tests do?
It creates, browses, and updates manual QA test suites and test cases in TestDino. It handles filters by tags, priority, severity, and automation status.
Can I execute manual test runs with this skill?
No, this skill only manages cases and suites. Running test executions requires separate TestDino run tools.
Source text
SKILL.md · MIT
--- name: testdino-manual-tests description: Use when the user wants to create, update, or browse manual QA test cases and suites in TestDino — not execution runs. Covers list_manual_test_suites, list_manual_test_cases, get_manual_test_case, create_manual_test_case, update_manual_test_case, create_manual_test_suite. --- # TestDino Manual Tests Use TestDino manual-test tools when the user wants to create, update, or browse manual QA cases and suites. Preferred flow: 1. Call `health` if `projectId` is not known. 2. Use `list_manual_test_suites` to find the destination suite when needed. 3. Use `list_manual_test_cases` or `get_manual_test_case` to inspect existing cases. 4. Use `create_manual_test_case`, `update_manual_test_case`, or `create_manual_test_suite` for edits. Boundary: - This skill is for manual test cases and suites. - Manual execution runs are a separate workflow and should use the manual-run tools. Good requests for this skill: - create a manual test case - update preconditions or steps - list manual cases in a suite - create a new manual test suite Common filters from the docs: - search - suite - status - priority - severity - type - layer - behavior - automation status - tags - flaky flag When creating a case: - confirm or resolve the target suite first - include steps, preconditions, and postconditions when the user provides them - preserve existing fields on updates by sending only the fields that should change - send structured arrays for fields like tags when the MCP payload requires arrays
© TestDino · MIT · anthropics/claude-plugins-community