Guides · Updated November 18, 2026

Can I reuse an agent skill from GitHub?

By Tineessa Nelson, Use This Skill

You can reuse an agent skill from GitHub when a license covers its folder: a LICENSE file in the skill's folder, a parent folder or the repository root. Without one, GitHub's documentation says default copyright applies, so you may read and fork it but not copy or modify it. Of 1,972 public skills we read on November 18, 2026, 1,096 had a covering license file and 876 had none.

Most of the 876 sit in one large collection whose README states a license but whose repository has no license file. The steps below show how to check a skill in about a minute, and what the numbers say about where licenses go missing.

How many public skills have a license?

We cloned all 47 GitHub repositories in this directory's November 16 crawl on November 18, 2026, and, for each of the 1,972 SKILL.md folders, looked for the nearest LICENSE or COPYING file in the skill's folder, then in each parent folder up to the repository root. We read each file and named the license it contains. We also read every license field in the front matter.

License covering the skill folder Skills Repositories
MIT 623 27
Apache-2.0 367 14
CC BY-SA 4.0 99 1
Anthropic's proprietary terms (all rights reserved) 4 1
BSD 1 1
CC0 1.0 1 1
Functional Source License (FSL-1.1-Apache-2.0) 1 1
No license file anywhere above the skill 876 5

Source: Use This Skill directory (data/skills.json, crawl of November 16, 2026), every repository cloned and read by script on November 18, 2026. All 1,972 SKILL.md files were found. A license file was matched by its text, not its name.

Where the covering file sat: the repository root for 1,028 skills, a parent folder such as a package directory for 31, and the skill's own folder for 37. The 37 come from seven repositories, led by anthropics/skills (18) and ComposioHQ/awesome-claude-skills (13).

The 876 with no license file come from five repositories: ComposioHQ/awesome-claude-skills (851), remotion-dev/skills (13), vercel-labs/agent-skills (9), anthropics/skills (2) and multica-ai/andrej-karpathy-skills (1). Four of the five state a license in their README instead. ComposioHQ's says the repository "is licensed under the Apache License 2.0" and that "Individual skills may have different licenses"; vercel-labs and multica-ai say MIT; Anthropic's says many of its skills are open source under Apache 2.0. We found no license statement in the remotion-dev/skills repository.

GitHub's documentation says a license stated only in a README is acceptable but not the recommended practice, and it does not change what the default is when no license applies.

What does a license let me do with a skill?

What you have Use in your own project Change it Share it, or ship it in a product
MIT, Apache-2.0, BSD Yes Yes Yes, keeping the copyright and license notice
CC BY-SA 4.0 (trailofbits/skills) Yes, even commercially Yes Yes, with credit, a link to the license, a note of changes, and your version under the same license
CC0 1.0 Yes Yes Yes; the author has waived rights
A noncommercial or proprietary license Read the terms Read the terms Usually not without permission
No license Read it; fork it on GitHub Not without permission Not without permission

The no-license row follows GitHub's documentation; the CC BY-SA 4.0 row follows the Creative Commons deed, both read November 18, 2026. Other rows summarize the license texts found in the repositories. This is not legal advice.

Two things in this table surprise people. First, a share-alike license such as CC BY-SA 4.0, which covers all 99 trailofbits skills in the crawl, lets you use and change the skills commercially, but a changed version you distribute has to carry the same license. Second, a public repository with no license is not free to copy: GitHub's terms let other users view and fork it, and that is all.

Does the license field in SKILL.md settle it?

Not on its own. The Agent Skills specification lists license as an optional field that "specifies the license applied to the skill", and suggests either a license name or the name of a bundled license file. Of the 1,972 skills, 226 set it, in 12 repositories.

In 59 of those, the field names a different license from the license file covering the folder. 55 are in K-Dense-AI/claude-scientific-skills, where the repository license is MIT. Many of these name the license of the open-source library the skill is about: scikit-learn, for example, says BSD-3-Clause license, which is scikit-learn's own license. A few would restrict the skill itself if they apply to it: what-if-oracle says CC BY-NC-SA 4.0 and its text adds that "commercial use requires a license from the author", and deepspot-m says PolyForm-Noncommercial-1.0.0. Three say Unknown.

When the field and the file disagree, the safe reading is the stricter one until the author clarifies. If you write skills, use the field for the skill's own license and say the library's license in the text.

Can a copied skill carry a different license from the original?

Yes, and the crawl has an example. ComposioHQ/awesome-claude-skills includes copies of Anthropic's docx, pdf, pptx and xlsx skills. In that repository, whose latest commit is dated July 24, 2026, each copy's LICENSE.txt reads "© 2025 Anthropic, PBC. All rights reserved" and forbids reproducing the materials or creating derivative works. In anthropics/skills, cloned the same day, the same four folders carry an Apache License 2.0 file, and the README calls them open source under Apache 2.0.

A copy keeps the terms it was copied with until someone updates it. If you find a skill in a collection, check the original repository too: docx and its copy composiohq-docx are both in this directory. For more on how the two sources differ, see Anthropic's official skills vs community skills.

How do I check a skill's license before I copy it?

  1. Open the skill's folder on GitHub and look for LICENSE, LICENSE.txt or COPYING. A file there applies to that folder.
  2. Walk up the path. Check each parent folder, then the repository root. In monorepos the license often sits in a package folder: 31 skills in the crawl are covered that way.
  3. Read the license field in SKILL.md. If it disagrees with the file, ask the author or follow the stricter terms.
  4. Read the README's license section if there is no file. It tells you what the author intends, but it is not a license file.
  5. Keep the notice when you copy. With MIT or Apache-2.0, copy the LICENSE file into the skill's folder in your project so the notice travels with it.

Before you install, check what the skill does as well as what you may do with it: paste the GitHub link into the live skill check, which runs the nine rules on the safety page. To copy a folder with its license file in one command, see how to install a skill from GitHub.

Should I add a license to my own skills?

Yes, if you want anyone else to use them. Put a LICENSE file in the repository root, and, if one skill uses different terms, a second LICENSE file in that skill's folder. Add license: MIT (or your license) to the front matter so tools that read only SKILL.md can see it. If you share skills inside a company, how to share skills with your team covers the packaging.

How this directory shows licenses

Each skill page on this site shows a license, and the skill's full text appears on the page only when the license is MIT, Apache-2.0 or BSD; otherwise we link to the source. That label is read from the repository root. This count looked deeper, so it reaches a different answer for 44 skills:

  • 18 Anthropic skills and 9 ComposioHQ skills have an Apache-2.0 file in their own folder but show "Not stated" on their skill pages today.
  • 4 ComposioHQ copies (the document skills above) show "Not stated"; their folder carries Anthropic's proprietary terms.
  • 11 trigger.dev skills show Apache-2.0, the repository root's license; the package folders that hold them carry an MIT file.
  • 2 ui-ux-pro-max skills show MIT, the root's license; their folders carry an Apache-2.0 file.

The 99 trailofbits skills, 1 color-space skill and 1 Sentry skill show "Other"; their licenses are CC BY-SA 4.0, CC0 1.0 and FSL-1.1-Apache-2.0. Until the labels read the folder, check the folder yourself.

We did not contact any author for this page. The counts come from reading the files in each repository on November 18, 2026; a repository can change its license at any time, so check again before you rely on it.

Questions

Can I use a skill that has no license in my own projects?

You can read it, and GitHub's terms let other users view and fork a public repository. GitHub's documentation says that without a license the default copyright laws apply, so no one may reproduce, distribute or create derivative works from it. Copying it into your project, editing it or sharing it with your team is safest after the author adds a license or gives you permission.

Does the license field in SKILL.md count as the license?

It is a statement from the author, and the Agent Skills specification says it names the license applied to the skill. It is not the license text itself. In our count, 59 skills had a license field that named a different license from the license file covering their folder, so read both, and treat a license file as the stronger signal.

Do I have to keep the author's name when I change a skill?

Under the licenses most skills use, yes. MIT and Apache-2.0 both ask you to keep the copyright and license notice in copies, and Apache-2.0 also asks you to say which files you changed. CC BY-SA 4.0 asks for credit, a link to the license and a note of changes, and your changed version must use the same license.

Is this legal advice?

No. This page counts what the license files in public repositories say and points to the official pages that explain the rules. For a decision that matters to a business, ask a lawyer who can read the specific license and your use.