From patinaproject-skills
Install one or more agent skills into the current repository with the skills CLI. Use when adding or refreshing locked project-local skills, when a user names a skill source, or when a repository needs shared skills installed without mutating global agent state.
How this skill is triggered — by the user, by Claude, or both
Slash command
/patinaproject-skills:install-skillsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Install skills project-locally so the repository, not the operator's global
Install skills project-locally so the repository, not the operator's global environment, owns the shared workflow catalog.
This skill changes the locked skill set and may update skills-lock.json.
Vendored skills are committed to the repo, so they load without an install step.
To re-vendor the committed overlays from an existing lockfile, use the
repository's manual maintenance command instead:
pnpm skills:install
Use this skill when the desired result is a changed skill catalog: adding,
removing, refreshing, or otherwise updating the entries recorded in
skills-lock.json. After changing the lockfile, run pnpm skills:install and
commit the refreshed .agents/skills/** and .claude/skills/** overlays.
Read repository guidance first: AGENTS.md, CLAUDE.md if present, and
any docs governing agent skills or shared tooling.
Inspect the current catalog if present:
test -f skills-lock.json && npm_config_ignore_scripts=true npx --yes skills@latest list --json
If the repository exposes a wrapper such as pnpm skills:list, use that
instead of the raw CLI list command.
Resolve the requested source and skill names. If the source contents or requested skill names are ambiguous, list before installing:
npm_config_ignore_scripts=true npx --yes skills@latest add <source> --list
Run installs from the repository root. Do not use --global.
Canonical single-source install:
npm_config_ignore_scripts=true npx --yes skills@latest add <source> --skill <skill-name> --agent '*' --yes
For multiple skills from the same source, repeat --skill values as separate
arguments after one flag:
npm_config_ignore_scripts=true npx --yes skills@latest add <source> --skill <skill-a> <skill-b> --agent '*' --yes
For all skills from a source, prefer an explicit all-agent install:
npm_config_ignore_scripts=true npx --yes skills@latest add <source> --skill '*' --agent '*' --yes
GitHub lock entries record a source and skillPath. The upstream skills CLI
(skills experimental_install) restores them by cloning each source's default
branch, so the lock does not pin an immutable ref; re-running picks up the
latest upstream commit on that branch. Locked GitHub sources must be publicly
readable because restore clones from the public GitHub source.
To re-vendor the committed overlays from the lockfile, run:
pnpm skills:install
This runs pnpm dlx skills@latest experimental_install --yes, which reads
skills-lock.json, restores each locked skill into .agents/skills/, and
maintains the relative .claude/skills/ symlinks. Commit the refreshed
overlays afterward.
For Patina Project marketplace skills, use patinaproject/skills as the source
and install only the requested skills unless the user explicitly asks for all.
Active Patina scaffold defaults are:
scaffold-repositoryusing-githubnew-branchdevelop-issuefinish-prreview-codeinstall-skillsAfter installing, prove what changed:
npm_config_ignore_scripts=true npx --yes skills@latest list --json
git status --short
Report the installed skills, the source used, and the changed lockfile or agent overlay paths. Stop before committing unless the user asked you to finish the branch.
npx claudepluginhub patinaproject/skills --plugin patinaproject-skillsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.