skills.rest
ksoichiro
ksoichiroCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

license-compliance

Audit dependencies and generate THIRD_PARTY_LICENSES.md for LGPL-3.0 compliance.

Updated Oct 19, 2025
Search Tags:#distribution#open-source#license-headers#license-compliance#dependency-audit#LGPL-3.0#third-party-licenses
One-click install
npx skills add https://github.com/ksoichiro/ChronoDawn --skill license-compliance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: license-compliance
Source: https://github.com/ksoichiro/ChronoDawn/tree/main/.claude/skills/license-compliance
Command: npx skills add https://github.com/ksoichiro/ChronoDawn --skill license-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides clear guidance to ensure LGPL-3.0 license compliance throughout Chrono Dawn development, covering dependency reviews, header insertion, and distribution licensing.

Core Features & Use Cases

  • License auditing: Identify LGPL-3.0 requirements and verify all dependencies and libraries meet them.
  • Documentation generation: Create and maintain a THIRD_PARTY_LICENSES.md with project name, version, developer, license type, project URL, and license URL for each dependency.
  • License headers guidance: Offer templates and best practices for header insertion in core files and platform entry points to comply with LGPL-3.0.

Quick Start

Describe your planned dependency update or distribution task, and I will generate a compliant license plan, header templates, and a license inventory.

Frequently Asked Questions about license-compliance

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

FAQPage Schema
How do I generate a third-party license inventory for LGPL-3.0 compliance?▼

To generate a third-party license inventory for LGPL-3.0 compliance, describe your dependency update or distribution task. The skill produces a THIRD_PARTY_LICENSES.md file containing the project name, version, developer, license type, project URL, and license URL for each dependency.

What are the LGPL-3.0 license header requirements for core files and platform entry points?▼

LGPL-3.0 license header requirements for core files and platform entry points involve inserting standardized header templates. The skill offers best practices and templates to ensure proper header inclusion across core and platform-specific code to maintain distribution compliance.

How do I audit dependencies to verify they meet LGPL-3.0 requirements?▼

To audit dependencies and verify they meet LGPL-3.0 requirements, the skill performs license tracking and reviews your planned dependency updates. It identifies specific LGPL-3.0 requirements to ensure all libraries conform before distribution.

When do I need to update my THIRD_PARTY_LICENSES.md file during development?▼

You need to update your THIRD_PARTY_LICENSES.md file during dependency management and distribution tasks. The skill standardizes license tracking to help you maintain accurate documentation whenever you add, update, or remove libraries in your project.

Related Skills

Explore More Legal & Compliance Skills→
MearmanMearman
3

pypi-package-info

Retrieve PyPI package metadata including versions, licenses, and dependencies.

Community
Intermediate
leaderiopleaderiop
7

Packages Graph

Parse package manifests, construct graphs, and generate compliance reports.

Community
Intermediate
betobeticobetobetico
35

revisor-licencias-oss

Classify open-source software licenses and determine copyleft strength from dependency inventories.

Community
Intermediate
choxoschoxos

licensing

Guide R package license selection and configuration for CRAN submission.

Community
Intermediate