testdino-releases — Claude Code skill: what it does, how to install
Manage TestDino releases and milestones directly in Claude Code. Inspect existing iterations, filter lists, or create new project targets.
MIT ★ 4,931 updated 2026-10-24
/plugin marketplace add anthropics/claude-plugins-community
/plugin install testdino@claude-communityWhat testdino-releases does
This skill provides list_releases, get_release, create_release, and update_release actions for TestDino projects. When the agent lacks a known projectId, the standard flow calls health first. Target releases can be referenced through raw database IDs or counter-based identifiers like MS-12.
Payload formatting demands precision. Parameter linkedIssues must be submitted as a JSON array during creation and updates. Lowercase canonical values are the safest choice for type, even though display variants are accepted.
What it helps with
- fetch details for counter-based releases like
MS-12 - create milestone records for sprints and iterations
- update release schedules and deployment status
- filter project release histories
Example prompts for the agent
- Show details for release MS-12 in TestDino
- Create an iteration release for the current sprint
- List all releases available in the active project
How to install testdino-releases
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-releases -a claude-code3Manually: put the files in place
~/.claude/skills/testdino-releases/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/testdino-releases/
1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill testdino-releases -a codex2Manually: put the files in place
.agents/skills/testdino-releases/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill testdino-releases -a cursor2Manually: put the files in place
.cursor/skills/testdino-releases/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/claude-plugins-community testdino/skills/testdino-releases2Manually: put the files in place
.github/skills/testdino-releases/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/claude-plugins-community --skill testdino-releases -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/claude-plugins-community --path testdino/skills/testdino-releasesManually: put the files in place
.devin/skills/testdino-releases/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-releases
How to install testdino-releases in Claude Code?
Run /plugin marketplace add anthropics/claude-plugins-community in Claude Code, then run /plugin install testdino@claude-community.
What does testdino-releases do?
It connects Claude Code to TestDino release management tools to inspect and update project milestones.
What identifier format is required for releaseId?
The tools take either internal database IDs or counter-style names like MS-12.
Source text
SKILL.md · MIT
--- name: testdino-releases description: Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers list_releases, get_release, create_release, and update_release. Accepts counter-style IDs like MS-12. --- # TestDino Releases Use TestDino release tools when the user wants to browse, inspect, create, or update releases in a project. Preferred flow: 1. Call `health` if `projectId` is not known. 2. Use `list_releases` when the user needs discovery, filtering, or release lookup. 3. Use `get_release` when the user already has a specific `releaseId` or needs full release details. 4. Use `create_release` or `update_release` for release changes. Important details: - `releaseId` accepts either the internal ID or a counter-style ID like `MS-12`. - `type` accepts either display form or canonical form, but canonical lowercase values are safest. - `linkedIssues` must be sent as a JSON array for create and update operations. Good requests for this skill: - list releases in a project - show details for release MS-12 - create a sprint or iteration release - update release dates or status
© TestDino · MIT · anthropics/claude-plugins-community