Skm install linked agent skills

Skill weiox/skm/skills/skm-install-linked-agent-skills

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

Install

npx -y skills add weiox/skm --skill skm-install-linked-agent-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 a user pastes a GitHub repo URL, `skills.sh` link, `owner/repo@skill` reference, or local git path for an external skill package and wants it imported into `~/.skm/vendor` with `Codex` and `Claude Code` entrypoints rebuilt automatically.

SKILL.md

3.2 KB, as published. Nobody here has run it

Install Linked Agent Skills

Overview

When a user gives you a link to an external skill package, do not leave it floating in chat and do not install it into tool-owned directories directly.

Import the package into:

~/.skm/vendor/<package>

Then regenerate entrypoints:

~/.agents/skills
~/.claude/skills

When to Use

Use this skill when:

the user pastes a GitHub link for a skill package
the user pastes a skills.sh link
the user gives an owner/repo@skill reference
the user gives a local git path and wants to import it into the shared skill library

Do not use this skill for:

skills you are authoring yourself from scratch
project-local AGENTS.md or CLAUDE.md
runtime caches or tool internals

Core Rule

For external skill links:

import into ~/.skm/vendor/
keep the upstream package boundary intact
rebuild entrypoints with bootstrap.sh
verify with check.sh

Installation Command

Use the bundled installer script instead of hand-writing git submodule commands:

bash ~/.skm/skills/skm-install-linked-agent-skills/scripts/skm-install-linked-skill.sh "<link>" [vendor-name]

Examples:

bash ~/.skm/skills/skm-install-linked-agent-skills/scripts/skm-install-linked-skill.sh \
  "https://github.com/obra/superpowers"

bash ~/.skm/skills/skm-install-linked-agent-skills/scripts/skm-install-linked-skill.sh \
  "https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices"

bash ~/.skm/skills/skm-install-linked-agent-skills/scripts/skm-install-linked-skill.sh \
  "owner/repo@skill-name" custom-package-name

Workflow

1. Normalize the link

Accept any of these inputs:

https://github.com/<owner>/<repo>
[email protected]:<owner>/<repo>.git
https://skills.sh/<owner>/<repo>/<skill>
<owner>/<repo>@<skill>
local git path

If the link points to a skill inside a larger package, import the package into vendor/ and let the entrypoint builder expose the concrete skills.

2. Run the installer script

The script will:

derive the upstream repo URL
choose the vendor directory name
add the package under ~/.skm/vendor/
run bootstrap.sh --force
run check.sh

3. Report the result

After installation, report:

the installed vendor directory
whether it was newly imported or already present
which Codex and Claude Code entrypoints were refreshed

Common Mistakes

cloning a linked skill somewhere outside skm
copying files manually instead of preserving an upstream package boundary
editing ~/.agents/skills or ~/.claude/skills directly
forgetting to rebuild entrypoints after import
treating a link to one skill as a reason to scatter files into personal directories

Completion Checklist

Before calling the import done:

the package exists under ~/.skm/vendor/
bash ~/.skm/scripts/bootstrap.sh --force has run
bash ~/.skm/scripts/check.sh passes
the resulting symlink destinations are reported back to the user