nicelicense

Add, identify, and manage open-source LICENSE files with SPDX IDs.

Updated Feb 8, 2026

Search Tags:#cli #license #licensing #spdx #opensource #license-file

Ready to run

npx skills add https://github.com/Xalior/agent-skills --skill nicelicense

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nicelicense
Source: https://github.com/Xalior/agent-skills/tree/main/nicelicense
Command: npx skills add https://github.com/Xalior/agent-skills --skill nicelicense

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open-source licensing is error-prone and time-consuming; this skill helps you add, identify, and manage LICENSE files across projects using the nicelicense CLI.

Core Features & Use Cases

Add a license to a project (interactive prompts or non-interactive mode).
Identify the existing license in a project and report SPDX ID.
List supported SPDX IDs with optional metadata.
Handle template variables like name and years for licenses that require them.
Write LICENSE files to a specific path or stdout, with dry-run option.

Quick Start

Run the nicelicense CLI in your project directory to generate or validate a LICENSE file.

Frequently Asked Questions about nicelicense

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

FAQPage Schema

How do I add an open-source LICENSE file to my project?▼

To add an open-source LICENSE file, you can use interactive prompts or non-interactive automation to generate and write it directly to a specific path in your software project.

How can I identify the existing license in a project and get its SPDX ID?▼

You can identify the existing license in a project by running a validation command that detects the license file and reports its corresponding SPDX ID.

Can I automate license generation across a monorepo non-interactively?▼

Yes, you can automate license generation across a monorepo using non-interactive mode, applying a single SPDX ID and template variables across multiple projects without manual prompts.

What SPDX IDs are supported when generating a license file?▼

Supported SPDX IDs include common open-source license identifiers, and you can list all available options with optional metadata to choose the correct one for your project.

Does license generation support template variables like name and years?▼

Yes, license generation handles template variables like name and years for licenses that require them, allowing you to customize the output for accurate open-source compliance.

Can I preview a license file with a dry-run before writing it to disk?▼

Yes, you can preview a license file using a dry-run simulation or by directing the output to stdout, ensuring the content is correct before writing to a specific path.