Dependency Licence Audit

Use when a dependency licence may block publishing or selling, or a component swap needs pricing.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add SamueleBassoli/hermes-fleet-apps --skill dependency-licence-audit
Manual install
git clone --depth 1 https://github.com/SamueleBassoli/hermes-fleet-apps.git /tmp/hermes-fleet-apps
mkdir -p ~/.claude/skills
cp -r /tmp/hermes-fleet-apps/roles/coordinator/skills/dependency-licence-audit ~/.claude/skills/dependency-licence-audit

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Dependency licence audit

For answering "can I publish this / sell this, and what is blocking me" — and
the question that always follows: "what does it cost to swap the offending
component out?" Also covers weighing a swap to a more permissive component.

The owner builds tools they intend to open-source. They are not a lawyer and
neither are you: the job is to establish **facts about which artifact carries
which licence** and **what a swap actually costs in code and data**, then give
them options.

## Always-on rules

- **Verify a licence by reading the licence file, never a search snippet or a
  vendor page.** Vendors who sell commercial licences write marketing copy that
  is ambiguous on purpose.
- **Never promise "the same quality" from a replacement.** Headline benchmarks
  are saturated and say nothing about the user's own data. Promise a
  measurement instead, against the project's own evaluation set.
- **Say plainly when an option is paid or cloud-hosted.** It is the last resort,
  not a peer option — local and FOSS is the default.
- **Separate what you ran and saw from what you believe.** "I read the LICENSE
  file" and "I expect this model is weaker" are different claims and must not be
  delivered in the same voice.

## Procedure

### 1. Name the artifacts separately

One project ships several things under several licences. Enumerate before
concluding anything:

| artifact | typical licence | who it binds |
|---|---|---|
Read the full skill on GitHub

Details

Skill name
dependency-licence-audit
Path
roles/coordinator/skills/dependency-licence-audit/SKILL.md
License
MIT
Repo updated
31 October 2026

FAQ

What does the Dependency Licence Audit skill do?

Use when a dependency licence may block publishing or selling, or a component swap needs pricing.

How do I install the Dependency Licence Audit skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add SamueleBassoli/hermes-fleet-apps --skill dependency-licence-audit. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Dependency Licence Audit popular?

It lives in SamueleBassoli/hermes-fleet-apps, which has 44 GitHub stars and 0 forks.

Related skills

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.