home / skills / ehtbanton / claudeskillsrepo / license-file-generator

license-file-generator skill

safe

This skill generates a complete OSI-approved LICENSE file for a specified open source license, including MIT, Apache, or GPL.

npx playbooks add skill ehtbanton/claudeskillsrepo --skill license-file-generator

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

643 B

---
name: license-file-generator
description: Generate LICENSE files for open source projects (MIT, Apache, GPL, etc.). Triggers on "create license file", "generate license", "mit license", "apache license".
---

# License File Generator

Generate LICENSE files for various open source licenses.

## Output Requirements

**File Output:** `LICENSE`
**Format:** Plain text license
**Standards:** OSI-approved licenses

## When Invoked

Immediately generate a complete LICENSE file for the specified license type.

## Example Invocations

**Prompt:** "Create MIT license for my project"
**Output:** Complete MIT `LICENSE` file with current year.

Overview

This skill generates complete LICENSE files for open source projects, covering OSI-approved licenses such as MIT, Apache, and GPL. It produces a plain text file named LICENSE, formatted exactly as required by the chosen license and populated with project-specific details like year and copyright holder. It triggers on prompts like "create license file", "generate license", "MIT license", or "Apache license". The output is ready to drop into a project repository.

How this skill works

When invoked, the skill selects the specified license template, fills in dynamic fields (current year, holder name, project name when applicable), and outputs a plain text LICENSE file. It supports common OSI-approved licenses and validates that required fields are present before generation. The generated content follows canonical wording for each license so it can be used directly in open source projects.

When to use it

Initializing a new open source repository and you need a LICENSE file.
Adding or updating a project's license to reflect a new year or copyright holder.
Converting licensing requests from contributors into a standard LICENSE file.
Automating project scaffolding or CI workflows that require a LICENSE artifact.

Best practices

Specify the exact license type (e.g., "MIT", "Apache-2.0", "GPL-3.0") to avoid ambiguity.
Provide the correct copyright holder name and confirm the current year for accuracy.
Review license headers for projects with multiple components or third-party code before replacing existing files.
Use the generated LICENSE file as-is for repository root; avoid modifying canonical license texts except where allowed (e.g., adding names).
Keep a note of any contributor agreements or additional notices that must accompany the LICENSE file.

Example use cases

"Create MIT license for my project" — outputs a standard MIT LICENSE with the current year and provided copyright holder.
"Generate Apache license" — produces an Apache-2.0 LICENSE with required boilerplate and patent clauses.
"Create GPL-3.0 license" — returns the full GNU GPL v3 text suitable for inclusion at project root.
Automated project scaffolding: include a step that calls the skill to add a LICENSE file during repository creation.

FAQ

Which licenses are supported?

Common OSI-approved licenses such as MIT, Apache-2.0, GPL-3.0 and similar variants are supported; specify the exact identifier when requesting a license.

Can you customize the license text?

The skill fills required dynamic fields like year and copyright holder. Canonical license wording is preserved; avoid altering required legal terms unless you understand the implications.