Skm update vendor skills

Skill weiox/skm/skills/skm-update-vendor-skills

Agent Skill Manager — discover, install, link, and upgrade skills for Claude Code & Codex.

Install

npx -y skills add weiox/skm --skill skm-update-vendor-skills

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when vendor skill packages under `~/.skm/vendor` may have upstream updates and you want to refresh one package or all packages, then rebuild and verify the Codex and Claude Code entrypoints.

SKILL.md

2.2 KB, as published. Nobody here has run it

Update Vendor Skills

Overview

Vendor skill packages drift over time. This skill updates those packages without losing the local skm entrypoint model.

After updating a vendor package, it immediately rebuilds the entrypoints and verifies the result.

When to Use

Use this skill when:

a vendor package has upstream changes you want locally
a submodule is behind remote
you imported a package earlier and now want to refresh it
you want to update all vendor packages in one pass

Do not use this skill for first-time installation of a new package. Use skm-install-linked-agent-skills for that.

Core Rule

After every vendor update:

rebuild entrypoints
verify entrypoints

Run the bundled script:

bash ~/.skm/skills/skm-update-vendor-skills/scripts/skm-update-vendor-skills.sh [package-name...]

Workflow

1. Choose scope

no arguments: update all vendor packages
one argument: update one vendor package
multiple arguments: update only the named packages

2. Run the updater

Examples:

bash ~/.skm/skills/skm-update-vendor-skills/scripts/skm-update-vendor-skills.sh

bash ~/.skm/skills/skm-update-vendor-skills/scripts/skm-update-vendor-skills.sh superpowers

bash ~/.skm/skills/skm-update-vendor-skills/scripts/skm-update-vendor-skills.sh superpowers skm

3. Read the result

The script reports one of:

UPDATED <package>
UNCHANGED <package>
SKIP <package>

Then it runs:

bootstrap.sh --force
check.sh

Common Mistakes

pulling a vendor package manually and forgetting to rebuild entrypoints
editing vendor packages directly in entrypoint directories
using install flow for updates instead of using the updater
assuming vendor updates do not affect Codex or Claude Code visibility

Completion Checklist

Before calling the update complete:

target vendor packages have been refreshed
bootstrap.sh --force has run
check.sh passes
updated packages are clearly reported back to the user