licensing

Verify and document software dependency licenses for project compliance.

2|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/air-gapped/cooked --skill licensing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: licensing
Source: https://github.com/air-gapped/cooked/tree/main/.claude/skills/licensing
Command: npx skills add https://github.com/air-gapped/cooked --skill licensing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams prevent license violations by auditing and documenting dependency licenses before adding them to a project.

Core Features & Use Cases

  • License compatibility checks across common open-source licenses.
  • Documentation of compatible licenses and recommended alternatives.
  • Use Case: When integrating a new library, verify its license against project licensing rules and track compliance.

Quick Start

Run an automated license check on any new dependency before adding it. Review the results, and record license decisions in the project docs. Integrate license checks into the PR workflow to prevent non-compliant imports.

Frequently Asked Questions about licensing

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

FAQPage Schema
How do I check open-source dependency licenses for compliance before importing them?

You check open-source dependency licenses by running an automated license verification against your project's licensing policy before adding the dependency. This skill audits and documents compatibility to ensure compliance before integration.

How do I verify license compatibility for a new library?

To verify license compatibility, evaluate the new library's license against your project's established licensing rules. This process identifies compatible open-source licenses and documents recommended alternatives to prevent violations.

When do I need to perform a dependency license check?

You need to perform a dependency license check when integrating a new library into your project. Running automated verification during this phase prevents non-compliant imports before they enter your codebase.

What is the best way to integrate license checks into a continuous integration workflow?

The best way to integrate license checks is to run automated verification on any new dependency directly within your PR workflow. This prevents non-compliant imports and records license decisions in project docs.

Can this skill document compatible licenses and track compliance for my team?

Yes, the skill documents compatible licenses and tracks compliance by generating clear reporting for teams. It records license decisions in project documentation to maintain an auditable compliance trail.

Does automated license verification work with common open-source licenses?

Yes, automated license verification evaluates common open-source licenses to ensure compatibility. It covers evaluating standard license types and guiding license-aware dependency selection based on your project policy.