skill-collection

Personal manager for Claude Code skills, plugins, and bookmarks — keeps global Claude lightweight by defaulting to project-scope installs, while still being able to discover, install, and clean up across scopes.

What it does

• Install/list/remove/move/dedupe skills across project and user (global) scope
• Install/list/reload/update/uninstall plugins via the /plugin system
• Bookmark library of favorite skills with install paths, when-to-use, and personal notes
• Auto-triggers when you mention installing/uninstalling/listing/managing skills or plugins

The pattern

Claude Code skills can pile up at user-scope (~/.claude/skills/) and slow you down — every conversation loads them, even when irrelevant. The opposite extreme is forgetting which skills exist when you start a new project.

This skill is the middle ground:

• One user-scope skill (skill-collection) holds bookmarks, manages installs, and understands plugin/skill/scope distinctions.
• Each bookmark is a markdown file with frontmatter (install path, collections, dates) plus When-to-use and Notes sections.
• Bookmarked skills are installed per-project, not at user-scope. Triggered by natural language: "install nextjs skills from my collection".
• Collections are tags, not folders — a single skill can belong to core, nextjs, and dashboard simultaneously.

Install for yourself

For project use:

npx skills add jubscodes/skill-collection --agent claude-code -y

For everywhere (recommended for the manager itself, since it's how you'd install skills into new projects):

npx skills add jubscodes/skill-collection --agent claude-code --global -y

Then in any project, just say:

Bookmarks:

• "install nextjs skills from my collection"
• "what skills do I have for solana"
• "bookmark this skill: anthropics/knowledge-work-plugins@architecture"
• "add a note to shadcn"

Skills lifecycle:

• "list my skills" / "what's installed"
• "remove [name] from project scope"
• "move [name] from user to project"
• "dedupe my skills"

Plugins lifecycle:

• "list my plugins"
• "install plugin [name]"
• "uninstall plugin [name]"

Fork it for your own bookmarks

The bookmarks in bookmarks/ are mine. Fork the repo and replace them:

1. Fork jubscodes/skill-collection → yourname/skill-collection
2. Edit bookmarks/*.md — replace with skills you actually use, with your own notes
3. Update collection tags in SKILL.md if you want different categories
4. Push and install via npx skills add yourname/skill-collection --agent claude-code --global -y

The pattern is the value; the bookmarks are personal.

Structure

SKILL.md                       # main skill: concepts, trigger phrases, workflows
README.md                      # this file
LICENSE                        # MIT
bookmarks/                     # one file per bookmark
├── shadcn.md                  # collections: [nextjs, react-ui, dashboard]
├── code-review.md             # collections: [core]
├── debug.md                   # collections: [core]
└── …

Bookmark format

---
name: <skill-name>
install: <install-path>            # e.g. anthropics/knowledge-work-plugins@code-review
collections: [core, nextjs]         # at least one
source: <https://skills.sh/...>     # optional
added: YYYY-MM-DD
last_installed: YYYY-MM-DD          # optional
---

# <skill-name>

**Install:** `npx skills add <install-path> --agent claude-code -y`

## When to use
<one-liner>

## Notes
<personal observations from using it>

Why project-scope installs?

Every collaborator gets the same skill set via git pull. The skill ships with the repo. No "works on my machine" surprises. See the Concepts section in SKILL.md for the full rationale.

License

MIT.