agentleFS
PradnyeshpPradnyeshp/Claude-Skills/.claude/skills/license/SKILL.md

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

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
  1. Very specific:

    Determine the license: Use the id in $ARGUMENTS, else the one declared in the manifest (package.json license, pyproject.toml, Cargo.toml).

    line 23
  2. Very specific:

    License headers (only if asked): When the user wants per-file headers, insert the short SPDX header (// SPDX-License-Identifier: MIT + …

    line 27
  3. Distinctive:

    Don't overwrite an existing LICENSE without confirming.

    line 32
  4. Very specific:

    Keep the LICENSE file, manifest license field, and any headers all naming the same SPDX id — no drift.

    line 33
  5. Distinctive:

    After writing, report the license chosen, the holder/year used, the files written, and whether headers were added.

    line 35

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Determine the license. Use the id in $ARGUMENTS, else the one declared in the manifest (package.json license, pyproject.toml, Cargo.toml). If they conflict, surface the conflict and confirm. Don't pick a license on the user's behalf.
  2. Determine holder and year. Copyright holder from $ARGUMENTS, the manifest author, or git user.name; year is the current year (or first-current if an existing header shows an earlier start). Confirm the holder if you had to guess.
  3. Write LICENSE with the exact, unmodified canonical SPDX text, substituting only the bracketed [year] and [holder] placeholders. Never paraphrase or trim license text.
  4. Keep metadata in sync. Set/update the license field in the manifest to the matching SPDX identifier (e.g. MIT, Apache-2.0).
  5. 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

  1. Reproduce canonical license text verbatim — the only edits are the year and copyright-holder placeholders. A modified license is not that license.
  2. 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).
  3. Keep the LICENSE file, manifest license field, and any headers all naming the same SPDX id — no drift.
  4. 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.
  5. After writing, report the license chosen, the holder/year used, the files written, and whether headers were added.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.