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.
SkillScore65Maintained
Automatic
◆QA & Test Engineering pack
Last verified 9/28/2026
What it changes
Passed 12 of 19 test cases with the skill, and 8 of 19 without it.
Without skill43%
With skill65%
Checks it passed that the model alone missed
specifies calling health first when the project ID is unknown
utilizes status and type filter fields on list_manual_test_cases
invokes create_manual_test_suite before calling create_manual_test_case
and 4 more in the full report
7 fixed8 passed either way6 still failing2 broke
Pass-rate lift
+22 pp
Tokens
-13%
Agent turns
0%
Response time
-31%
Model gemini-3.6-flashMeasured 9/28/2026v115 of 23 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
I need to add a manual test case for resetting password via email link in TestDino, but I do not know the current projectId. What tool call must be performed first before searching suites or creating cases?
What was checked, without and with the skill
Checked
Without skill
With skill
specifies calling health first when the project ID is unknown
Missed
Passed
case-07 · gemini-3.6-flash · 9/28/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md43 linessingle file
TestDino Manual Tests
Use TestDino manual-test tools when the user wants to create, update, or browse manual QA cases and suites.
Preferred flow:
Call health if projectId is not known.
Use list_manual_test_suites to find the destination suite when needed.
Use list_manual_test_cases or get_manual_test_case to inspect existing cases.
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.