license-and-legal
Skill1 starsChanged 3 months agoMITView on GitHub
When a repo has no license or unclear terms. Triggers: 'add a license', 'which license', 'license and legal', 'can people use this'. Helps pick and add the right license plus any third-party notices.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-testsSkill
- cut-a-releaseSkill
- env-and-configSkill
- lint-and-formatSkill
- one-command-runSkill
- package-for-npmSkill
- package-for-pypiSkill
- readme-that-convertsSkill
- repo-hygiene-passSkill
- security-basicsSkill
- set-up-ciSkill
- ship-checklistSkill
- ship-contextSkill
- write-a-changelogSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 14
Read .agents/ship.md and ask the user's intent: maximum adoption, or copyleft.
- Distinctive: line 20
Third-party: if you vendored or heavily adapted others' code, keep their notices and add a NOTICE or credits section.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
License and Legal
Code with no license is all-rights-reserved by default, nobody can legally use it. You fix that deliberately.
Before you start
Read .agents/ship.md and ask the user's intent: maximum adoption, or copyleft.
Steps
- Pick by intent: MIT or Apache-2.0 for permissive (Apache adds a patent grant), GPL or AGPL for copyleft, CC0 for public domain (docs, lists). If unsure and the goal is adoption, MIT is the safe default.
- Add
LICENSEwith the correct year and author, and set thelicensefield in package metadata to match. - Third-party: if you vendored or heavily adapted others' code, keep their notices and add a NOTICE or credits section.
- State the license in the README.
Done when
A LICENSE file exists, the package metadata matches, and any third-party obligations are honoured.
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.

