Skip to content
Skills Library
Law & compliance · Learning & explanation

open-source-licensing

/open-source-licensing

Choose a licence, comply with the licences you depend on, and keep attribution correct as a project grows. Use when publishing a project, adding a dependency, or answering whether a licence permits your use.

Repository
AI-SKILLS ↗
Licence
MIT
Last repository change
05.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Choose a licence, comply with the licences you depend on, and keep attribution correct as a project grows. Use when publishing a project, adding a dependency, or answering whether a licence permits your use.

Original author description

Choose a licence, comply with the licences you depend on, and keep attribution correct as a project grows. Use when publishing a project, adding a dependency, or answering whether a licence permits your use.

How it works

  1. Method
  2. Boundaries
Original SKILL.md headings · 41 lines, 297 words
SKILL.md preview
---
name: open-source-licensing
description: Choose a licence, comply with the licences you depend on, and keep attribution correct as a project grows. Use when publishing a project, adding a dependency, or answering whether a licence permits your use.
---

# Open source licensing

A licence is the terms under which others may use your work, and the
terms under which you use theirs. Most projects get this wrong in one of
two ways: publishing with no licence at all, which grants nothing, or
pulling in a dependency whose terms conflict with how they ship.

## Method

1. **Publish with an explicit licence or nothing is granted.** Code
   without a licence is under exclusive copyright by default, so
   omitting one is the most restrictive choice rather than the most
   permissive.
2. **Pick by what you want downstream.** Permissive licences allow use
   in closed products; copyleft requires derivative works to carry the
   same terms; weak copyleft sits between and applies at the library
   boundary. Choose by the outcome you want, not by popularity.
3. **Check dependency compatibility before adding, not at release.**
   Some combinations cannot be distributed together, and discovering
   that after building on a library is the expensive path.
4. **Preserve attribution and notices.** Most licences require the
   original notice to travel with the code, which means a notices file
   in your distribution rather than a link (see
   dependency-management).
5. **Know how distribution changes obligations.** Some terms trigger on
   distributing binaries and some on providing a network service, so
   how you ship decides what you owe.
6. **Record contributor terms up front.** Whether contributions are
   under the project licence by default or need a signed agreement is
   far easier to settle before the first outside contribution.

## Boundaries

- Licence interpretation is a legal question and this is not legal
  advice; anything commercially significant needs counsel.
- Automated licence scanners identify declared licences and miss
  vendored code and mixed files.
- Changing a project's licence later requires permission from
  contributors who hold copyright, which is often impractical.

Versions

RepositoryScoreLicence
This page · Amey-Thakur/AI-SKILLS90MIT
Tyler-R-Kendrick/agent-skills100MIT

Database snapshot: 13.11.2026 · package version d560d018bf88 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100dependency-licence-audit
    Use when a dependency licence may block publishing or selling, or a component swap needs pricing.
  • 100attribution
    Use when identifying attribution requirements that apply to software products — open-source license notices, third-party asset credits, API usage attribution, font licensing, media licensing, and data source attribution. Covers what must be attributed, how, and where across…
  • 96open-source-release
    Use when a project may go public. Repo and licence.
  • 90prompt-pack-open-source-compliance-review
    Use when conducting an open source licence compliance review for a software product or codebase. Identifies open source components, classifies licence types (permissive, weak copyleft, strong copyleft), assesses compatibility with proprietary and other open source licences,…
  • 100oss-review
    Open source licence compliance check for a dependency list, a single library, or outbound code. Use when reviewing a manifest, SBOM, or repo for copyleft obligations and licence compatibility, when asked whether a library can ship, or when preparing code to be open-sourced.
  • 90open-source-license-selection
    Use when the user asks to choose, reconcile, or apply an open-source license and package metadata. Not for readiness auditing.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.