- Home
- Skills
- Legal & Compliance
- Commercial License Skill
Works with the AI Agents you already use
Commercial License Skill
Review dependency and asset licenses against commercial-use, source-sharing and distribution conditions. Get versioned evidence, obligations, coverage gaps and verified replacement options.
Free
Commercial License Skill
Example session with this skill installed
Use commercial-license-skill to triage the repository's synthetic node-risk fixture. Run the separately available local CLI with snippets redacted. Report exactly what ran and its coverage; do not treat a GPL declaration as proof that commercial use is forbidden. This is a demonstration fixture, not a real third-party package.
- Read your context and instructions
- Compiled the commercial license
Actual local demonstration
Executed on 2026-10-29 using the repository CLI 0.4.0:
node ./bin/commercial-license-skill.mjs scan ./test/fixtures/node-risk --format human --no-snippets
The complete terminal output follows. The component name is fictional test metadata. This is a local CLI smoke test, not a recorded multi-agent compatibility evaluation.
CommercialLicenseSkill — commercial-safe dependency triage
Root: D:/commercial-license-skill/test/fixtures/node-risk
Summary: 1 dependencies | critical 0 | high 1 | review 0 | allow 0
Coverage: partial local inventory; 0 excluded record(s).
✗ [HIGH] npm:gpl-demo@1.0.0 — GPL-3.0-only
scope: runtime; source: package.json
Copyleft review: distribution, modifications and combination can impose source obligations. A manifest entry alone does not establish those obligations.
usage: 1 source reference(s) found
- src/index.ts:1 [js-import] [REDACTED]
note: Resolved from installed node_modules metadata.
COVERAGE: Inventory is bounded and rooted at this directory; nested workspace manifests, symlinks, unsupported lockfiles, binary contents and assets without license files may be missed. No findings is not compliance clearance.
NOTICE: This report is an engineering triage aid, not legal advice. A license name alone cannot determine obligations. Confirm exact terms, distribution model, linking/bundling, modifications, and notices with qualified counsel before release.
Exit code: 0 for this reporting command; no --fail-on threshold was requested.
Interpretation and next action
One runtime dependency needs copyleft review. The scan observed installed metadata and an import reference; it did not establish the exact distributed artifact's grant, integration facts or source obligations. Commercial use is not inherently forbidden by GPL. Obtain the versioned LICENSE/NOTICE, distribution and modification details before a release decision. No replacement was verified, no dependency was changed and no package installation ran. For a full product review, supply the remaining dependency and asset evidence and an explicit accepted-license policy.
Connects securely to your tools. The creator never sees your data.
About this skill
Review commercial-use conditions with evidence
Commercial License Skill helps AI agents review dependency and asset licenses for a commercial product. Define accepted licenses, source-sharing limits and the delivery model, then get a dated inventory of observed grants, obligations, policy mismatches and unresolved questions.
What it covers
- Direct, transitive, development and vendored code where evidence is available.
- Fonts, icons, images, model code and weights, datasets and separately licensed assets.
- SPDX expressions, exceptions, dual grants, notices and version-specific replacement options.
- Migration plans matched to the APIs and operations actually used.
How it works
Supply an accessible project, manifests/lockfiles, SBOMs, LICENSE/NOTICE files or an asset inventory. The agent separates observed declarations from interpretation, verifies primary sources when browsing is available, and reports coverage gaps. It can review supplied artifacts without a shell, API key or installation.
The package includes the workflow, five reference documents, a report template within those references, three worked examples, a quick-start README and the Apache-2.0 license. Agensi delivers these text files through MCP; it does not install the separate CLI or expose local files.
What you receive
Conditions and coverage; an evidence table with component/version, dated sources, actual use, obligations and a keep/comply, replace, remove or unresolved decision; verified candidate comparisons when supported; and the next concrete action. Implementation happens only when requested.
Requirements and limits
Fresh upstream verification needs browsing. Optional local scanning needs a separately available commercial-license-skill CLI 0.4.0 and Node.js 18.17+. CLI 0.4.0 features in the source checkout may differ from older published packages. No installation is required for the main supplied-artifact workflow.
This is engineering review guidance, not a compliance certificate or legal opinion. Commercial use and source-sharing duties are separate questions. Missing grants, unsupported ecosystems, inaccessible artifacts and disputed integration facts remain explicit. No claim of successful testing across every hosted agent is made.
Free and open source under Apache-2.0: https://github.com/Aminoragit/commercial-license-skill Third-party components retain their own licenses. No private source, reports or credentials are uploaded by this workflow. Optional online discovery sends only an approved public search query to npm. General browsing reads upstream license and release documentation. Private identifiers must stay out of external queries. Do not publish the user's artifacts without separate authorization. Higher-priority host rules and the user's scope always apply.
Reviews are limited to accessible evidence. Agensi does not install the optional CLI or grant local project access. Fresh upstream verification requires browsing. Scanning does not cover every ecosystem, binary or asset. This skill does not provide legal certification.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 19 days ago
- Free with an Agensi account
Permissions
Read only user-authorized project and license artifacts. Browser/network read upstream license and release docs; optional npm discovery sends only a public capability query. No credentials, environment variables or account connections required. Shell is only for an already available local CLI. File writes are only for explicitly requested migration or report output. No private source uploads or automatic software installation.