license-enforcement

Audit public evidence of unlicensed skill use and prepare compliance outreach.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/franklinbaldo/skills --skill license-enforcement-franklinbaldo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: license-enforcement
Source: https://github.com/franklinbaldo/skills/tree/main/license-enforcement
Command: npx skills add https://github.com/franklinbaldo/skills --skill license-enforcement-franklinbaldo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Investigating whether a company or product is using licensed skill material without permission is error-prone: similarity gets mistaken for proof, unknown license status gets treated as unlicensed, and premature accusations create legal risk. This Skill turns weak public signals into a reviewable, provenance-rich evidence record while keeping humans in control of every external action. ## Core Features & Use Cases - Evidence classification: Distinguishes exact protected expression, distinctive arrangement, adaptation, attribution remnants, and mere idea/method similarity, with low/medium/high confidence ratings. - Structured case bundles: Builds a YAML case record with frozen source commits, stable target locators, counterevidence, license status, and a signal/verified-use/actionable-concern classification. - Human-gated outreach: Drafts neutral compliance inquiries, retroactive licensing offers, and formal notices only after explicit human approval, never inventing prices or debts. - Self-audit mode: Lets users check whether their own workflow requires an Operational License under Skill Use License 0.1. - Use Case: You spot a public repository whose agent skill closely mirrors one of yours. The Skill freezes both versions, classifies each match, checks for an existing license, and produces a decision packet for you to approve before any contact. ## Quick Start Ask the agent to investigate whether a specific public repository is using material from franklinbaldo/skills without an Operational License and produce an evidence bundle for review.

Frequently Asked Questions about license-enforcement

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

FAQPage Schema
How do I investigate unlicensed use of my open-source skill?▼

Freeze the source material to a specific commit, collect public target artifacts with stable locators, classify each match by evidentiary type, and build a structured case bundle. The Skill then checks license status and classifies the case as signal, verified use, or actionable concern.

How to tell copyright infringement from idea similarity?▼

Copyright protects expression, not ideas, methods, or functionality. The evidence model separates exact prose or code copying and distinctive arrangement from functional or methodological similarity, which alone is weak or non-actionable.

Can the agent contact a suspected infringer automatically?▼

No. All external contact, formal notices, takedowns, and legal escalation require explicit human approval. The agent only prepares a decision packet with evidence, counterevidence, and proposed next steps for a human to decide.

What if the target has a private license I cannot see?▼

Unknown license status is recorded as unknown, never unlicensed. The Skill checks available rights-holder records for paid licenses or written permission before classifying a case as an actionable concern.

Can I use this to audit my own license compliance?▼

Yes. Self-audit mode identifies which repository material your workflow loads, distinguishes evaluation from productive use, checks existing licenses, and drafts an inquiry to the licensor if a paid Operational License appears necessary.