setup-project-skillslisted

Installs skills from a user-curated manifest (`~/.claude/skill-manifest.json`) into the current project's `.claude/skills/` — symlinks local skills, runs `npx skills add` for third-party ones, and advises `/plugin install` for native Claude plugins. Optionally scans the project for trigger files (Dockerfile, wrangler.jsonc, *.tf, etc.) and pre-selects recommended matches. Use when the user wants to set up skills in a new project, add a skill they curated, see what skills fit the current project, or bootstrap a freshly cloned repo with their toolbox.
Goodsmileduck/claude-registry · ★ 1 · DevOps & Infrastructure · score 74

Install: claude install-skill Goodsmileduck/claude-registry

# setup-project-skills Installs skills into the current project from a manifest the user maintains. Distinct from `claude-automation-recommender` (which advises across hooks/MCP/subagents/skills/plugins and does not install) and from `find-skills` (which discovers public skills). This skill is opinionated: it installs only what's on the user's whitelist. ## When to invoke - "Set up skills for this project." - "Bootstrap this repo with my skills." - "What skills should I install here?" — the project-detection pass answers that from the manifest. - "Link/install/add `<name>` here." - Fresh `git clone` followed by a session in the new directory. ## When NOT to invoke - User is actually doing terraform/k8s/docker/etc. work — the underlying skills handle that. - User wants a recommendation across the full Claude Code surface (hooks, subagents, MCP, plugins) — that's `claude-automation-recommender`. - User wants to discover what skills exist on the public registry — that's `find-skills`. - User wants to author a new skill — that's `skill-creator`. ## Cross-cutting rules 1. **The manifest is the source of truth.** Always read `~/.claude/skill-manifest.json` (or `$SKILL_MANIFEST` if set). Never invent skills not listed there. If a skill the user names isn't in the manifest, offer to add it rather than installing ad-hoc. 2. **Project-scoped install only.** Always link or install into `./.claude/skills/<name>` of the current working directory. Never into `~/.claude/skills/` from