New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Trigger Prepare Release

by UniClipboard in UniClipboard/UniClipboard

Trigger the prepare-release workflow on GitHub Actions. An agent skill from UniClipboard/UniClipboard.

AGPL-3.0Auto-check passedDevOps & Cloud

Install Trigger Prepare Release

skills CLI
$ npx skills add UniClipboard/UniClipboard --skill trigger-prepare-release -a claude-code

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

GitHub CLI
$ gh skill install UniClipboard/UniClipboard trigger-prepare-release --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/UniClipboard/UniClipboard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/trigger-prepare-release .claude/skills/trigger-prepare-release && 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/

Facts

Skill name
trigger-prepare-release
GitHub stars
1.8k
Token cost
~1.7k tokens
SKILL.md length
724 words
Files
1
Skills in repo
24
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Trigger the prepare-release workflow on GitHub Actions. An agent skill from UniClipboard/UniClipboard.

  • Works in 4 steps: Parse arguments → Confirm with user → Trigger the workflow → …
  • The prepare-release workflow on GitHub Actions
  • SKILL.md covers Arguments and Workflow
  • Calls gh and git

What it does

Trigger Prepare Release is an agent skill from UniClipboard/UniClipboard. Trigger the prepare-release workflow on GitHub Actions. Supports optional arguments for version, bump type, channel, and base branch. Defaults to bump=patch, channel=stable, basebranch=main.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering CI/CD. It works with GitHub Actions. The repository describes itself as: Real-time clipboard sync across all your devices — local-first, peer-to-peer, and end-to-end encrypted. No account. No cloud dependency. No central server. The licence is AGPL-3.0.

When your agent uses it

  • The prepare-release workflow on GitHub Actions
  • Tasks that involve CI/CD

Example prompts

  • “/trigger-prepare-release”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Parse arguments
  2. Confirm with user
  3. Trigger the workflow
  4. Confirm dispatch

What it can do on your machine

Read from SKILL.md and the folder at commit 9c76e0f. 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:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, 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

Trigger Prepare Release loads about 1.7k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 724 words of instructions outside code blocks.

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

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 UniClipboard/UniClipboard at commit 9c76e0f, republished under its AGPL-3.0 licence (© UniClipboard). 724 words, ~1,709 tokens.

Download SKILL.mdSave it as .claude/skills/trigger-prepare-release/SKILL.md (or your agent's skills folder).
name
trigger-prepare-release
description
Trigger the prepare-release workflow on GitHub Actions. Supports optional arguments for version, bump type, channel, and base branch. Defaults to bump=patch, channel=stable, base_branch=main.

Trigger Prepare Release

Trigger the prepare-release.yml workflow on GitHub Actions.

The workflow produces a release/v<version> branch + PR. By default it bases the release off main, but the base_branch input lets you base it off (and target the PR at) any branch — see Choosing base_branch.

Arguments

All arguments are optional.

ParameterDefaultDescription
version(empty)Exact semver, no v prefix. Include the channel suffix if you want one (e.g. 0.9.0-alpha.1). Overrides bump AND channel.
bumppatchVersion bump type: patch, minor, major. Only used when version is empty.
channelstableRelease channel: stable, alpha, beta, rc. Only used when version is empty.
base_branchmainBranch the release is checked out from and the branch the PR targets. Use release/vX.Y.Z when iterating prereleases on a release branch whose commits are not yet merged back to main.
Critical: how version interacts with channel

The workflow's Determine version step is:

sh
if [ -n "$version" ]; then
  VERSION="$version"        # used verbatim, channel ignored
else
  VERSION=$(bump-version.js --type "$bump" --channel "$channel" --dry-run ...)
fi

So:

  • ✅ version=0.9.0-alpha.1 → release v0.9.0-alpha.1 (correct way to ship an alpha at an exact version)
  • ❌ version=0.9.0 + channel=alpha → release v0.9.0 (channel silently ignored, this is the trap)
  • ✅ bump=minor + channel=alpha → script computes next alpha (e.g. v0.9.0-alpha.1)
Choosing base_branch

base_branch controls two things at once: the branch the release is checked out from, and the branch the resulting PR targets (--base).

  • main (default) — the normal case: cut a release off the mainline.
  • release/vX.Y.Z — iterating prereleases on a release branch whose commits are NOT yet merged back to main. The workflow checks out that branch (so the release includes its un-merged commits) and opens the PR back against it. Example: you committed fixes onto release/v0.14.1 and want the next alpha to include them without first merging to main.

Two things to verify before triggering with a non-default base_branch:

  • The branch must be pushed. The workflow checks out the remote origin/<base_branch>, so anything still local-only won't be in the release. Confirm git status -sb shows the branch in sync (not ahead) before triggering.
  • Version is computed from that branch. The Determine version dry-run runs against base_branch's package.json, so the resolved version reflects that branch, not main. The created branch is always named release/v<resolved-version> regardless of base_branch.

Workflow

1. Parse arguments

Accept either key=value form (channel=beta bump=minor) or positional tokens (/trigger-prepare-release 0.9.0-alpha.1). For each positional token, classify by shape:

Token shapeClassified asExamples
Looks like semver (digit-dot-digit, optional -suffix.N)version0.9.0, 0.9.0-alpha.1, 1.2.3-rc.2
One of stable / alpha / beta / rc (bare word)channelalpha, rc
One of patch / minor / majorbumpminor

base_branch is never inferred from a positional token (a branch name like release/v0.14.1 is too free-form to classify safely) — accept it only via the explicit base_branch=<branch> form.

Ambiguity rule: if the user supplies a semver-shaped token AND a bare channel word (e.g. 0.9.0 alpha.1 or 0.9.0 alpha), do NOT split them across version/channel — that triggers the trap above. Instead, ask the user whether they meant:

  • version=0.9.0-alpha.1 (exact version with suffix), or
  • bump=minor channel=alpha (let the script compute the next alpha)
Show full SKILL.md (243 more words)Show less
2. Confirm with user

Display the resolved parameters and ask for confirmation before triggering:

text
Will trigger prepare-release with:
  version:     0.9.0-alpha.1
  bump:        (ignored — version is set)
  channel:     (ignored — version is set)
  base_branch: main
Proceed? (y/n)

If version is empty, show resolved bump and channel instead. Always show base_branch — and when it is not main, restate the resolved version so the user can confirm it was computed from the intended branch.

3. Trigger the workflow
bash
gh workflow run prepare-release.yml \
  --repo UniClipboard/UniClipboard \
  --ref main \
  -f version=<version> \
  -f bump=<bump> \
  -f channel=<channel> \
  -f base_branch=<base_branch>

Omit -f version= when version is empty. Omit -f base_branch= to default to main.

--ref vs base_branch — don't confuse them:

  • --ref main selects which copy of the workflow file to run. Keep it main: it's the default branch, so GitHub validates the dispatch inputs against main's workflow definition. (Both main and the release branches carry the base_branch input, so this is safe.)
  • base_branch is what actually controls which branch the release is based on and where the PR is targeted. --ref does not affect that.

(Older versions of this skill claimed the workflow "always checks out main regardless" — that is no longer true; base_branch is honored.)

4. Confirm dispatch

After triggering, wait a few seconds and show the latest run:

bash
gh run list --repo UniClipboard/UniClipboard --workflow=prepare-release.yml --limit 1

Report the run URL so the user can monitor progress.

To verify the version came out as intended, do not rely on the run name: it is prepare-release-v${version || bump}, so when version is empty it shows the bump type (e.g. prepare-release-vpatch), not the resolved version. Instead check the Determine version step's log, or the PR it opens — the PR title is release: v<resolved-version> and its body states the base branch.

© UniClipboard, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/trigger-prepare-release of UniClipboard/UniClipboard.

Open the folder on GitHubat commit 9c76e0f

Compare with similar skills

Trigger Prepare 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.

Trigger Prepare Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Trigger Prepare Release this skillUniClipboard/UniClipboard1.8k—~1.7kAutomated safety check: PassAGPL-3.0
Analyze GitHub Action Logswithastro/astro63k1 repos~1.3kAutomated safety check: PassCustom licence
GitHub Actions Templatesbartstc/vite-ts-react-template12213 repos~1.9kAutomated safety check: PassMIT
Nushellccusage/ccusage19k—~938Automated safety check: PassCustom licence
Repo Hygiene Scan and FixQwenLM/qwen-code28k—~1.7kAutomated safety check: PassApache-2.0
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2596 repos~1.1kAutomated safety check: NotesCustom licence

Similar skills

  • Analyze GitHub Action Logs

    withastro/astro

    Official

    Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.

    63k GitHub starsUsed in 1 repo~1.3k tokens
    DevOps & CloudAuto-check passed

  • GitHub Actions Templates

    bartstc/vite-ts-react-template

    Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications.

    122 GitHub starsUsed in 13 repos~1.9k tokens
    DevOps & CloudAuto-check passed

  • Nushell

    ccusage/ccusage

    Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.

    19k GitHub stars~938 tokensUpdated today
    DevOps & CloudAuto-check passed

  • 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

  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    259 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes

  • CI Failure Triage and Repair

    Chachamaru127/claude-code-harness

    Diagnoses failing CI pipelines and tests, deciding first whether the test or the implementation is at fault, and hands hard cases to a dedicated fixer subagent.

    3.2k GitHub starsUsed in 1 repo~1.1k tokens
    DevOps & CloudAuto-check: notes

More from UniClipboard/UniClipboard

All 24 skills in this repo

  • Beui

    UniClipboard/UniClipboard

    Pick and install beUI (@beui) animated React components from the shadcn registry.

    1.8k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Create PR

    UniClipboard/UniClipboard

    Push the current branch and open a GitHub pull request against main.

    1.8k GitHub stars~4.6k tokensUpdated today
    Auto-check passed

  • Design Audit

    UniClipboard/UniClipboard

    定期审计代码库的工程设计问题（高心智复杂度、单一真相源被破坏、catch-all 胖接口、死代码、散落魔法字面量、泄漏抽象、资源生命周期靠环形缓冲）与可优化点，范围限定为自上次审计以来的 git churn，每条发现都落到 file:line 并对照本项目自己的 VISION.md / 各级 AGENTS.md / memory…

    1.8k GitHub stars~554 tokensUpdated today
    Auto-check passed

  • Dual Side Debug

    UniClipboard/UniClipboard

    Inspect uniclipboard logs from BOTH the macOS host and the mounted Windows peer when debugging cross-platform sync, pairing, transfer, or daemon issues.

    1.8k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • E2E Test Thinker

    UniClipboard/UniClipboard

    Analyze the current branch's diff against main and determine which changes are testable via CLI-based end-to-end tests.

    1.8k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • iOS Log Diagnose

    UniClipboard/UniClipboard

    Drive the UniClipboard iOS app in a simulator and read its OSLog yourself to diagnose a mobile-sync bug, instead of asking the user to paste logs.

    1.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Trigger Prepare Release

What does Trigger Prepare Release do?

Trigger the prepare-release workflow on GitHub Actions. An agent skill from UniClipboard/UniClipboard. Trigger Prepare Release is an agent skill from UniClipboard/UniClipboard. Trigger the prepare-release workflow on GitHub Actions.

When should I use Trigger Prepare Release?

Trigger Prepare Release fits situations like: the prepare-release workflow on GitHub Actions; tasks that involve CI/CD.

How do I install Trigger Prepare Release in Claude Code?

Run `npx skills add UniClipboard/UniClipboard --skill trigger-prepare-release -a claude-code`. Or copy the skill folder (.agents/skills/trigger-prepare-release in UniClipboard/UniClipboard) into .claude/skills/trigger-prepare-release in your project. Claude Code loads it when a task matches its description.

How do I install Trigger Prepare Release in Codex?

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

Can I use Trigger Prepare 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 UniClipboard/UniClipboard --skill trigger-prepare-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/trigger-prepare-release, .gemini/skills/trigger-prepare-release, .github/skills/trigger-prepare-release and .opencode/skills/trigger-prepare-release in your project.

What does Trigger Prepare Release need to run?

Going by SKILL.md and its folder, Trigger Prepare Release needs the command-line tools its instructions call (gh and git).

Does Trigger Prepare Release access the network?

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

Is Trigger Prepare 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 Trigger Prepare Release use?

Trigger Prepare Release is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Trigger Prepare Release use?

About 1.7k tokens (SKILL.md is roughly 6.8k 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 Trigger Prepare Release?

Skills that share tags, products or a category with Trigger Prepare Release: Analyze GitHub Action Logs (withastro/astro, 63k stars), GitHub Actions Templates (bartstc/vite-ts-react-template, 122 stars), Nushell (ccusage/ccusage, 19k stars) and Repo Hygiene Scan and Fix (QwenLM/qwen-code, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Trigger Prepare Release?

UniClipboard (a GitHub organization) maintains it in UniClipboard/UniClipboard, which has 1,847 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 7, 2026.

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