publish-cli

Use when preparing, tagging, and publishing an apps/cli npm release. Guides changelog drafting, apps/cli/package.json version bumps, cli-vX.Y.Z tags, local npm publishing, and the publish-cli GitHub workflow.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%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 highly actionable, well-sequenced release runbook with strong validation gates and executable commands. Its main weakness is verbosity in two rationale/troubleshooting passages and a monolithic single-file structure with no progressive disclosure references.

Suggestions

Tighten the Step 0 hub-respawn rationale and the ignore-scripts test-failure note to the essential actionable facts; move the full diagnostic detail to a reference file.

Consider extracting the SDK release (Step 0) and/or the local test-failure troubleshooting into a referenced file so SKILL.md stays a lean overview with one-level-deep detail.

Trim repeated phrasing around 'Ask before pushing' and approval gates where the same gate is stated multiple times in adjacent steps.

Dimension	Reasoning	Score
Conciseness	Mostly efficient domain-specific guidance, but the Step 0 hub-respawn rationale paragraph and the lengthy ignore-scripts test-failure note (line 181) are padded and could be tightened without losing clarity.	3 / 5
Actionability	Fully executable git/gh/bun commands throughout, with copy-paste-ready blocks covering the main, nightly, forced-nightly, and local publish paths.	5 / 5
Workflow Clarity	Clear Step 0 -> 9-step sequence with explicit validation checkpoints (approval gates, 'Ask before pushing', test runs, 'wait for the SDK workflow to succeed'); destructive-op validation is present so no cap applies.	5 / 5
Progressive Disclosure	Single self-contained file with well-organized sections (Release contract, Step 0, numbered Workflow), but it is long and monolithic with no one-level-deep references; the long inline notes could be split out.	4 / 5
	Total	17 / 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, third-person description that clearly states both capabilities and trigger conditions with concrete, domain-specific actions. The only gap is minor synonym coverage in trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'changelog drafting, apps/cli/package.json version bumps, cli-vX.Y.Z tags, local npm publishing, and the publish-cli GitHub workflow' — giving comprehensive coverage of the release process rather than just a few actions.	5 / 5
Completeness	Explicitly answers both 'what' ('Guides changelog drafting...') and 'when' ('Use when preparing, tagging, and publishing an apps/cli npm release') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms ('publishing an npm release', 'tagging', 'version bumps', 'cli-vX.Y.Z tags') but omits common synonyms a user might say such as 'release the CLI', 'release notes', or 'publish cline'.	4 / 5
Distinctiveness Conflict Risk	Clear niche scoped to CLI npm releases with distinct triggers (cli-vX.Y.Z tags, publish-cli workflow), distinct from the SDK release skill and minimal overlap risk.	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: cline/cline
Path: .cline/skills/publish-cli/SKILL.md
Commit: 35b4cd0

Reviewed: 7 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.