Install once, use everywhere

The CLI lists the four skills and asks which ones to install, which agents to target, and whether the scope is project or global.

Quick install

$ npx skills add NaveenGumaste/keyskills --all -y$ bunx skills add NaveenGumaste/keyskills --all -y

Flag reference

--list

List the four skills without installing anything.

--skill <name>

Install one skill. Repeatable per skill.

--all

Install all four skills at once.

-a <agent>

Target an agent. Repeatable per agent.

-y

Skip prompts. Required for non-interactive shells.

Non-interactive recipes

$ npx skills add NaveenGumaste/keyskills --list$ npx skills add NaveenGumaste/keyskills --skill seo-setup -y$ npx skills add NaveenGumaste/keyskills --skill seo-setup --skill design-skill -a claude-code -a cursor -y

Agent integration

Claude Code
-a claude-code
Cursor
-a cursor
Codex
-a codex
Gemini CLI
-a gemini-cli
Antigravity
-a antigravity
OpenCode
-a opencode
Copilot
-a copilot
Windsurf
-a windsurf
v0
-a v0

The four skills

seo-setup

Metadata, Open Graph, Twitter cards, sitemap, robots, and JSON-LD schema. Everything a page needs to get indexed and clicked.

Triggers: metadata · sitemap · open graph · json-ld · robots

design-skill

Kills generic AI-template output. Applies design dials, real design systems, and editorial rhythm to every interface.

Triggers: landing page · redesign · anti-slop · design system

git-skill

Conventional commits, branch naming, PR templates, and ignore hygiene. Zero secret leaks, every time.

Triggers: commit · branch · pull request · git hygiene

codebase-cleanup

Purges zombie dependencies, unused exports, dead files, and console noise. Ships a leaner, faster repo.

Triggers: dead code · unused deps · cleanup · production ready

Custom skill creation

Copy the folder shape of an existing skill: a SKILL.md with triggers up top and numbered rules below.
Keep triggers to short phrases the agent will literally see in prompts. Three to six is the sweet spot.
Write rules as enforceable checks, not advice. Each rule needs a title and a one-paragraph body.
Validate against the skill contract (Zod) and test with --list before publishing.