Use when the user wants to browse, inspect, create, or update exploratory testing sessions in TestDino — by state, status, session type, assignee, release, or tags. Covers list_sessions, get_session, create_session, and update_session. Accepts counter-style IDs like SES-12.
SkillScore22Maintained
Automatic
◆QA & Test Engineering pack
Last verified 9/28/2026
What it changes
Passed 2 of 8 test cases with the skill, and 1 of 8 without it.
Without skill13%
With skill22%
Checks it passed that the model alone missed
Invokes get_session with session ID SES-09.
Performs health check first if project identifier is missing.
Invokes list_sessions with tag accessibility and session type unscripted.
2 fixed3 passed either way18 still failing0 broke
Pass-rate lift
+9 pp
Tokens
-37%
Agent turns
0%
Response time
-40%
Model gemini-3.6-flashMeasured 9/28/2026v15 of 23 cases passed with skill · 8 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
I have session ID SES-09 in TestDino and want to inspect its full charter, notes, and attachments. Which tool call should I invoke?
What was checked, without and with the skill
Checked
Without skill
With skill
Invokes get_session with session ID SES-09.
Missed
Passed
case-12 · 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.md24 linessingle file
TestDino Exploratory Sessions
Use TestDino session tools when the user wants to browse, inspect, create, or update exploratory testing sessions.
Preferred flow:
Call health if projectId is not known.
Use list_sessions to discover sessions by state, status, session type, assignee, release, or tags.
Use get_session to inspect one session in detail.
Use create_session or update_session for session changes.
Important details:
sessionId accepts an internal ID or a counter-style ID like SES-12.
assigneeUserId accepts either a user ID or an email address.
state accepts display form or canonical form, but canonical lowercase values are safest.
tags and linkedIssues must be JSON arrays for create and update operations.
Trigger on-chain data collection (a "Commit") in Tres Finance for wallets that have already been onboarded. Use this skill whenever the user wants to collect data, pull balances, sync wallets, refresh on-chain data, run a commit, trigger a commit, or "collect" anything in Tres. This is the second step of the Tres onboarding flow — it sits between wallet upload (tres-wallets-upload) and balance validation (tres-asset-balance-validation). Always trigger this skill for any request that mentions "co