From slim-rebranding
Detects project type and adds Apache 2.0 or MIT open source licenses to repositories, including NASA JPL variants with institutional copyright headers. Ideal for new projects, OSS conversion, or compliance.
npx claudepluginhub nasa-ammos/slim --plugin slim-rebrandingThis skill uses the workspace's default tool permissions.
This skill helps you add appropriate open source licenses to your project. It supports both standard open source licenses and NASA JPL variants with institutional copyright headers.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Monitors deployed URLs for regressions in HTTP status, console errors, performance metrics, content, network, and APIs after deploys, merges, or upgrades.
Provides React and Next.js patterns for component composition, compound components, state management, data fetching, performance optimization, forms, routing, and accessible UIs.
This skill helps you add appropriate open source licenses to your project. It supports both standard open source licenses and NASA JPL variants with institutional copyright headers.
First, check if a LICENSE file already exists in the repository root:
ls -la LICENSE*
If a license exists, ask the user if they want to replace it or keep it.
Ask the user:
Which license would you like to use?
Is this a NASA JPL project?
Based on the user's choices, copy the appropriate license file from the assets directory:
assets/LICENSE-APACHE-JPLassets/LICENSE-MIT-JPLassets/LICENSE-APACHEassets/LICENSE-MITCopy the selected file to the repository root as LICENSE:
cp assets/LICENSE-[TYPE] LICENSE
Remind the user to:
Choose Apache 2.0 when:
Choose MIT when:
Use JPL variant when:
LICENSE-APACHE: Standard Apache 2.0 LicenseLICENSE-APACHE-JPL: Apache 2.0 with JPL/Caltech copyrightLICENSE-MIT: Standard MIT LicenseLICENSE-MIT-JPL: MIT with JPL/Caltech copyright