CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

An efficient, well-structured instruction-only skill body that pairs a release contract with a sequenced execution plan and cleanly offloads detail to one reference file; the only gaps are the literal dispatch commands and an explicit recovery loop, both deferred to the playbook.

Suggestions

Inline the exact dispatch command (e.g. the gh workflow run invocation for 'promote-stable') so the body is executable without opening the reference.

Add an explicit 'if verification or install-test fails' recovery step to the Execution list to close the validate→fix→retry loop inline.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and assumes Claude's competence: no concept explanations, only contract rules and execution steps, so every token earns its place.

5 / 5

Actionability

Guidance is concrete — named workflow action 'promote-stable', named packages '@composio/cli', named file 'ts.release.yml' — but literal dispatch commands are deferred to the reference rather than being copy-paste ready in the body.

4 / 5

Workflow Clarity

A clear 5-step sequence with checkpoints (read-only preflight, watch to completion, verify, report) and an explicit confirmation gate, but the failure-to-recovery feedback loop is referenced via classification rather than spelled out inline.

4 / 5

Progressive Disclosure

A concise overview with a single well-signaled one-level-deep reference ('Read references/release-workflow.md before...'), and that reference file is present in the bundle.

5 / 5

Total

18

/

20

Passed

Description

100%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 states concrete capabilities, provides natural trigger phrases, answers both what and when, and draws a clear boundary against adjacent skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'automatic beta builds, promote-stable dispatches, beta-tag selection, asset and installation verification, and failed release recovery' — giving comprehensive coverage rather than a few generic verbs.

5 / 5

Completeness

Explicitly answers both 'what' (release and recover CLI binaries through Build CLI Binaries...) and 'when' (Use when a contributor asks...) with concrete trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

The 'Use when' clause enumerates natural contributor phrases — 'build a CLI beta', 'publish or promote a stable CLI version', 'choose a release candidate', 'monitor a CLI release', 'diagnose a failed CLI release' — covering the domain's main request shapes.

5 / 5

Distinctiveness Conflict Risk

A narrow first-party-CLI niche with an explicit 'Do not use for TypeScript SDK Changesets releases or CLI source implementation' boundary clause, giving minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ComposioHQ/composio
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.