claude-skill-plugin-packaginglisted

How to distribute Claude Code skills for reuse across repos and how to install them — as a plugin via a marketplace, a pinned git-submodule with committed project-scope settings, or globally. Covers the depth-1 discovery rule (why a bare folder/submodule of skills is NOT found), the `settings.json` schema, aggregating other skill repos, and the gotchas. Invoke when sharing skills across projects, wiring a skill plugin into a repo, choosing flat-skills vs plugin, or asked "why aren't my submodule'd skills showing up / how do I install project skills".
wei18/apple-dev-skills · ★ 0 · AI & Automation · score 70

Install: claude install-skill wei18/apple-dev-skills

# Claude Code Skill Plugin Packaging ## When to invoke - You have skills in one repo and want them reusable across other repos/projects. - Wiring an existing skill plugin (e.g. `apple-dev-skills`) into a new project. - Deciding **flat project skills** vs a **plugin**. - A submodule/nested folder of skills "isn't being discovered" and you don't know why. - Aggregating *other people's* skill repos without copy-pasting. - User asks "how do I share/install skills", "why is my `.claude/skills/<lib>/...` not found". ## The one rule that explains everything: discovery is depth-1 Claude Code discovers **plain project skills only at depth 1**: `.claude/skills/<skill>/SKILL.md`. It does **not** recurse into subdirectories. Consequences (each has burned someone): - A **git submodule** of skills at `.claude/skills/<lib>/` puts SKILL.md at `.claude/skills/<lib>/skills/<skill>/SKILL.md` (depth ≥ 2) → **NOT discovered**. - A bare folder of skills nested one level down → **NOT discovered**. - An in-repo submodule of a plugin you *also* installed via a marketplace is **vestigial** — the marketplace-installed copy is what loads, the submodule does nothing for discovery. (This is why a repo can carry `.claude/skills/superpowers` yet superpowers actually loads from the plugin cache.) So: **to share skills across repos, package them as a plugin and distribute via a marketplace.** A bare submodule alone never works. ## Packaging: make your skills a plugin + marketplace A repo becom