Symlink skills

Skill usrrname/agent-skills/.agents/skills/symlink-skills

skill dump

Install

npx -y skills add usrrname/agent-skills --skill symlink-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.
0 stars0 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

Symlink every skill in this repo into one or more agent skills directories (defaults to ~/.claude/skills/ and ~/.agents/skills/) so the skills become globally discoverable. Use when the user says "install these skills", "make these skills global", "symlink skills to ~/.claude", "symlink skills to ~/.agents", "register the skills", or wants to update the global skill set after editing skills here.

SKILL.md

2.7 KB, 598 tokens by cl100k_base, as published. Nobody here has run it

Symlink Skills

Symlinks every directory under <repo>/skills/ into each configured target, making each skill in the registry globally discoverable. Edits in the repo are picked up live because the symlinks point at the real files.

Default targets:

~/.claude/skills/ (Claude Code's standard skill directory)
~/.agents/skills/ (other agents that follow the same convention)
~/.cursor/skills/
~/.config/opencode/skills/ on macOS, ~/.opencode/skills/ elsewhere (auto-detected via $OSTYPE; override with OPENCODE_SKILLS_DIR)

Run

From the repo root:

./skills/symlink-skills/link.sh             # link into both default targets
./skills/symlink-skills/link.sh --dry-run   # preview without changes
./skills/symlink-skills/link.sh --force     # replace existing files / mis-pointed symlinks
./skills/symlink-skills/link.sh --unlink    # remove only the symlinks created by this skill

Pick targets explicitly (skips the defaults entirely once --target is set):

# Just Claude Code:
./skills/symlink-skills/link.sh --target ~/.claude/skills

# Multiple custom targets:
./skills/symlink-skills/link.sh --target ~/.claude/skills --target /work/.agents/skills

Or override any default via env var:

CLAUDE_SKILLS_DIR=/tmp/fake-claude/skills \
AGENTS_SKILLS_DIR=/tmp/fake-agents/skills \
CURSOR_SKILLS_DIR=/tmp/fake-cursor/skills \
OPENCODE_SKILLS_DIR=/tmp/fake-opencode/skills \
  ./skills/symlink-skills/link.sh

Behaviour

Idempotent. Re-running is safe; correct symlinks are left alone.
Safe by default. If <target>/<name> exists as a real directory (or as a symlink to a different target), the script refuses to overwrite it and exits non-zero. Pass --force to replace.
Per-target reporting. Each target is processed in turn with its own pass/fail summary.
Scoped unlink. --unlink removes only symlinks under each target whose target resolves back into this repo. Other files and symlinks are untouched.
Returns non-zero if any skill could not be linked in any target.

Why

Editing skills in one place (this repo) and having them auto-available in every agent that reads from ~/.claude/skills/ or ~/.agents/skills/ beats maintaining multiple copies.

What ships with it: 1 file

5.2 KB alongside SKILL.md, 1 of them executable

link.shruns5.2 KB