patinaproject/skills

install-skills

Install or refresh project-local agent skills recorded in skills-lock.json. Use when the user names a skill source to add to the repository or asks to update its locked skills.

First seen May 20, 2026

Installation

$ npx skills add patinaproject/skills --skill install-skills

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from patinaproject/skills · top by installs.

npx skills add patinaproject/skills

Browse all from patinaproject/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,990 B
  • docs SUMMARY.md 198 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 124 installs

SKILL.md

Install project skills

Project-local skills belong to the repository. The lockfile records their sources, and the committed .agents/skills/ and .claude/skills/ entries make them available in a fresh checkout.

If skills-lock.json has not changed and the user only wants to restore the committed skill directories, run:

pnpm skills:install

When adding, removing, renaming, or refreshing a lockfile entry, read [the skill list change instructions](./catalog-change.md). They define the order of work, the check for skills renamed or removed upstream, the pull request summary, and required verification.

Before installing

  1. Read AGENTS.md, CLAUDE.md, and any repository instructions for agent

skills or shared tools.

  1. Inspect the current installed list. Prefer a repository script such as

pnpm skills:list. Otherwise run:

``bash test -f skills-lock.json && npmconfigignore_scripts=true npx --yes skills@latest list --json ``

  1. Resolve the requested source and skill names. If either is unclear, list the

source before installing:

``bash npmconfigignore_scripts=true npx --yes skills@latest add <source> --list ``

Install

Run installs from the repository root. Never use --global.

Install one or more named skills from one source:

npm_config_ignore_scripts=true npx --yes skills@latest add <source> --skill <skill-a> <skill-b> --agent '*' --yes

Install every skill from a source only when the user asks for all of them:

npm_config_ignore_scripts=true npx --yes skills@latest add <source> --skill '*' --agent '*' --yes

GitHub lock entries contain source and skillPath. The restore command clones the source's default branch, so another run may install newer upstream content. The source must be publicly readable. Use a source with a git ref when the user requires a fixed version.

After changing the lockfile, restore every locked skill:

pnpm skills:install

This command reads skills-lock.json, writes real skill directories under .agents/skills/, and maintains matching relative links under .claude/skills/.

For Patina Project skills, use patinaproject/skills and install only the requested names. Common repository defaults are:

  • scaffold-repository
  • using-github
  • install-skills
  • grill-to-spec
  • design-by-contract
  • grill-system-design
  • review-system-design
  • writing-for-pstack

Verify

Run:

npm_config_ignore_scripts=true npx --yes skills@latest list --json
git status --short

Follow every additional check in catalog-change.md. Report the installed skills, their source, and the changed lockfile or skill directories. Stop before committing unless the user asked to finish the branch.