setting-up-public-domain-repos-majo

Automate dual licensing setup with Unlicense OR 0BSD for repositories.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/markjoshwel/skills --skill setting-up-public-domain-repos-majo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setting-up-public-domain-repos-majo
Source: https://github.com/markjoshwel/skills/tree/main/setting-up-public-domain-repos-majo
Command: npx skills add https://github.com/markjoshwel/skills --skill setting-up-public-domain-repos-majo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the setup of dual-licensing and public-domain configurations for software projects, ensuring licensing consistency from the start.

Core Features & Use Cases

  • Initialize a repository with dual licensing (Unlicense OR 0BSD) and populate license files in the root.
  • Validate absence of conflicting licenses and fetch authoritative license documents from trusted sources.
  • Use case: you are starting a new project or converting an existing repo and want to standardize licensing across all contributions.

Quick Start

Initialize a new repository with dual licensing and public-domain setup.

Frequently Asked Questions about setting-up-public-domain-repos-majo

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

FAQPage Schema
How do I set up a public domain repository with dual licensing?

Setting up dual licensing for a public domain repository involves fetching authoritative Unlicense and 0BSD license files, updating the copyright year, and placing them at the repo root. This process validates the absence of conflicting licenses to ensure consistent public-domain usage.

What is dual licensing with Unlicense and 0BSD for git repositories?

Dual licensing with Unlicense and 0BSD allows git repositories to offer software under both a public domain dedication and a permissive license. This dual approach promotes public-domain usage while providing a fallback for jurisdictions where Unlicense might not be legally recognized.

Can I convert an existing git repository to use Unlicense and 0BSD?

Yes, you can convert an existing git repository to use Unlicense and 0BSD. The process validates the absence of conflicting licenses in your current project, fetches the authoritative license documents, and applies the consistent dual-licensing structure directly to your repository root.

Does setting up dual public-domain licensing require initializing a new git repository?

No, setting up dual public-domain licensing does not require initializing a new git repository. While it can populate license files during new repository initialization, it equally supports converting existing repositories by applying the Unlicense and 0BSD structures directly.

What happens if my repository already has conflicting licenses?

If your repository already has conflicting licenses, the setup process will validate and identify them. The skill checks for existing conflicting licenses before applying the Unlicense and 0BSD dual-licensing structure to ensure legal compliance and licensing consistency across all contributions.