skills.rest
aaronbassett
aaronbassettCOMMUNITY
Explore all skills by this author →
GitHub

readme-and-co:license-selection

Select software licensing strategies across permissive, copyleft, and multi-licensing scenarios.

4|1|Updated Jan 23, 2026
Search Tags:#compliance#license#licensing#OSS#FSL#dual-licensing
One-click install
npx skills add https://github.com/aaronbassett/aaronbassett-marketplace --skill readme-and-co-license-selection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: readme-and-co:license-selection
Source: https://github.com/aaronbassett/aaronbassett-marketplace/tree/main/plugins/readme-and-co/skills/license-selection
Command: npx skills add https://github.com/aaronbassett/aaronbassett-marketplace --skill readme-and-co-license-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams choose the right license strategy for software projects, including open-source, dual licensing, and time-delayed models, reducing legal risk and confusion.

Core Features & Use Cases

  • License decision trees for code, documentation, and libraries.
  • Guidance on multi-licensing patterns (dual licensing, FSL, open core).
  • Clear README-style explanations to help teams communicate licensing choices with stakeholders.

Quick Start

Use the license-selection skill to determine the appropriate licensing approach for a new project, then generate a compliant README section and license files.

Frequently Asked Questions about readme-and-co:license-selection

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

FAQPage Schema
How do I choose the right software license for my project?▼

Dual licensing allows you to offer software under both an open-source license and a commercial license. This Skill provides guidance on multi-licensing patterns, including dual licensing and FSL, to help organizations manage time-delayed models and open core strategies.

What is the Functional Source License and when should I use it?▼

The Functional Source License (FSL) is a time-delayed licensing model that eventually converts to an open-source license. You should use FSL when you want to restrict immediate commercial exploitation while eventually providing full OSS compliance for the community.

How do I write a README section to explain my licensing strategy?▼

You write a README section to explain your licensing strategy by generating clear, compliant explanations of your chosen license context. This Skill creates README-style explanations and contributor agreements to communicate licensing choices to stakeholders and minimize organizational risk.

Does my open-source library need a contributor agreement for compliance?▼

Your open-source library needs a contributor agreement to enforce clear license context and minimize legal risk. This Skill generates contributor agreements alongside license files to help organizations and communities maintain OSS compliance across permissive and copyleft scenarios.

Related Skills

Explore More Legal & Compliance Skills→
cornmanwtfcornmanwtf

delivery-checklist-and-handoff

Generate delivery checklists and handoff artifacts for software projects.

Community
Intermediate
pradyumnasagarpradyumnasagar
6

roadmap-author

Guide authors through creating and validating ORS SKILL.md files.

Community
Intermediate
ntaksh42ntaksh42
1

dependency-analyzer

Analyze project dependencies for security vulnerabilities, updates, and license compatibility.

Community
Intermediate
lushly-devlushly-dev
4

audit-licenses

Audit OSS dependency licenses and generate SBOMs in CycloneDX and SPDX formats.

Official
Advanced