Open Source License

Community

skala-io

open-source-license

Open Source License guidance, selection, compliance review, and drafting. Use this skill when users ask about choosing open source licenses, checking license compatibility, reviewing projects for OSS compliance, generating LICENSE/NOTICE files, or understanding specific license terms. Triggers include questions about MIT, Apache, GPL, BSD, LGPL, AGPL, copyleft, permissive licenses, license compatibility, SPDX identifiers, or any OSS licensing topic.

Overview

Publisher	skala-io
Repository	`legal-skills`
Skill name	`open-source-license`
Stars	53
Forks	11
Bundled files	11
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
11 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by skala-io on GitHub. Read the source before you install it.

Installation

Install the Open Source License AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/skala-io/legal-skills/tree/main/skills/open-source-license
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/skala-io/legal-skills.git /tmp/legal-skills
mkdir -p .claude/skills
cp -r /tmp/legal-skills/skills/open-source-license .claude/skills/open-source-license

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Open Source License in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Open Source License on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Open Source License is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

First published on Skala Legal Skills

Legal Disclaimer

This skill is provided for informational and educational purposes only and does not constitute legal advice. The analysis and information provided should not be relied upon as a substitute for consultation with a qualified attorney. No attorney-client relationship is created by using this skill. Open source licensing involves complex legal considerations that may vary by jurisdiction. Laws and regulations vary by jurisdiction and change over time. Always consult with a licensed attorney in your jurisdiction for advice on specific legal matters. The creators and publishers of this skill disclaim any liability for actions taken or not taken based on the information provided.

Open Source License Skill

Comprehensive guidance for open source license selection, compliance review, and documentation drafting.

Capabilities

1. License Selection

Help users choose the right license based on their goals using the decision tree.

2. License Comparison

Explain differences between licenses, compatibility, and trade-offs.

3. Compliance Review

Analyze projects for license compliance issues and compatibility conflicts.

4. License Drafting

Generate LICENSE files, NOTICE files, and source file headers using canonical texts.

Workflow

For License Selection Questions

Read references/selection/decision-tree.md
Ask clarifying questions based on the decision tree:
- Primary goal (adoption vs keeping code open)?
- Patent protection needed?
- Library or application?
- SaaS/network use?
Provide recommendation with reasoning
Reference notable projects using recommended license
Offer to generate LICENSE file if desired

For License Comparison Questions

Read references/selection/comparison-matrix.md
Compare requested licenses across key dimensions:
- Permissions (commercial use, distribution, modification)
- Conditions (attribution, copyleft, source disclosure)
- Limitations (liability, warranty)
Highlight key differences
Provide examples of projects using each license

For Compliance Review

Read references/compliance/compatibility.md and references/compliance/checklist.md
Identify all licenses in the project
Check compatibility between licenses
Flag any copyleft licenses that may affect distribution
Note any missing attribution or compliance gaps
Provide actionable remediation steps
Reference references/compliance/common-issues.md for context

For License/NOTICE File Generation

Read appropriate template from references/templates/
CRITICAL: Always use canonical license text exactly as provided
Never modify license terms or generate license text from scratch
Only fill in placeholders: [YEAR], [FULLNAME], [PROJECT NAME]
For NOTICE files, aggregate third-party attributions properly
For headers, use language-appropriate comment syntax

Reference Files

Topic	File
Permissive licenses (MIT, Apache, BSD, ISC)	`references/licenses/permissive.md`
Copyleft licenses (GPL, LGPL, AGPL, MPL)	`references/licenses/copyleft.md`
Other licenses (CC, Boost, zlib)	`references/licenses/specialty.md`
License comparison table	`references/selection/comparison-matrix.md`
License selection guide	`references/selection/decision-tree.md`
License compatibility rules	`references/compliance/compatibility.md`
Compliance checklist	`references/compliance/checklist.md`
Common compliance mistakes	`references/compliance/common-issues.md`
LICENSE file templates	`references/templates/license-files.md`
NOTICE file templates	`references/templates/notice-files.md`
Source header templates	`references/templates/source-headers.md`

Key Rules

Never Generate License Text

Always use canonical license text from templates. License texts are legal documents that must be exact. Do not:

Paraphrase license terms
Generate license text from memory
Modify standard license language
Create "custom" licenses

Include Project Examples

When discussing licenses, mention notable projects that use them:

MIT: React, Node.js, jQuery, Rails, Angular
Apache-2.0: Kubernetes, TensorFlow, Android, Spark
GPL-3.0: WordPress, GIMP, Bash
AGPL-3.0: Nextcloud, Mastodon, Grafana
BSD-3-Clause: Django, Flask, numpy
MPL-2.0: Firefox, Thunderbird

Flag Complex Scenarios

Recommend legal counsel for:

Dual licensing strategies
License changes mid-project
Commercial projects with copyleft dependencies
AGPL in SaaS environments
Multi-jurisdictional distribution
Patent-sensitive situations

Quick Answers

"What license should I use?"

→ Follow decision tree; default to MIT for simplicity or Apache-2.0 for patent protection.

"Can I use GPL code in my proprietary app?"

→ Generally no, unless through LGPL dynamic linking or separate processes.

"What's the difference between MIT and Apache-2.0?"

→ Apache-2.0 includes explicit patent grant and retaliation clause; MIT is simpler but no patent protection.

"Is Apache-2.0 compatible with GPL?"

→ Apache-2.0 is compatible with GPL-3.0, but NOT with GPL-2.0.

"Do I need to open source my code if I use AGPL?"

→ Only if you modify the AGPL code AND provide it as a network service. Using unmodified AGPL tools internally doesn't trigger copyleft.

Output Format

When generating LICENSE files:

Confirm the license choice
Ask for copyright holder name and year
Output the complete canonical license text
Remind user to place it in repository root as LICENSE or LICENSE.txt

When reviewing compliance:

List all identified licenses
Show compatibility analysis
Flag any issues with severity (critical/warning/info)
Provide specific remediation steps

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Open Source License AI skill do?

Why use Open Source License on TypingMind?

Because you install it once and use it with any model. Open Source License is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Open Source License in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/skala-io/legal-skills/tree/main/skills/open-source-license. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Open Source License?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Open Source License?

As many as you like. As long as a model supports skills, you can use Open Source License with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Open Source License AI skill free?

Yes. It is published on GitHub by skala-io under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Executing Plans

obra

CommunityPopular

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Context And Decisions

affaan-m

CommunityPopular

Govern stable domain context with a narrowly scoped CONTEXT.md when needed, and route hard-to-reverse decisions to ECC's existing architecture-decision-records skill. Use when domain terms require…

Docs Governance

Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Legal Disclaimer

Open Source License Skill

Capabilities

1. License Selection

2. License Comparison

3. Compliance Review

4. License Drafting

Workflow

For License Selection Questions

For License Comparison Questions

For Compliance Review

For License/NOTICE File Generation

Reference Files

Key Rules

Never Generate License Text

Include Project Examples

Flag Complex Scenarios

Quick Answers

"What license should I use?"

"Can I use GPL code in my proprietary app?"

"What's the difference between MIT and Apache-2.0?"

"Is Apache-2.0 compatible with GPL?"

"Do I need to open source my code if I use AGPL?"

Output Format

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now