licensing

Guide R package license selection and configuration for CRAN submission.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/choxos/RPkgAgent --skill licensing-choxos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: licensing
Source: https://github.com/choxos/RPkgAgent/tree/main/plugins/r-package-development/skills/licensing
Command: npx skills add https://github.com/choxos/RPkgAgent --skill licensing-choxos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the complex landscape of R package licensing, ensuring compliance with CRAN requirements and legal best practices for code, data, and bundled third-party components.

Core Features & Use Cases

  • License Selection: Guides users through choosing appropriate open-source or proprietary licenses.
  • File Setup: Demonstrates correct DESCRIPTION, LICENSE, and .Rbuildignore configurations.
  • Compatibility Guidance: Provides a matrix and explanations for license compatibility between packages.
  • Bundled Code Handling: Advises on licensing when incorporating external code snippets or libraries.
  • Use Case: A developer needs to choose a license for their new R package and ensure it's compatible with a dependency they wish to include. This Skill will help them select a license, configure the necessary files, and verify compatibility.

Quick Start

Use the licensing skill to understand how to apply the MIT license to an R package.

Frequently Asked Questions about licensing

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

FAQPage Schema
How do I choose the right open source license for my R package?

To choose an open source license for an R package, evaluate your project requirements against common options like MIT or GPL. This Skill guides you through selecting appropriate open-source or proprietary licenses based on your distribution needs and dependency constraints.

What's the best way to set up the DESCRIPTION file for CRAN submission licensing?

Setting up the DESCRIPTION file for CRAN submission requires correctly declaring your package license. This Skill demonstrates the correct configurations for DESCRIPTION, LICENSE, and .Rbuildignore files to ensure CRAN compliance.

How does license compatibility work when bundling third party code in an R package?

License compatibility when bundling third party code in an R package depends on matching restrictive and permissive license terms. This Skill provides a compatibility matrix and advises on correctly incorporating external code snippets or libraries without violating terms.

Do I need a separate LICENSE file for my R package data?

You need specific licensing configurations for R package data, as data licensing differs from code licensing. This Skill addresses specific scenarios for data licensing, ensuring you apply the correct copyright and attribution rules for CRAN submission.

Can I use a proprietary license for an R package submitted to CRAN?

You can use certain proprietary licenses for an R package submitted to CRAN, provided they meet the repository's specific open-source and attribution requirements. This Skill guides you through configuring proprietary licenses while ensuring compliance.