testdino-sessions Skill
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 listsessions, getsession, createsession, and updatesession. Accepts counter-style IDs like SES-12. Published by anthropics in claude-plugins-community.
Decision snapshot
Is this a fit?
Testing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
15 days ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is testdino-sessions Skill?
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 listsessions, getsession, createsession, and updatesession. Accepts counter-style IDs like SES-12. Published by anthropics in claude-plugins-community. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Testing use cases
Declared skill metadata
- Source file: testdino/skills/testdino-sessions/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use testdino-sessions Skill
- Use it for testing.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/claude-plugins-community
- Skill file: testdino/skills/testdino-sessions/SKILL.md
What it does
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 listsessions, getsession, createsession, and updatesession. Accepts counter-style IDs like SES-12.
Skill instructions
TestDino Exploratory Sessions Use TestDino session tools when the user wants to browse, inspect, create, or update exploratory testing sessions. Preferred flow: 1. Call health if projectId is not known. 2. Use listsessions to discover sessions by state, status, session type, assignee, release, or tags. 3. Use getsession to inspect one session in detail. 4. Use createsession or updatesession 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. Good requests for this skill: - list exploratory sessions in a project - create an exploratory session for auth regression - assign a session to alice@example.com - update session state to under review
Verified compatibility and discovery
Frequently asked questions
What is testdino-sessions?
testdino-sessions is a open-source AI agent skill with Copy skill directory. 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.
Who is testdino-sessions best for?
testdino-sessions is best for reusing agent instructions, scripts, and references, testing workflows.
How do I install testdino-sessions?
Install or run testdino-sessions using Copy skill directory. Check testdino-sessions for the latest setup command.
Is testdino-sessions actively maintained?
testdino-sessions may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
