Agent skill

Publish UI Package Release

Validates and publishes the standalone @cline/ui npm package through its own release workflow, separate from the Cline SDK runtime packages.

Apache-2.0Auto-check passedDevOps & Cloud

Install Publish UI Package Release

skills CLI

$ npx skills add cline/cline --skill publish-ui -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install cline/cline publish-ui --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/cline/cline.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cline/skills/publish-ui .claude/skills/publish-ui && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "publish-ui" agent skill from https://github.com/cline/cline/tree/main/.cline/skills/publish-ui into .claude/skills/publish-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-ui", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/cline/cline/tree/main/.cline/skills/publish-ui

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add cline/cline --skill publish-ui -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install cline/cline publish-ui --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cline/cline.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cline/skills/publish-ui .agents/skills/publish-ui && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "publish-ui" agent skill from https://github.com/cline/cline/tree/main/.cline/skills/publish-ui into .agents/skills/publish-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-ui", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add cline/cline --skill publish-ui -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install cline/cline publish-ui --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cline/cline.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cline/skills/publish-ui .cursor/skills/publish-ui && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "publish-ui" agent skill from https://github.com/cline/cline/tree/main/.cline/skills/publish-ui into .cursor/skills/publish-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-ui", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/cline/cline.git --path .cline/skills/publish-ui

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add cline/cline --skill publish-ui -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install cline/cline publish-ui --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cline/cline.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cline/skills/publish-ui .gemini/skills/publish-ui && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "publish-ui" agent skill from https://github.com/cline/cline/tree/main/.cline/skills/publish-ui into .gemini/skills/publish-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-ui", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install cline/cline publish-ui

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add cline/cline --skill publish-ui -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/cline/cline.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cline/skills/publish-ui .github/skills/publish-ui && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "publish-ui" agent skill from https://github.com/cline/cline/tree/main/.cline/skills/publish-ui into .github/skills/publish-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-ui", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add cline/cline --skill publish-ui -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install cline/cline publish-ui --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/cline/cline.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cline/skills/publish-ui .opencode/skills/publish-ui && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "publish-ui" agent skill from https://github.com/cline/cline/tree/main/.cline/skills/publish-ui into .opencode/skills/publish-ui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-ui", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: publish-ui
GitHub stars: 70k
Token cost: ~1.4k tokens
SKILL.md length: 516 words
Files: 2
Skills in repo: 8
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Validates and publishes the standalone @cline/ui npm package through its own release workflow, separate from the Cline SDK runtime packages.

Works in 3 steps: Inspect the branch, current version, npm… → Ask for the npm channel and version… → Validate the release candidate.
Bumping and publishing a new @cline/ui version
SKILL.md covers Release contract, Normal release, One-time npm bootstrap and Final report
Calls npm, bun and git

What it does

This skill releases @cline/ui on its own cadence rather than alongside the Cline SDK runtime packages. The package's version lives in a workspace package.json, the actual publish happens through a manually dispatched workflow, and latest is the production npm tag while next is an explicit prerelease-only preview tag.

A normal release checks the branch, current version and npm state, asks for the channel and exact version bump rather than guessing, runs the UI package's typecheck and test suite along with a packed-tarball install test under both newer and older React, commits the version bump separately from feature work, and only then talks through dispatching the workflow with an explicit publish confirmation from the main branch.

Every step that pushes a commit, triggers the publish workflow, changes npm trust settings, or runs a local publish command waits for an explicit go-ahead first, since npm versions are immutable and can never be republished once they land.

When your agent uses it

Bumping and publishing a new @cline/ui version
Publishing a preview build of @cline/ui under the next tag
Checking whether @cline/ui is ready to release

Example prompts

“Bump @cline/ui to the next patch version and publish it to latest.”
“Publish a 0.2.0-next.0 preview build of the UI package.”
“Is @cline/ui ready to ship? Run the release checks.”

Requirements

npm publish access to @cline/ui
Bun for running the package's checks

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Inspect the branch, current version, npm state, and UI changes.
Ask for the npm channel and version together. For latest, ask for patch,
Validate the release candidate.

What it can do on your machine

Read from SKILL.md and the folder at commit fa840c7. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- npm
- bun
- git
- gh
- node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Publish UI Package Release loads about 1.4k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 516 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~65
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cline/cline at commit fa840c7, republished under its Apache-2.0 licence (© cline). 516 words, ~1,366 tokens.

Download SKILL.mdSave it as .claude/skills/publish-ui/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: publish-ui
description: 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.

Publish UI

Release @cline/ui independently from the Cline SDK runtime packages.

Release contract

Version source: sdk/packages/ui/package.json.
Workflow: .github/workflows/ui-publish.yml.
The package keeps internal: true only to stay out of the SDK's shared version/publish scripts. It is still a public npm package because private: false and publishConfig.access: public control npm publication.
latest is the production channel. next is an opt-in preview channel.
Use prerelease versions such as 0.2.0-next.0 for next; do not publish a version intended for latest under the preview tag because npm versions cannot be republished.
There is no UI Git tag, GitHub release, schedule, or Slack announcement.
The workflow runs only by manual dispatch. Every release attempt runs the UI quality checks before publishing and requires confirm_publish=publish from main.
The publish job and npm trust relationship use the protected Publish environment.
Every npm publication needs a new semver version; npm versions are immutable.
Always ask before pushing commits, triggering the publish workflow, changing npm trust settings, or running a local publish command.

Normal release

Inspect the branch, current version, npm state, and UI changes.

git status --short --branch
node -p "require('./sdk/packages/ui/package.json').version"
npm view @cline/ui dist-tags versions --json
git log --oneline --no-merges -- \
  sdk/packages/ui apps/examples/desktop-app/webview/components/views/chat \
  .github/workflows/ui-publish.yml

Ask for the npm channel and version together. For latest, ask for patch, minor, major, or an explicit version. For next, require an explicit prerelease version such as 0.2.0-next.0. Do not guess. Update only sdk/packages/ui/package.json and its workspace version in bun.lock. Do not run the SDK version command.
Validate the release candidate.

bun install --filter @cline/ui --filter @cline/code --frozen-lockfile
bun -F @cline/ui typecheck
bun -F @cline/ui test
bun -F @cline/ui test:package
bun -F @cline/ui build-storybook
bun -F @cline/code test:chat-ui

The packed-package test installs the tarball with Bun/React 19 and with npm/Node/React 18. Inspect bun pm pack --dry-run when the exported file set changed.

Commit the version bump separately from feature work. Ask before pushing.

git add sdk/packages/ui/package.json bun.lock
git commit -m "chore(ui): release vX.Y.Z"
git push origin HEAD

After the release commit reaches main, restate the selected npm tag and ask for explicit publish approval. Then trigger and watch the standalone workflow:

run_url=$(gh workflow run ui-publish.yml --ref main \
  -f npm_tag=latest \
  -f confirm_publish=publish)
test -n "$run_url"
run_id=${run_url##*/}
gh run watch "$run_id" --exit-status

Use npm_tag=next only for a deliberate preview. Do not report success until the workflow succeeds and npm shows the exact version under the selected tag.

npm view @cline/ui dist-tags versions --json

Show full SKILL.md (200 more words)Show less

One-time npm bootstrap

Use this only while npm view @cline/ui returns E404. npm requires the package to exist before its GitHub trusted publisher can be configured.

Merge the package and ui-publish.yml to main. Start from a clean, reviewed main checkout. Verify authentication, account 2FA, and write access to the @cline npm organization. The npm trust command in step 4 requires npm CLI 11.15 or newer; the automated trusted-publishing workflow itself enforces npm 11.5.1 or newer.

npm --version
npm whoami
npm view @cline/ui version

If npm is older than 11.15, ask before upgrading with npm install -g npm@^11.15.0.

Run the normal release validation in step 3 above. Then build, pack, test, and inspect the exact initial tarball. Record the absolute archive path printed by the final command.

bun -F @cline/ui build
pack_dir=$(mktemp -d)
(cd sdk/packages/ui && bun pm pack --ignore-scripts --destination "$pack_dir" --quiet)
tarball=$(find "$pack_dir" -maxdepth 1 -name '*.tgz' -print -quit)
test -n "$tarball"
bun sdk/packages/ui/scripts/smoke-package.ts "$tarball"
tar -tzf "$tarball"
printf 'Bootstrap archive: %s\n' "$tarball"

Ask for explicit approval, then publish the initial version publicly under latest:

npm publish /absolute/path/from-step-2.tgz --access public --tag latest

Ask separately before configuring the standalone workflow as the trusted publisher:

npm trust github @cline/ui \
  --repo cline/cline \
  --file ui-publish.yml \
  --env Publish \
  --allow-publish

Verify both package state and trust. Every later release uses the workflow; do not add a long-lived npm token.

npm view @cline/ui dist-tags versions --json
npm trust list @cline/ui

Final report

Report the version and npm tag, release commit, whether anything was pushed, workflow URL or bootstrap result, npm verification, and tests/builds run. If the package still returns E404, state that bootstrap remains required.

Files

SKILL.md and 1 other file in .cline/skills/publish-ui of cline/cline.

SKILL.md
agents/openai.yaml

Open the folder on GitHubat commit fa840c7

Compare with similar skills

Publish UI Package Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Publish UI Package Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Publish UI Package Release this skillcline/cline	70k	—	~1.4k	Automated safety check: Pass	Apache-2.0	today
ClickUp CLI Release Processkrodak/clickup-cli	121	—	~906	Automated safety check: Warn	MIT	3 days ago
GAIA Sidecar Agent Releaseamd/gaia	1.6k	—	~3.6k	Automated safety check: Pass	MIT	yesterday
Check Release DeploymentsNVIDIA/NeMo-Relay	192	—	~415	Automated safety check: Pass	Apache-2.0	yesterday
Adf MasterKilo-Org/kilo-marketplace	190	—	~3.2k	Automated safety check: Pass	MIT	11 days ago
Cicd Playbookmohitagw15856/pm-claude-skills	1.4k	—	~2.9k	Automated safety check: Notes	MIT	yesterday

Similar skills

ClickUp CLI Release Process
krodak/clickup-cli
Walks through releasing a new version of clickup-cli: pre-release checks, version bump, tagging, CI watch, release notes and the Homebrew update.
121 GitHub stars~906 tokensUpdated 3 days ago
DevOps & CloudAuto-check: warnings
GAIA Sidecar Agent Release
amd/gaia
Walks through releasing a GAIA sidecar agent as a frozen binary plus npm client through the tag-triggered Agent Hub CI pipeline, with a human gate before publishing.
1.6k GitHub stars~3.6k tokensUpdated yesterday
DevOps & CloudAuto-check passed
Check Release Deployments
NVIDIA/NeMo-Relay
Official
Verify whether a tagged NeMo Relay release reached GitHub Actions, tagged Go module source, crates.io, PyPI, and npm.
192 GitHub stars~415 tokensUpdated yesterday
DevOps & CloudAuto-check passed
Adf Master
Kilo-Org/kilo-marketplace
Azure Data Factory (ADF) CI/CD, deployment, and pipeline development.
190 GitHub stars~3.2k tokensUpdated 11 days ago
DevOps & CloudAuto-check passed
Cicd Playbook
mohitagw15856/pm-claude-skills
Write a CI/CD pipeline playbook for a service or team. An agent skill from mohitagw15856/pm-claude-skills.
1.4k GitHub stars~2.9k tokensUpdated yesterday
DevOps & CloudAuto-check: notes
Repo Hygiene Scan and Fix
QwenLM/qwen-code
Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.
28k GitHub stars~1.7k tokensUpdated today
DevOps & CloudAuto-check passed

Questions about Publish UI Package Release

What does Publish UI Package Release do?

Validates and publishes the standalone @cline/ui npm package through its own release workflow, separate from the Cline SDK runtime packages. This skill releases @cline/ui on its own cadence rather than alongside the Cline SDK runtime packages.json, the actual publish happens through a manually dispatched workflow, and latest is the production npm tag while next is an explicit prerelease-only preview tag.

When should I use Publish UI Package Release?

Publish UI Package Release fits situations like: bumping and publishing a new @cline/ui version; publishing a preview build of @cline/ui under the next tag; checking whether @cline/ui is ready to release.

How do I install Publish UI Package Release in Claude Code?

Run `npx skills add cline/cline --skill publish-ui -a claude-code`. Or copy the skill folder (.cline/skills/publish-ui in cline/cline) into .claude/skills/publish-ui in your project. Claude Code loads it when a task matches its description.

How do I install Publish UI Package Release in Codex?

Run `npx skills add cline/cline --skill publish-ui -a codex`. Or copy the skill folder (.cline/skills/publish-ui in cline/cline) into .agents/skills/publish-ui in your project. Codex loads it when a task matches its description.

Can I use Publish UI Package Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cline/cline --skill publish-ui -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/publish-ui, .gemini/skills/publish-ui, .github/skills/publish-ui and .opencode/skills/publish-ui in your project.

What does Publish UI Package Release need to run?

Going by SKILL.md and its folder, Publish UI Package Release needs the command-line tools its instructions call (npm, bun, git, gh and node). Our summary lists: npm publish access to @cline/ui; Bun for running the package's checks.

Does Publish UI Package Release access the network?

SKILL.md contains no URLs. Its commands use npm, git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Publish UI Package Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Publish UI Package Release use?

Publish UI Package Release is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Publish UI Package Release use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Publish UI Package Release?

Skills that share tags, products or a category with Publish UI Package Release: ClickUp CLI Release Process (krodak/clickup-cli, 121 stars), GAIA Sidecar Agent Release (amd/gaia, 1.6k stars), Check Release Deployments (NVIDIA/NeMo-Relay, 192 stars) and Adf Master (Kilo-Org/kilo-marketplace, 190 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Publish UI Package Release?

cline (a GitHub organization) maintains it in cline/cline, which has 70,041 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 9, 2026.

Source: cline/cline on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Publish UI Package Release

Install Publish UI Package Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Publish UI

Release contract

Normal release

One-time npm bootstrap

Final report

Files

Compare with similar skills

Similar skills

ClickUp CLI Release Process

GAIA Sidecar Agent Release

Check Release Deployments

Adf Master

Cicd Playbook

Repo Hygiene Scan and Fix

More from cline/cline

Cline SDK Guide

Create Pull Request

OpenTUI Terminal Interfaces

Desktop What's New Dialog

Cline Desktop App Release

Cline CLI Release Publisher

Questions about Publish UI Package Release

Install Publish UI Package Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Publish UI

Release contract

Normal release

One-time npm bootstrap

Final report

Files

Compare with similar skills

Similar skills

More from cline/cline

Related

Questions about Publish UI Package Release