Name: publish-ui
Rating: 73.6 (1 reviews)
Author: cline

publish-ui

Prepare, validate, and publish standalone @cline/ui npm releases. Use when bumping the UI package version, publishing latest or next through ui-publish.yml, checking UI release readiness, or completing the one-time npm trusted-publishing bootstrap.

Quality

90%

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

88%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 tightly written, highly actionable release runbook with strong validation checkpoints appropriate to irreversible npm publishes. Minor conciseness and content-splitting opportunities keep it just short of perfect.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence (no explaining npm/GitHub Actions/semver), with a few explanatory sentences about the `internal: true` flag and version-tag semantics that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands (git, node, npm view, bun -F, gh workflow run, npm publish, npm trust) cover both the normal release and bootstrap paths with concrete examples.	5 / 5
Workflow Clarity	Numbered sequences with explicit validation checkpoints (validate before commit, `test -n` guards, `--exit-status`, verifying npm dist-tags before declaring success) for an immutable npm-publish operation.	5 / 5
Progressive Disclosure	Single self-contained file with well-organized section headers (Release contract, Normal release, One-time bootstrap, Final report) and no nested references; the release-contract bullets could conceivably live as a reference but the structure is otherwise clean.	4 / 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 precise, well-scoped description that pairs concrete actions with an explicit "Use when" trigger clause and clear boundaries against the broader SDK publishing flow. The only minor gap is slightly internal-domain trigger vocabulary.

Dimension	Reasoning	Score
Specificity	"Prepare, validate, and publish" lists multiple concrete actions and names the domain ("standalone @cline/ui npm releases"), giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	It explicitly states what the skill does ("Prepare, validate, and publish standalone @cline/ui npm releases") and when to use it via a concrete "Use when..." clause with multiple trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases like "bumping the UI package version", "publishing latest or next", "checking UI release readiness", and "npm trusted-publishing bootstrap" map well to user requests, though a few common variations are absent.	4 / 5
Distinctiveness Conflict Risk	Scoped to standalone @cline/ui releases via ui-publish.yml, clearly distinct from SDK runtime packages, with minimal risk of triggering for unrelated 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: cline/cline
Path: .cline/skills/publish-ui/SKILL.md
Commit: f91af30

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