Make your agent find and compare its own skills. Who knows? Might get better.
  • TypeScript 80.1%
  • JavaScript 19.9%
Find a file
2026-03-13 19:17:30 +04:00
skills/skills-sh chore: improve skills 2026-03-13 19:11:41 +04:00
.gitignore feat: initial commit 2026-03-13 19:03:16 +04:00
api.ts feat: initial commit 2026-03-13 19:03:16 +04:00
bun.lock feat: initial commit 2026-03-13 19:03:16 +04:00
formatters.ts feat: initial commit 2026-03-13 19:03:16 +04:00
index.ts feat: initial commit 2026-03-13 19:03:16 +04:00
LICENSE feat: initial commit 2026-03-13 19:03:16 +04:00
package.json v1.0.1 2026-03-13 19:07:26 +04:00
README.md docs: document skills in readme 2026-03-13 19:17:30 +04:00
tsconfig.json feat: initial commit 2026-03-13 19:03:16 +04:00
types.ts feat: initial commit 2026-03-13 19:03:16 +04:00

skills-sh

Search, inspect, and compare skills from skills.sh.

  • npm: https://www.npmjs.com/package/skills-sh
  • repo: https://github.com/eznix86/skills-sh

Install

npm install -g skills-sh

Or run it directly:

npx skills-sh --help

Companion Skill

This project also has a companion Claude/OpenCode skill named skills-sh.

Install it with:

npx skills add https://github.com/eznix86/skills-sh --skill skills-sh

Commands

Search by keyword:

skills-sh search <query> [--limit n] [--json | --md]

Browse built-in categories:

skills-sh search --category=trending [--limit n] [--json | --md]
skills-sh search --category=hot [--limit n] [--json | --md]

Examples:

skills-sh search golang
skills-sh search react --limit 5
skills-sh search --category=trending
skills-sh search --category=hot --md
skills-sh search typescript --json

show

Show metadata and rendered SKILL.md content for one skill:

skills-sh show <owner/repo/skillId> [--meta-only] [--json | --md]

Alias:

skills-sh details <owner/repo/skillId>

Examples:

skills-sh show jeffallan/claude-skills/golang-pro
skills-sh show jeffallan/claude-skills/golang-pro --meta-only
skills-sh show jeffallan/claude-skills/golang-pro --json
skills-sh show jeffallan/claude-skills/golang-pro --md

show includes:

  • weekly installs
  • first seen
  • security audits
  • platform usage
  • source links
  • install command
  • rendered SKILL.md content unless --meta-only is used

compare

Compare two skills side by side:

skills-sh compare <owner/repo/skillId> <owner/repo/skillId> [--json | --md]

Examples:

skills-sh compare jeffallan/claude-skills/golang-pro affaan-m/everything-claude-code/golang-patterns
skills-sh compare jeffallan/claude-skills/golang-pro affaan-m/everything-claude-code/golang-patterns --json
skills-sh compare jeffallan/claude-skills/golang-pro affaan-m/everything-claude-code/golang-patterns --md

compare focuses on:

  • source
  • weekly installs
  • first seen
  • security audits

It intentionally does not include install commands.

Output formats

Flag Best for
(none) Human terminal output
--json Scripts, agents, jq
--md Markdown reports or reusable context

Security audits

show and compare include results from three auditors:

Auditor What it checks
Gen Agent Trust Hub Agent-specific trust and prompt safety
Socket Malicious packages, typosquatting, supply chain
Snyk Vulnerabilities and dependency issues

Overall status is the worst of the three: pass > warn > fail.

How it works

  • Keyword search uses GET https://skills.sh/api/search?q=...&limit=...
  • Category search reads the trending and hot pages from skills.sh
  • show scrapes the skill page and extracts rendered SKILL.md content
  • compare fetches both skills and formats the important metadata side by side

Development

bun install
bun run typecheck
bun run build
bun run dev search golang
bun run dev show jeffallan/claude-skills/golang-pro

Run the built CLI:

node dist/index.js search golang