cli-release

Release and recover first-party Composio CLI binaries through Build CLI Binaries, including automatic beta builds, promote-stable dispatches, beta-tag selection, asset and installation verification, and failed release recovery. Use when a contributor asks to build a CLI beta, publish or promote a stable CLI version, choose a release candidate, monitor a CLI release, or diagnose a failed CLI release. Do not use for TypeScript SDK Changesets releases or CLI source implementation.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%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.

A clean, well-architected skill body that pairs critical guardrails with a clear execution sequence and a single well-signaled reference. The chief weakness is that actionable commands and the error-recovery feedback loop are deferred to the reference rather than surfaced in the body.

Suggestions

Add a one-line inline example of the core dispatch command (e.g., the `gh workflow run build-cli-binaries.yml ... action=promote-stable` form) so the most common action is executable without opening the reference.

State an explicit recovery feedback loop in the body (verify → if failed, inspect draft and re-dispatch with --clobber) rather than only classifying 'recovery' as a request type.

Reference the playbook's specific validation checkpoints (the six required assets and installation-test matrix) by name in the body's verify step so the checkpoint is concrete without duplicating the full command.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense — a short contract of guardrail bullets plus a tight 5-step execution list — with no padding or explanation of concepts Claude already knows, so every token earns its place.	5 / 5
Actionability	The phased guidance is concrete and specific (preflight, identify commit/tag, dispatch the single requested action, verify, report), but the actual executable commands live in the referenced playbook rather than the body itself, leaving minor gaps.	4 / 5
Workflow Clarity	A clearly sequenced 5-step workflow with explicit verification (step 4) and a pre-dispatch confirmation checkpoint is present, but the validate→fix→retry feedback loop for this production-write operation is delegated to the reference rather than stated in the body.	4 / 5
Progressive Disclosure	The body is a concise overview that signals a single one-level-deep reference ('Read references/release-workflow.md...'), which exists and is itself well-organized with no nested references, matching the anchor 5 pattern.	5 / 5
	Total	18 / 20 Passed

Description

92%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.

A strong, well-structured description that concretely states capabilities and gives explicit, natural trigger conditions plus a clear out-of-scope boundary. The only gap is minor synonym coverage in the trigger phrasing.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'automatic beta builds, promote-stable dispatches, beta-tag selection, asset and installation verification, and failed release recovery' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	It explicitly answers both 'what' (release and recover CLI binaries through Build CLI Binaries with enumerated sub-actions) and 'when' (a concrete 'Use when a contributor asks to...' clause), matching the anchor 5 example.	5 / 5
Trigger Term Quality	The 'Use when' clause supplies natural phrases ('build a CLI beta', 'publish or promote a stable CLI version', 'choose a release candidate', 'diagnose a failed CLI release'), but informal synonyms such as 'ship' or 'cut a release' are not covered, so it stops short of anchor 5.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (Composio CLI binary releases) and adds an explicit boundary — 'Do not use for TypeScript SDK Changesets releases or CLI source implementation' — minimizing conflict with adjacent skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ComposioHQ/composio
Path: .agents/skills/cli-release/SKILL.md
Commit: 7a63e5a

Reviewed: 3 hours ago

Table of Contents

Discovery Implementation Validation

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.