CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

team-release

Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/team-release/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exceptionally well-engineered orchestration pipeline: every phase has an owner, an output destination, a decision gate, and a failure path, and the irreversible deploy step is unconditionally gated. Its weaknesses are verbosity in the justificational essays and the absence of any content split into reference files, both of which cost tokens without costing clarity.

DimensionReasoningScore

Conciseness

The body is mostly dense, project-specific policy (exact paths, prompts, option labels) with no padding about concepts Claude already knows, but several multi-paragraph justification blocks — the active-set collapse rationale ('The collapse is correct... a reader cannot distinguish...'), the Collaboration Protocol exception, and the announce-the-active-set essay — explain why rules are correct at length where a tighter statement would do. That is 'mostly efficient but includes some unnecessary explanation or could be tightened', not the minor-trim level of 4.

3 / 5

Actionability

Guidance is highly concrete: exact AskUserQuestion prompts with option labels ('[A] Stop — I'll run /gate-check release'), a full table of per-agent output paths, exact record strings for overrides, a return-contract template, and one executable bash command. It falls short of fully copy-paste-ready because several delegation bullets remain high-level directives ('Confirm all milestone acceptance criteria are met', 'Run automated tests in CI'), leaving minor gaps for the orchestrator.

4 / 5

Workflow Clarity

Seven phases are clearly sequenced with explicit validation checkpoints and feedback loops: the Phase 0 stage check stops everything before spawning, every phase transition is a decision point, the Error Recovery Protocol verifies the named artifact before treating a phase as done and resumes naming the unmet contract, and NO-GO triggers an explicit option set that skips Phase 6. Destructive operations (production deploy) are guarded by an unconditional approval gate, so no cap applies.

5 / 5

Progressive Disclosure

Structure is good: well-organized sections, a destination table, and clearly signaled one-level-deep references to external docs (.claude/docs/automation-modes.md, config-resolution.md, error-recovery-protocol.md). It is not a 5 because no content is split out of SKILL.md — the long rationale blocks and the error-recovery common blockers could live in reference files — and not a 3 because what is inline is well-sectioned and references are clearly flagged, not buried.

4 / 5

Total

16

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description communicates a clear, well-scoped 'what' — orchestrating a named release team from candidate to deployment — and is appropriately concise. Its main weakness is the complete absence of any 'when to use' trigger guidance, and its keyword coverage misses common release synonyms (ship, launch, publish).

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to release, ship, or deploy a version, or to run the release pipeline.'

Include natural synonyms users would actually say — ship, launch, publish, go live — alongside 'release' and 'deployment'.

List one or two more concrete actions (e.g., 'bump versions, run the QA gate, tag and deploy') to round out the capability coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Orchestrate the release team') and one concrete macro action ('execute a release from candidate to deployment'), plus the agent roster — that is 1-2 concrete actions, matching the anchor for a clear but non-comprehensive action list. It does not list several specific actions (version bump, changelog, QA gate, deploy), so it is not a 4.

3 / 5

Completeness

The 'what' is clear (orchestrate the named team to take a release from candidate to deployment), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines. The 'when' is only weakly implied by the word 'release', not explicitly stated.

3 / 5

Trigger Term Quality

'release', 'release team', and 'deployment' are natural terms a user would say, but common variations like 'ship', 'launch', 'publish', or 'go live' are absent, matching 'some relevant keywords but missing common variations or synonyms'. Coverage is above the single-keyword anchor 3 example yet short of the near-complete coverage anchor 5 requires.

3 / 5

Distinctiveness Conflict Risk

Naming the specific agent roster (release-manager, qa-lead, devops-engineer, producer) carves a clear niche with distinct triggers and minimal conflict risk. It is not a 5 because in a suite of team-orchestration skills (e.g., a sibling narrative-team orchestrator) the shared 'orchestrate the team' framing creates minor overlap risk.

4 / 5

Total

13

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/team-release/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.