add-license

Create or update root LICENSE files from an MIT template and append README license links.

12|2|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/osolmaz/tools --skill add-license
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-license
Source: https://github.com/osolmaz/tools/tree/main/agents/skills/add-license
Command: npx skills add https://github.com/osolmaz/tools --skill add-license

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures consistent licensing across repositories by automatically creating or updating a root LICENSE from a bundled template and appending a standard License link to the README.

Core Features & Use Cases

  • Default to MIT unless the user or repository specifies a different license.
  • Create or update a root LICENSE from references/mit-license-template.txt.
  • Ensure the README ends with a bottom-of-README License section like MIT.

Quick Start

Run the add-license on your repository to generate or normalize the root LICENSE from the MIT template and append a bottom README license link.

Frequently Asked Questions about add-license

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate adding an MIT license to my repository?

To automate adding an MIT license, this skill generates a root LICENSE file from a bundled template, fills in the current year and copyright holder, and appends a local license link to your README.

How do I update my README with a license section automatically?

Updating your README with a license section happens automatically by appending a standard bottom-of-README block containing a local link like [MIT](LICENSE) to your existing repository documentation.

Can I apply a custom license instead of the default MIT template?

Yes, you can apply a custom license. The skill defaults to the MIT license unless you or your project specifies a different license, which it then uses to generate the root LICENSE file.

What is the best way to ensure consistent licensing across multiple repositories?

The best way to ensure consistent licensing across repositories is to run an automated process that creates or normalizes the root LICENSE from a standard template and appends a uniform license link to every README.

Does the license automation tool fill in the copyright year and holder automatically?

Yes, the license automation tool fills in the copyright year and holder automatically. It extracts this information to populate the generated root LICENSE file from the MIT template.

How do I normalize an existing license file in my repository?

To normalize an existing license file, the skill updates or overwrites your root LICENSE using the bundled MIT template, ensuring the copyright details and README documentation remain consistent.