agentsclimarketplace

Skm update vendor skills

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

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.From its SKILL.md

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.

SKILL.md

2.2 KB, 476 tokens by cl100k_base, 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:

  1. rebuild entrypoints
  2. 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:

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

What ships with it: 1 file

2.3 KB alongside SKILL.md, 1 of them executable

scripts/

Gives 0 of the 12 instructions most operations skills give in 476 tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

  • Collect monitoring data throughout the simulationin 14 of 483, across 6 files
  • Set the random seed for reproducibilityin 14 of 483, across 6 files
  • Validate simulations against analytical solutionsin 12 of 483, across 4 files
  • Clarify goals, constraints, and inputsin 11 of 483, across 2 files
  • Implement contract tests for integration pointsin 11 of 483, across 2 files
  • Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
  • Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
  • Avoid Python blocking calls in processesin 10 of 483, across 3 files
  • Use resource context managers for automatic cleanupin 9 of 483, across 2 files
  • Maintain consistent time unitsin 9 of 483, across 2 files
  • Validate outcomes against success criteriain 8 of 483, across 1 file
  • Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Said here and by no other author read

  • run the updater script to refresh packages
  • pass no arguments to update all packages
  • pass package names to update specific packages
  • rebuild entrypoints after every vendor update
  • run bootstrap.sh with the force flag
  • run check.sh to verify entrypoints

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.