AGENT SKILL

upgrade-plugin

Use this skill when upgrading pinned `npx universal-plugin@<version>` calls across a project to a newer version.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 1
Forks
0

01 前言 Front Matter

name
upgrade-plugin
metadata
{ "pin-exempt": true }
description
Use this skill when upgrading pinned `npx universal-plugin@<version>` calls across a project to a newer version.

02 资源文件 1

03 SKILL.md 正文

Upgrade Universal Plugin

When to use

When the user wants to bump the pinned universal-plugin version in hook commands, SKILL.md files, docs, or any other project files from the current pinned version to a target version (latest or a specific semver).

Recognizes both runner words — npx universal-plugin@<version> and upx universal-plugin@<version> (the fast local-first runner, see the adopt-upx skill). A reference keeps whichever runner word it already uses; this skill only bumps the version, never changes npx to upx or vice versa.

Instructions

Step 1 — Resolve the target version

If the user supplied a version (e.g. 2.1.0), use it directly.

Otherwise, fetch the latest published version:

npm view universal-plugin version

Step 2 — Find all pinned calls

Search the project for every occurrence of npx universal-plugin@ or upx universal-plugin@:

grep -rnE "(npx|upx) universal-plugin@" . \
  --include="*.md" --include="*.json" --include="*.yaml" --include="*.yml" \
  --include="*.ts" --include="*.js" \
  | grep -v node_modules

Report a summary: how many files, which files, the runner word each uses (npx or upx), and the versions currently pinned.

If zero occurrences are found, report that there is nothing to upgrade and stop — do not modify files or create a commit.

Step 3 — Confirm with the user

Show the list of files and the planned replacement, then ask for confirmation before making any changes.

Example summary:

Found universal-plugin@1.2.3 pins in 4 files:
  <skill>/SKILL.md (2 occurrences, npx)
  <hooks-file> (1 occurrence, npx)
  <docs-file> (1 occurrence, upx)

Replace all with @1.5.0, keeping each occurrence's runner word (npx/upx)? (y/n)

Step 4 — Apply replacements

For each confirmed file, replace every npx universal-plugin@<old-version> with npx universal-plugin@<target-version>, and every upx universal-plugin@<old-version> with upx universal-plugin@<target-version> — bump the version, keep whichever runner word was already there.

Only replace within the same major version by default — cross-major bumps may include breaking changes. Warn the user and ask for explicit confirmation before replacing across major versions.

# Dry-run first (review output before applying)
grep -rnE "(npx|upx) universal-plugin@" <file> | head -20

Apply with the Edit tool, not sed, so each change is reviewable.

Step 5 — Verify

Re-run the search from Step 2 and confirm no old version strings remain (within the same major), for either runner word.

grep -rnE "(npx|upx) universal-plugin@" . \
  --include="*.md" --include="*.json" --include="*.yaml" --include="*.yml" \
  --include="*.ts" --include="*.js" \
  | grep -v node_modules

Step 6 — Commit

Commit the changes following the project commit discipline:

chore: upgrade npx universal-plugin pin to @<target-version>

04 同仓库更多 Skills

cyberuni
cyberuni/universal-plugin

remove-plugin

Use this skill to remove a universal agent plugin's artifacts — delete the generated vendor manifests for Claude Code, Cursor, or Codex, clear a stale or shadowing manifest left by an older build, or take the whole plugin out of a project. Trigger on "delete the generated manifests", "remove the vendor manifests", "clean the plugin build output", "drop Codex support", "get rid of this plugin", or "stop shipping this plugin".

★ 1
cyberuni
cyberuni/universal-plugin

migrate-plugin

Move a repository-root or sibling-workspace universal agent plugin into its npm package so the package distributes its manifest, vendor manifests, skills, and agents, and bundle the package's CLI with tsdown so it runs from an installed plugin directory with no node_modules. Use this skill when packaging an existing plugin for npm, relocating a top-level or plugins/<name> plugin into a package, fixing a package that omits plugin assets, or making a plugin's bundled CLI self-contained, even if the user says only 'ship this plugin through npm', 'move the plugin into the package', or 'the CLI can't find its dependencies when installed as a plugin.'

★ 1
cyberuni
cyberuni/universal-plugin

marketplace

Use this skill to run a repository's own plugin marketplace — generate the catalogs Claude Code, Codex, GitHub Copilot CLI, and Cursor read, list a plugin that lives elsewhere (an npm package, a GitHub repo, or `<plugin>@<marketplace>`), change one listed entry in place, check every catalog against the schema its runtime loads, and write the README install section. Trigger on "set up a local marketplace", "let users install this from my repo", "generate marketplace catalogs", "add a plugin to the marketplace", "list this npm package in my marketplace", "switch this entry to a url source", "bump the ref on this entry", "change the category of a marketplace entry", "make this repo installable", "add install instructions to the README", or "check my marketplace catalogs".

★ 1
cyberuni
cyberuni/universal-plugin

<skill-name>

Use this skill when <trigger>. <One-line summary.>

★ 1
cyberuni
cyberuni/universal-plugin

adopt-upx

Use this skill when the user wants to make their skills use upx — the fast local-first package runner shipped as @repobuddy/upx. Trigger on phrases like "make my skills use upx", "adopt the upx runner", "speed up npx calls", "switch to upx", or "rewrite npx pins to upx". Rewrites `npx <pkg>@<version>` references to a caret range on `upx` (`^<major>`, or `^0.<minor>` for a 0.x pin) across one skill, a named set, or every skill in the project.

★ 1
cyberuni
cyberuni/universal-plugin

subagent-driven-development

Use this skill when committing changes in this repository, even if the user does not explicitly mention the required pre-commit checks.

★ 1