ClaudeSkills
All guides

ClaudeSkills guide

Know the source and the permission

A source label, a license and a delivery method answer different questions. Read all three before downloading, adapting or redistributing a skill package.

Updated 2026-10-04

Identify who maintains the skill

The publisher is the person or organization credited for the skill; the source record identifies the repository or distribution inspected. “Official”, “community” and “original” describe provenance. They do not independently prove compatibility, reliability or permission to resell. Use the source link and pinned revision to inspect what the catalog entry refers to.

Read the package-specific license

Follow the license link for the exact package or path. A repository can contain entries under different terms, and source-available code is not the same as an unrestricted open-source package. An unspecified license does not imply broad permission. When adapting or sharing a package, check attribution, redistribution and commercial-use requirements in the actual terms.

Keep supporting resources and rights together

A workflow can depend on scripts, references, fonts, media or external tools. Preserve the required files when installing and examine their own terms when they are distributed with the package. Public source references may link upstream rather than expose every file through this site. Original purchased files use a separate delivery route after verified payment.

  • The full package includes its required references and runtime files.
  • License and attribution information remain with the adapted or shared files.
  • External accounts, model usage and third-party assets have their own terms.

Compare a new revision before replacing it

The pinned revision makes an inspected reference traceable. If an upstream package changes, compare the instructions, dependencies and license before upgrading your working copy. Keep local edits and a record of the revision you used for an important artifact. A newer source date is not proof that your workflow has been re-tested.

Related reading