Choose and install one Claude Code skill
Start with a task, inspect the original source, and install the skill directory you actually need. This registry aggregates third-party entries; it is not a single first-party skill pack.
1. Search for the task you need
Use concrete terms such as PDF extraction, frontend design or testing in skill search. The homepage starts with highlighted coverage; use Search all to load full search coverage. You can also browse the static skill guides by category without running search JavaScript.
Read what a skill does, which tools it expects and which output it produces. Prefer a skill whose documented workflow matches your task rather than a repository with an attractive name or star count.
2. Open the upstream source and license
A guide's source link identifies the original repository or skill file. Review its SKILL.md, referenced scripts, required tools and permissions. The registry maintainer is not necessarily the skill's author. Archived copies can lag upstream changes.
For a document-editing example, Anthropic's skill lives at anthropics/skills → skills/docx. Read that directory's license before reuse. Each third-party skill retains its own terms; the registry pipeline's MIT license does not relicense it.
A scan signal records a check against content at a point in time. It does not guarantee safe behavior, current upstream contents or permission to redistribute. Unknown licenses require an upstream permission check.
3. Select the exact installation path
If you use sk, the Claude Code skill manager, review the source first, then install the exact subdirectory:
sk install anthropics/skills/skills/docx
sk list
sk info docx
sk doctor
The first skills is the repository name; the second is the directory inside it. A short path selects that directory directly. sk info describes an installed skill, while sk doctor checks local installation health.
For other agent runtimes, follow their installation instructions. Vercel's skills CLI documents agent selection and project/global scopes. For a maintained collection organized into task bundles, see Spellbook. Do not copy the entire aggregate archive as one skill.
Common questions
The skill installed, but my agent cannot see it. What next?
Compare the installed location with the directory read by your agent and session. For sk, run sk info <name> and check its path against the configured Claude Code skills directory. Installation into one runtime's directory does not establish visibility in another.
Does a catalog entry belong to majiayu000?
Not necessarily. Check the source link and archive metadata's author, source_url, license and permission_note. The archive README explains how to trace these fields.
Where do I report a problem?
Send skill behavior questions to its upstream repository. Report search, attribution or catalog problems to the core issue tracker; authors can follow the removal and attribution request procedure. Report sk installation problems to the CLI issue tracker.