slim-license

Apply standard or NASA/JPL software licenses to project repositories.

35|14|Updated Feb 16, 2022

Search Tags:#open source #compliance #license #NASA #JPL #project licensing

Ready to run

npx skills add https://github.com/NASA-AMMOS/slim --skill slim-license

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: slim-license
Source: https://github.com/NASA-AMMOS/slim/tree/main/static/marketplace/skills/slim-license
Command: npx skills add https://github.com/NASA-AMMOS/slim --skill slim-license

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill automates the process of selecting and applying the correct software license to a project, ensuring compliant usage of standard OSS licenses or NASA/JPL institutional variants.

Core Features & Use Cases

Supports standard licenses (Apache 2.0, MIT) and NASA JPL variants with institutional headers.
Copies the chosen LICENSE file from assets to the repository root and verifies accompanying headers and documentation references.
Use Case: Starting a new project or open sourceing an existing one, apply the appropriate license to ensure legal clarity and consistent licensing across teams.

Quick Start

Place your project at the root, select a license variant, and run the license writer workflow to copy the corresponding license from assets to the project root.

Frequently Asked Questions about slim-license

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

FAQPage Schema

How do I apply an open source license to my project repository?▼

To apply an open source license, select a license variant and run the workflow to copy the corresponding LICENSE file to your project root, ensuring legal clarity and consistent compliance across teams.

What is the best way to add a NASA or JPL institutional license to government-funded software?▼

Adding a NASA or JPL institutional license involves selecting the specific institutional variant to deploy the correct license text with appropriate headers for public and government-funded repositories.

Can I use standard Apache 2.0 or MIT licenses for my open source project?▼

Yes, you can use standard licenses like Apache 2.0 and MIT to ensure compliant usage for public repositories, with the workflow copying the chosen license file directly to the project root.

Do I need external dependencies to apply a software license to my repository?▼

No external dependencies are required to apply a software license, as the workflow relies solely on internal assets to copy the license text and verify accompanying documentation references.

What documentation should I update after applying a project license?▼

After applying a project license, you should update file headers, repository badges, and documentation references to ensure complete legal clarity and consistent licensing across the codebase.