license
Skill2 starsChanged 4 months agoMITView on GitHub
Add or update an open-source LICENSE file for the project, filling in the right SPDX license, copyright holder, and year, and optionally inserting license headers into source files. Use when the user says "add a license", "what license should I use", "add MIT/Apache license", "add license headers", or "set up licensing".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- TsukiNi22/skillstheir own version, first seen Nov 16, 2026
- TsukiNi22/ai-utilstheir own version, first seen Nov 16, 2026
- apache/skywalkingtheir own version, first seen Oct 8, 2026
- drevendev/HungryCrabtheir own version, first seen Sep 20, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- apache/skywalking★ 25ksame name
- drevendev/HungryCrab★ 5same name
- TsukiNi22/ai-utils★ 1same name
- TsukiNi22/skills★ 1same 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 repository68 other files it gives its agents.
- a11ySkill
- api-docsSkill
- audit-logSkill
- benchmarkSkill
- bisectSkill
- cacheSkill
- changelogSkill
- cherry-pickSkill
- ci-setupSkill
- codeownersSkill
- commit-messageSkill
- connection-poolSkill
- contributingSkill
- coverageSkill
- db-migrateSkill
- dead-codeSkill
- debugSkill
- depsSkill
- diagramSkill
- dockerizeSkill
- docstringSkill
- e2eSkill
- env-exampleSkill
- error-handlingSkill
- explainSkill
- feature-flagSkill
- flaky-testSkill
- gitignoreSkill
- graceful-shutdownSkill
- graphqlSkill
- healthcheckSkill
- i18nSkill
- idempotencySkill
- lint-fixSkill
- loggingSkill
- migrateSkill
- mockSkill
- onboardSkill
- optimizeSkill
- paginationSkill
- pr-descriptionSkill
- pre-commitSkill
- profileSkill
- prune-branchesSkill
- rate-limitSkill
- readmeSkill
- rebaseSkill
- refactorSkill
- regexSkill
- releaseSkill
- resolve-conflictsSkill
- retrySkill
- review-diffSkill
- scaffoldSkill
- secrets-scanSkill
- security-headersSkill
- seedSkill
- soft-deleteSkill
- sqlSkill
- squashSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Determine the license: Use the id in $ARGUMENTS, else the one declared in the manifest (package.json license, pyproject.toml, Cargo.toml).
- Very specific: line 27
License headers (only if asked): When the user wants per-file headers, insert the short SPDX header (// SPDX-License-Identifier: MIT + …
- Distinctive: line 32
Don't overwrite an existing LICENSE without confirming.
- Very specific: line 33
Keep the LICENSE file, manifest license field, and any headers all naming the same SPDX id — no drift.
- Distinctive: line 35
After writing, report the license chosen, the holder/year used, the files written, and whether headers were added.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Licensing signals
!ls LICENSE* COPYING* 2>/dev/null && echo "(a license file already exists — update it, don't blindly overwrite)"
!cat package.json composer.json 2>/dev/null | grep -iE '"license"|"author"' | head
!git config user.name 2>/dev/null
Instructions
Add or update the project's license per $ARGUMENTS (license id and/or copyright holder). If no license is named and the manifest doesn't already declare one, ask which license the user wants before writing — licensing is a deliberate legal choice, not a default to guess.
Method
- Determine the license. Use the id in
$ARGUMENTS, else the one declared in the manifest (package.jsonlicense,pyproject.toml,Cargo.toml). If they conflict, surface the conflict and confirm. Don't pick a license on the user's behalf. - Determine holder and year. Copyright holder from
$ARGUMENTS, the manifestauthor, or gituser.name; year is the current year (orfirst-currentif an existing header shows an earlier start). Confirm the holder if you had to guess. - Write
LICENSEwith the exact, unmodified canonical SPDX text, substituting only the bracketed[year]and[holder]placeholders. Never paraphrase or trim license text. - Keep metadata in sync. Set/update the
licensefield in the manifest to the matching SPDX identifier (e.g.MIT,Apache-2.0). - License headers (only if asked). When the user wants per-file headers, insert the short SPDX header (
// SPDX-License-Identifier: MIT+ copyright line) at the top of source files in the project's comment style. Skip vendored/generated files and anything already carrying a header.
Rules
- Reproduce canonical license text verbatim — the only edits are the year and copyright-holder placeholders. A modified license is not that license.
- Don't overwrite an existing LICENSE without confirming; if updating, preserve the original year/holder and the existing license unless the user is intentionally changing it (a license change has implications — call them out).
- Keep the LICENSE file, manifest
licensefield, and any headers all naming the same SPDX id — no drift. - You're not a lawyer: when the user is unsure which license fits, briefly describe the common options (MIT = permissive/simple, Apache-2.0 = permissive + patent grant, GPL-3.0 = copyleft) and let them choose — don't decide for them.
- After writing, report the license chosen, the holder/year used, the files written, and whether headers were added.
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.

