license-guide

Analyze project context to recommend software licenses with SPDX identifiers.

Updated Mar 19, 2026

Search Tags:#compliance #license #risk-management #open-source #spdx #proprietary

Ready to run

npx skills add https://github.com/sunLeee/optimization --skill license-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: license-guide
Source: https://github.com/sunLeee/optimization/tree/main/.claude/skills/utility/license-guide
Command: npx skills add https://github.com/sunLeee/optimization --skill license-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured guide to select appropriate software licenses for projects, clarifying license types, uses, and compliance considerations.

Core Features & Use Cases

License comparison matrix and decision tree to choose between proprietary, MIT, Apache 2.0, GPL, LGPL, and BSD.
SPDX identifiers, compatibility checks, and deployment-ready checklists for OSS adoption or private use.
Use cases include opening a project to the community, migrating from proprietary, or ensuring license compliance in dependencies.

Quick Start

Describe your project context and follow the guide to obtain a recommended license.

Frequently Asked Questions about license-guide

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

FAQPage Schema

How do I choose the best open-source license for my project?▼

To choose an open-source license, evaluate your project's openness, distribution, and usage scenarios. A decision tree comparing proprietary, MIT, Apache 2.0, GPL, LGPL, and BSD licenses provides actionable recommendations based on your specific context.

What is the difference between MIT, Apache 2.0, and GPL licenses?▼

The difference between MIT, Apache 2.0, and GPL licenses lies in distribution requirements and patent grants. A license comparison matrix clarifies these distinctions, helping you select between permissive and copyleft licenses based on your deployment needs.

How do I check license compatibility across open-source dependencies?▼

To check license compatibility across dependencies, analyze the license types of your components and generate SPDX identifiers. This process ensures your open-source adoption or proprietary deployment meets compliance requirements without conflicting license terms.

When do I need SPDX identifiers for software compliance?▼

You need SPDX identifiers for software compliance when managing open-source adoption or proprietary deployment. Generating these identifiers standardizes license tracking and ensures your dependency compatibility checks meet formal risk-management requirements.

Can I migrate a proprietary project to an open-source license?▼

You can migrate a proprietary project to an open-source license by analyzing your project context and applying a deployment-ready checklist. This ensures proper license compatibility checks across dependencies and clarifies requirements for community openness.

Does using GPL dependencies affect proprietary software distribution?▼

Using GPL dependencies affects proprietary software distribution because GPL enforces copyleft distribution requirements. A license compatibility check across your dependencies clarifies these constraints and guides whether proprietary deployment is viable.