BrowseFull catalogOutcomesSolve a specific problemRolesStack by teamTrustFilter by risk tier
← Back to the Claude Observatory

Skills.sh — Agent Skills Directory

Workflow Setup & Config Poor
Works inClaude Code Claude Cowork Claude Chat
Poor Reviewed

Primary upstream for skill discovery. But 36% of community skills have security flaws per Snyk audit. Every entry needs individual evaluation.

Vercel-launched open directory of AI agent skills — the largest single source of community skills. Each entry installs with one command (npx skills add <owner/repo>) and works across Claude Code, Cursor, Copilot, and 20+ agent runtimes.

FreeQuick setup

Primary upstream for skill discovery. But 36% of community skills have security flaws per Snyk audit. Every entry needs individual evaluation.

Researchers scanning for new skills. Not for direct deployment — use as a discovery source only.

Claude Code Claude Cowork Claude Chat

https://skills.sh

By community

How to Get It

This is a methodology or approach. Paste the instructions below into a Claude conversation to get started.

Command
Browse https://skills.sh to find a skill, then install it with: npx skills add <owner/repo>

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

First thing to try

After installing, paste this into Claude:

Help me search the largest skill directory covering ninety thousand entries
PrerequisitesClaude Code CLI or Claude Desktop (Cowork)Time to functional10 minutesCostFree — Unknown — verify on site

Trust Signals Reviewed

Not yet scanned. Learn how to check this tool yourself.

Community Pulse Active

Discussed on Hacker News, Reddit

3 mentions across 2 sources

Reviewer notes

Reviewed review. These are observations, not a security certification.

catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 0 GitHub stars; contributors unknown; commit recency unknown; license no license.

2026-03-29: URL: https://skills.sh. Mentioned in Paweł Huryn's PM-focused Cowork guide. Focused on PM/product workflows: PRDs, competitive analysis, pricing models, launch checklists. Verify current pricing and update coverage before recommending. Evaluate security before client use.

Things to check

  • Directory size (91K+ skills) creates discovery overhead and quality varies by contributor; skills may require adaptation for specific runtime or platform versions, and maintenance burden falls on individual skill authors rather than centralized stewards.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation

Ease of Use
1/5
Versatility
1/5
Reliability
1/5
Security
3/5
Overall score1.30 / 5.00 PoorEvaluatedJul 2026
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 0 GitHub stars; contributors unknown; commit recency unknown; license no license.

← Back to the Claude Observatory

Rolling Claude out in your org? Let's talk.

Start a conversation →