skills.sh is a public directory and leaderboard for reusable agent skill packages. Its companion skills CLI installs skills from Git repositories into supported agent locations. The directory helps with discovery; the source repository remains the place to inspect what the skill contains.

Search before installing

Browse the directory or use npx skills find <query>. Look for a narrow description, visible source, license, recent maintenance, and instructions that match your host. Popularity is a discovery signal, not a security review. Read SKILL.md and inspect scripts, hooks, or tool dependencies before granting workspace access.

Install a repository or one skill

# Inspect what a repository exposes
npx skills add owner/repository --list

# Install one named skill into the current project
npx skills add owner/repository --skill release-notes

# Install for your user across projects
npx skills add -g owner/repository --skill release-notes

# Install non-interactively after review
npx skills add owner/repository --skill release-notes -y

Project scope is easier to review and share through version control. Global scope suits stable personal workflows. The CLI supports GitHub shorthand, full Git URLs, GitLab, direct repository paths, and local folders. Keep the source URL in your project documentation so another person can audit or update the package.

Manage the second day

Use npx skills list to see installed skills, skills check to inspect update status, skills update to refresh, and skills remove to uninstall. Review source changes before updating a skill with scripts or broad permissions. The CLI’s anonymous telemetry contributes install counts to the leaderboard; set DISABLE_TELEMETRY=1 when you do not want that event collected.

Publish a skill people can trust

Keep the public repository small and readable. Put each skill in a clearly named folder, include its license, state supported hosts, and give users one exact install command. Add test prompts and known limitations. A badge can show skills.sh installs, but it should not replace evidence that the workflow works.

A useful listing earns links because people install and cite it. Do not create duplicate repositories or automated posts solely to manufacture backlinks. Google identifies automated link creation and excessive exchanges as link spam. A maintained skill, a concrete guide, and a real case study are stronger acquisition assets than a large network of shallow pages.

Use SkillForge with the directory

SkillForge can help author or revise the SKILL.md visually. Download the file, place it in a public Git repository with any supporting resources, and test it in the hosts you claim to support. The directory distributes the package; it does not certify the instructions, scripts, or results.