license
Skill1 starsChanged 3 days agoMITView on GitHub
Choose, add, change, compare or check the license of a project - matches the user's needs (commercial use, copyleft, patents, attribution, SaaS, no-sale...) against the known SPDX licenses with a comparison matrix, proposes the closest existing one, discusses the 2-3 differing points before any custom text, fetches the official text (never written from memory), identifies the current LICENSE and asks before replacing it, updates the README/CPack/package files and checks the dependencies' licenses. Use whenever the user asks about a license, a LICENSE/COPYING file, licensing terms or license compatibility.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- apache/skywalkingtheir own version, first seen Oct 8, 2026
- drevendev/HungryCrabtheir own version, first seen Sep 20, 2026
- Pradnyeshp/Claude-Skillstheir own version, first seen Jul 6, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- apache/skywalking★ 25ksame name
- drevendev/HungryCrab★ 5same name
- Pradnyeshp/Claude-Skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository70 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-at-endSkill
- clarifySkill
- continue-workSkill
- exportSkill
- full-permissionSkill
- ideationSkill
- interactive-questionsSkill
- onboardSkill
- pauseSkill
- presentationSkill
- rtkSkill
- setup-contextSkill
- write-like-meSkill
- audit-bugsSkill
- audit-depsSkill
- audit-qualitySkill
- audit-securitySkill
- benchmarkSkill
- cmake-styleSkill
- cpp-classSkill
- cpp-commentsSkill
- cpp-projectSkill
- cpp-styleSkill
- better-explain-docSkill
- better-html-docSkill
- better-html-styleSkill
- better-protocol-docSkill
- docs-updateSkill
- explain-docSkill
- html-docSkill
- html-styleSkill
- protocol-docSkill
- readme-styleSkill
- reportSkill
- wiki-styleSkill
- ci-cdSkill
- git-commitSkill
- git-conventionsSkill
- pre-commitSkill
- legal-checkSkill
- legal-setupSkill
- libutils-exceptionSkill
- libutils-installSkill
- libutils-setupSkill
- libutilsSkill
- python-classSkill
- python-commentsSkill
- python-projectSkill
- python-styleSkill
- auditSkill
- cppSkill
- devSkill
- docSkill
- gitSkill
- legalSkill
- pythonSkill
- setup-projectSkill
- styleSkill
- setup-studioSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Not legal advice: say it once in the answer when the choice has consequences (custom terms, commercial restrictions, relicensing, …
- Distinctive: line 42
Check the dependencies against the chosen license (matrix "Compatibility").
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
License
Not legal advice: say it once in the answer when the choice has consequences (custom terms, commercial
restrictions, relicensing, incompatible dependencies) and recommend a lawyer for anything custom.
SKILL_DIR = the directory of this file. Matrix: reference/matrix.md (read it before proposing anything).
1. Current state
python3 SKILL_DIR/scripts/license.py identify <LICENSE|COPYING|LICENSE.md> # SPDX id + similarity + copyright noticeAlso look at where the license is declared: README (badge, ## License), CMakeLists.txt
(CPACK_RPM_PACKAGE_LICENSE, CPACK_RESOURCE_FILE_LICENSE, install(FILES LICENSE ...)), package.json,
pyproject.toml, Cargo.toml, debian/copyright, SPDX-License-Identifier: headers in the sources.
Dependencies: find_package/pkg_check_modules/FetchContent of the CMake, vendored folders, package manifests
(their LICENSE files when present locally).
2. Needs
From the request, then one AskUserQuestion call (French) for what is still unknown, max 4 questions among:
commercial use by others, must modifications/derived works stay open (none / modified files / library / whole work /
also SaaS), patent grant, attribution required, forbid selling or hosting, closed-source linking allowed,
documentation/assets (CC) vs code, compatibility with a given dependency or ecosystem. The user's own projects use
MIT (Copyright (c) <year> Tsukini): a good default when nothing is required.
3. Match (matrix)
- Exact match -> propose it with 1-2 alternatives and why (one line each).
- Close match (an existing license differs on 2-3 points) -> show a table "besoin / licence proposée / écart", then AskUserQuestion: accept the existing license as it is (Recommandé), pick another close one, or only if the points are really not negotiable, an addition. Never go straight to a custom license.
- Not negotiable -> prefer, in this order: another known license (incl. source-available:
BUSL-1.1,Elastic-2.0,PolyForm-*), a known license + an official exception/clause (license.py exception <ID>, Commons Clause), dual licensing. A text written from scratch is the very last resort: warn clearly (unknown license = legal risk, not OSI/FSF approved, incompatible with most ecosystems, packagers and companies will avoid it, have it reviewed by a lawyer) and keep it short, as additional terms on top of a known base. - Source-available licenses are not open source: say it when proposing them.
- Check the dependencies against the chosen license (matrix "Compatibility"); report blocking ones (ex: GPL dependency in an MIT project, Apache-2.0 with GPL-2.0-only).
4. Write it
python3 SKILL_DIR/scripts/license.py info <SPDX-ID> # permissions / conditions / limitations
python3 SKILL_DIR/scripts/license.py fetch <SPDX-ID> --holder "<name>" [--year YYYY] --out LICENSE [--force]- Texts only from choosealicense.com / the SPDX list (cached in
~/.cache/license-skill); fills[year],[fullname],<year>,<copyright holders>; holder = existing notice, elsegit config user.name, else ask. - Existing LICENSE: show its identification and ask (AskUserQuestion) before replacing it, with the option to
keep a backup (
LICENSE.old);--forceonly after the confirmation. Relicensing code that has other contributors needs their agreement: say it. - Licenses with parameters:
BUSL-1.1(Licensor, Licensed Work, Additional Use Grant, Change Date, Change License),Apache-2.0(NOTICEfile when redistributing), GPL/LGPL/AGPL (the copyright notice goes in the README / file headers, the LICENSE file is the plain text;-or-latervs-onlyis a notice choice, same text). - Exceptions / clauses go in the same LICENSE after the base text (or
LICENSE.exception), with a sentence saying so.
5. Update the references
README (readme-style: badge , ## License section
naming the SPDX id), CPACK_RPM_PACKAGE_LICENSE "<SPDX>", manifests license fields, SPDX-License-Identifier
headers when the project already uses them. Report: chosen license (SPDX), why, files changed, open points.
An analysis delivered as a summary (comparison of licenses, compatibility of the dependencies, state of a
project) goes through report (ask the output format of report (Markdown + PDF recommended, PDF only, Markdown only), English, audit/ at the repository root); a simple LICENSE change is just reported in the chat.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

