asset-license-checker
Purpose
Catch license risk before assets go into a scene that will be rendered, exported, or shipped. This is a planning / validation skill — does not modify assets, does not consult lawyers.
Quick start
- Receive the sourced external asset list from
asset-discovery (models, textures, HDRIs, fonts, sounds, brushes).
- Record source URL, documented license name, and stated permissions per asset.
- Flag risk per asset (
Pass / Warn / Fail) and specify required attribution lines and attribution plan.
- Gate progression: hand off to
asset-style-check, asset-library-plan, or workflow-stage-router only if all rows are Pass or explicitly accepted Warn; route any Fail rows to asset-fallback-strategy.
When to use
- Immediately after
asset-discovery produces a candidate asset list.
- Before handing off to
asset-style-check, asset-library-plan, or scene planners (product-hero-scene-planner, character-portrait, environment-shot, interior-scene, product-grid-scene-planner).
- Before
pre-handoff-verification, render-export-evidence, glb-web-handoff, or glb-animation-handoff.
- Whenever a previously sourced asset's license or attribution requirement is unclear.
When not to use
- Sourcing or searching for candidate assets → use
../asset-discovery/SKILL.md (Delegates out-of-scope requests to asset-discovery)
- Checking visual consistency, scale, or aesthetic fit across assets → use
../asset-style-check/SKILL.md (Delegates out-of-scope requests to asset-style-check)
- Replacing or working around rejected/blocked assets → use
../asset-fallback-strategy/SKILL.md (Delegates out-of-scope requests to asset-fallback-strategy)
- Structuring folders, naming conventions, or catalog storage → use
../asset-library-plan/SKILL.md (Delegates out-of-scope requests to asset-library-plan)
- First-party assets authored entirely in-house with no external dependencies. → use
../asset-discovery/SKILL.md (Delegates out-of-scope requests to asset-discovery)
- Legal advice or binding legal interpretation (this skill flags risk only; escalate ambiguity to legal). → use
../asset-style-check/SKILL.md (Delegates out-of-scope requests to asset-style-check)
Trigger phrases
- "is this license OK"
- "can I use this commercially"
- "what's the license"
- "license check"
Prerequisites / readiness
- Sourced asset list from
asset-discovery with source URLs/origins recorded.
- Intended use case stated (commercial, non-commercial, internal, or open-source).
- Target attribution plan defined (where and how attribution lines will be rendered, or whether attribution cannot be supported).
Input schema
Required inputs
| Input |
Why it is required |
| Asset list (name + source) |
Scope of check |
| Intended use case |
Drives compatibility |
| Target attribution policy |
Some licenses require attribution |
Optional inputs
| Input |
Use |
| Existing internal license whitelist |
Pre-approved sources |
| Brand legal policy |
Per-company override rules |
Assumptions to confirm
- Asset license file or page is publicly readable.
- License version is current (licenses sometimes change).
- The user's intended use is accurately stated.
Output schema
Primary output
A per-asset row table: asset name, source URL, documented license name, attribution required (Y/N), commercial allowed (Y/N), modification allowed (Y/N), redistribution allowed (Y/N), validation verdict (Pass / Warn / Fail), and notes.
Secondary output
- Required attribution lines and attribution rendering plan (where applicable).
- Blocked assets (
Fail) routed to asset-fallback-strategy.
- Top-line gate status (
Pass / Warn / Fail).
Evidence / caveat output
Validation verdicts (Pass / Warn / Fail) apply per asset and are separate from runtime and artifact truth states. Truth states are downgrade-only (never upgrade), and Artifact status defaults to Not Produced:
Runtime status: Not Run | Attempted | Produced | Verified | Failed
Artifact status: Not Produced | Produced | Verified | Failed
Evidence used: <links, paths, logs, or "none">
Limitations: <known gaps>
Required laws
../../laws/evidence-before-done.md
../../laws/non-blender-user-language.md
../../laws/no-arbitrary-python-interface.md
../../laws/official-runtime-only.md
Official runtime boundary
Validation skill — does not modify assets, does not run Blender. Verdicts are based on documented license terms, not legal interpretation. Not legal advice: when in doubt, recommend the user consult their legal team.
Operating procedure
- Ingest the external asset list from
asset-discovery.
- Ensure every external asset has its own row; unknown or missing license immediately blocks use (
Fail).
- Look up documented license terms per
references/license-source-rules.md (do not interpret ambiguous legal language).
- Map documented permissions (commercial, modification, redistribution, attribution) against the stated intended use and attribution plan.
- Assign a per-asset validation verdict (
Pass / Warn / Fail) separate from runtime/artifact truth states.
- Compile exact attribution lines and verify an attribution plan exists wherever attribution is required.
- Route any
Fail assets to asset-fallback-strategy (or back to asset-discovery for re-sourcing).
- Gate downstream progression: proceed to
asset-style-check, asset-library-plan, or workflow-stage-router only if all rows are Pass or explicitly accepted Warn.
Decision tree
License unknown, missing, or unverified source?
→ Fail (blocks use until source and license are confirmed)
"CC0 / public domain" with documented dedication?
→ Pass for the stated use (still record attribution plan as N/A)
Documented terms forbid intended use (e.g., non-commercial-only license for a commercial project, or no modification/redistribution when required)?
→ Fail (route asset to asset-fallback-strategy)
Attribution required by license, but no attribution plan exists?
→ Fail (blocks use until attribution plan is confirmed)
Documented terms permit intended use, but contain ambiguity?
→ Warn (escalate ambiguity to legal; requires explicit user/legal acceptance to proceed)
Playbooks
Playbook A: Commercial delivery
Require explicit documented commercial permission for every asset row. If attribution is required, verify the attribution plan is approved before gating; otherwise mark Fail and route to asset-fallback-strategy. Escalate any custom or ambiguous terms to legal.
Playbook B: Internal / non-commercial review
Verify documented terms cover internal or non-commercial use. Track all required attribution lines so internal prototypes cannot advance to commercial handoff (pre-handoff-verification) without re-running asset-license-checker.
Playbook C: Redistributed or shared package
Verify documented redistribution and modification permissions for every external asset row, ensure package-level attribution lines are included in the attribution plan, and escalate cross-license compatibility questions to legal.
Mode handling
Text-only mode
Evaluate license rows strictly from the provided asset specification and documented source text. No Python and no Blender execution. Set Runtime status: Not Run and Artifact status: Not Produced (downgrade-only, never upgrade).
Runtime-ready mode
Evaluate license rows against user-supplied license files or manifest records. Maintain Runtime status: Not Run (this skill never runs Blender) and downgrade truth states if any expected documentation artifact is missing.
Blocked runtime mode
If source URLs or license files are unreadable or missing, assign per-asset verdict Fail (unknown license blocks use), keep Artifact status: Not Produced, and route blocked assets to asset-fallback-strategy.
Validation checklist
Pass / Warn / Fail rubric
| Verdict |
Criteria |
| Pass |
License is explicitly documented, permissions match intended use, and required attribution is covered by a concrete attribution plan. |
| Warn |
Documented permissions appear compatible, but terms contain ambiguity requiring legal review or the attribution plan needs explicit user confirmation. |
| Fail |
License is unknown/missing, documented terms forbid intended use, attribution is required without an attribution plan, or rights are reserved without explicit permission. |
Failure handling
- Unknown or missing license → assign
Fail and block asset use immediately.
- Attribution required without a rendering plan → assign
Fail and block until an attribution plan is established.
- Vague or unverified assurance ("probably fine") → never assign
Pass; mark Warn (if documented terms exist but need legal review) or Fail (if undocumented), and escalate ambiguity to legal.
- Any
Fail verdict → block downstream scene progression and hand off rejected assets to asset-fallback-strategy or asset-discovery.
- Truth states → downgrade-only; never upgrade
Runtime status or Artifact status.
Troubleshooting
| Problem |
Response |
| License page unreachable / missing |
Assign Fail (unknown license blocks use); route to asset-fallback-strategy or asset-discovery. |
| License terms changed since download |
Flag as Warn or Fail depending on whether dated proof of prior terms exists; do not assume grandfathering — escalate to legal. |
| Mixed-license asset bundle |
Split bundle so every individual external sub-asset gets its own row and verdict. |
| AI-generated external asset |
Treat as unknown/ambiguous unless platform terms are explicitly documented for the intended use; escalate ambiguity to legal. |
Best practices
- Record license at acquisition time, not at build time.
- Maintain an internal whitelist for repeat sources.
- Never ship without verifying every external asset's license.
- "Not legal advice" — escalate ambiguity to legal.
Good examples
- "Asset:
studio_hdri.exr, source: documented vendor URL, license: explicitly documented public-domain/permissive terms, commercial: Y, mod: Y, redist: Y, attribution: N. Verdict: Pass."
- "Asset:
hero_chair.glb, source: documented marketplace URL, license: attribution-required license, commercial: Y, attribution plan: credits screen line recorded. Verdict: Pass."
Bad examples
- "Asset is from internet." — no source, no license.
User-facing response template
Intended use: <commercial / non-commercial / internal / open-source>
Attribution plan: <where attribution will render or "none">
| Asset | Source | License | Comm | Mod | Redist | Attribution | Verdict | Notes |
|---|---|---|---|---|---|---|---|---|
Required attribution lines:
- <line 1 or "none">
Assets blocked (Fail — route to asset-fallback-strategy): <list or "none">
Top-line gate verdict: <Pass / Warn / Fail>
Note: Not legal advice; escalate any license ambiguity to your legal team.
Runtime status: Not Run | Attempted | Produced | Verified | Failed
Artifact status: Not Produced | Produced | Verified | Failed (default: Not Produced)
Evidence used: <links, paths, logs, or "none">
Limitations: <known gaps>
Next: <if all Pass or explicitly accepted Warn: asset-style-check / asset-library-plan / workflow-stage-router | if any Fail: asset-fallback-strategy / asset-discovery>
Anti-patterns
- "Should be fine" verdicts.
- Skipping the attribution plan.
- Treating "all rights reserved" assets as usable.
- Inventing license terms.
Cross-skill handoff
- [upstream_reference] Upstream asset sourcing →
../asset-discovery/SKILL.md
- [progression] Visual style validation →
../asset-style-check/SKILL.md
- [fallback] Rejected/blocked asset handling →
../asset-fallback-strategy/SKILL.md
- [progression] Asset library organization →
../asset-library-plan/SKILL.md
- [progression] Stage routing & scene planning gate →
../workflow-stage-router/SKILL.md
Non-goals
- Give legal advice or interpret complex contracts (escalate ambiguity to legal).
- Source or discover candidate assets (
asset-discovery).
- Check visual style or aesthetic consistency (
asset-style-check).
- Plan fallbacks or replacements for failed assets (
asset-fallback-strategy).
- Organize asset libraries or folder structures (
asset-library-plan).
- Modify asset files, write Python, or run Blender.
References
references/common-license-mapping.md
references/license-source-rules.md
references/attribution-rendering-patterns.md
../../docs/skill-system.md
1---2name: asset-license-checker3description: Audit commercial rights, CC-BY attribution, NC/SA traps, and brand/trademark restrictions for downloaded 3D meshes, HDRIs, textures, and fonts.4metadata:5 source: https://skillmd.com/skills/thanhnguyxnorg/asset-license-checker6---78# asset-license-checker910## Purpose11Catch license risk before assets go into a scene that will be rendered, exported, or shipped. This is a planning / validation skill — does not modify assets, does not consult lawyers.1213## Quick start14- Receive the sourced external asset list from `asset-discovery` (models, textures, HDRIs, fonts, sounds, brushes).15- Record source URL, documented license name, and stated permissions per asset.16- Flag risk per asset (`Pass` / `Warn` / `Fail`) and specify required attribution lines and attribution plan.17- Gate progression: hand off to `asset-style-check`, `asset-library-plan`, or `workflow-stage-router` only if all rows are `Pass` or explicitly accepted `Warn`; route any `Fail` rows to `asset-fallback-strategy`.1819## When to use20- Immediately after `asset-discovery` produces a candidate asset list.21- Before handing off to `asset-style-check`, `asset-library-plan`, or scene planners (`product-hero-scene-planner`, `character-portrait`, `environment-shot`, `interior-scene`, `product-grid-scene-planner`).22- Before `pre-handoff-verification`, `render-export-evidence`, `glb-web-handoff`, or `glb-animation-handoff`.23- Whenever a previously sourced asset's license or attribution requirement is unclear.2425## When not to use26<!-- blendops:generated:start exclusions -->27- Sourcing or searching for candidate assets → use `../asset-discovery/SKILL.md` (Delegates out-of-scope requests to asset-discovery)28- Checking visual consistency, scale, or aesthetic fit across assets → use `../asset-style-check/SKILL.md` (Delegates out-of-scope requests to asset-style-check)29- Replacing or working around rejected/blocked assets → use `../asset-fallback-strategy/SKILL.md` (Delegates out-of-scope requests to asset-fallback-strategy)30- Structuring folders, naming conventions, or catalog storage → use `../asset-library-plan/SKILL.md` (Delegates out-of-scope requests to asset-library-plan)31- First-party assets authored entirely in-house with no external dependencies. → use `../asset-discovery/SKILL.md` (Delegates out-of-scope requests to asset-discovery)32- Legal advice or binding legal interpretation (this skill flags risk only; escalate ambiguity to legal). → use `../asset-style-check/SKILL.md` (Delegates out-of-scope requests to asset-style-check)33<!-- blendops:generated:end exclusions -->3435## Trigger phrases36<!-- blendops:generated:start triggers -->37- "is this license OK"38- "can I use this commercially"39- "what's the license"40- "license check"41<!-- blendops:generated:end triggers -->4243## Prerequisites / readiness44- Sourced asset list from `asset-discovery` with source URLs/origins recorded.45- Intended use case stated (commercial, non-commercial, internal, or open-source).46- Target attribution plan defined (where and how attribution lines will be rendered, or whether attribution cannot be supported).4748## Input schema4950### Required inputs5152| Input | Why it is required |53|---|---|54| Asset list (name + source) | Scope of check |55| Intended use case | Drives compatibility |56| Target attribution policy | Some licenses require attribution |5758### Optional inputs5960| Input | Use |61|---|---|62| Existing internal license whitelist | Pre-approved sources |63| Brand legal policy | Per-company override rules |6465### Assumptions to confirm66- Asset license file or page is publicly readable.67- License version is current (licenses sometimes change).68- The user's intended use is accurately stated.6970## Output schema7172### Primary output73A per-asset row table: asset name, source URL, documented license name, attribution required (Y/N), commercial allowed (Y/N), modification allowed (Y/N), redistribution allowed (Y/N), validation verdict (`Pass` / `Warn` / `Fail`), and notes.7475### Secondary output76- Required attribution lines and attribution rendering plan (where applicable).77- Blocked assets (`Fail`) routed to `asset-fallback-strategy`.78- Top-line gate status (`Pass` / `Warn` / `Fail`).7980### Evidence / caveat output81Validation verdicts (`Pass` / `Warn` / `Fail`) apply per asset and are separate from runtime and artifact truth states. Truth states are downgrade-only (never upgrade), and `Artifact status` defaults to `Not Produced`:8283```txt84Runtime status: Not Run | Attempted | Produced | Verified | Failed85Artifact status: Not Produced | Produced | Verified | Failed86Evidence used: <links, paths, logs, or "none">87Limitations: <known gaps>88```8990## Required laws91- `../../laws/evidence-before-done.md`92- `../../laws/non-blender-user-language.md`93- `../../laws/no-arbitrary-python-interface.md`94- `../../laws/official-runtime-only.md`9596## Official runtime boundary9798Validation skill — does not modify assets, does not run Blender. Verdicts are based on documented license terms, not legal interpretation. **Not legal advice**: when in doubt, recommend the user consult their legal team.99100## Operating procedure1011021. Ingest the external asset list from `asset-discovery`.1032. Ensure every external asset has its own row; unknown or missing license immediately blocks use (`Fail`).1043. Look up documented license terms per `references/license-source-rules.md` (do not interpret ambiguous legal language).1054. Map documented permissions (commercial, modification, redistribution, attribution) against the stated intended use and attribution plan.1065. Assign a per-asset validation verdict (`Pass` / `Warn` / `Fail`) separate from runtime/artifact truth states.1076. Compile exact attribution lines and verify an attribution plan exists wherever attribution is required.1087. Route any `Fail` assets to `asset-fallback-strategy` (or back to `asset-discovery` for re-sourcing).1098. Gate downstream progression: proceed to `asset-style-check`, `asset-library-plan`, or `workflow-stage-router` only if all rows are `Pass` or explicitly accepted `Warn`.110111## Decision tree112113```txt114License unknown, missing, or unverified source?115 → Fail (blocks use until source and license are confirmed)116"CC0 / public domain" with documented dedication?117 → Pass for the stated use (still record attribution plan as N/A)118Documented terms forbid intended use (e.g., non-commercial-only license for a commercial project, or no modification/redistribution when required)?119 → Fail (route asset to asset-fallback-strategy)120Attribution required by license, but no attribution plan exists?121 → Fail (blocks use until attribution plan is confirmed)122Documented terms permit intended use, but contain ambiguity?123 → Warn (escalate ambiguity to legal; requires explicit user/legal acceptance to proceed)124```125126## Playbooks127128### Playbook A: Commercial delivery129130Require explicit documented commercial permission for every asset row. If attribution is required, verify the attribution plan is approved before gating; otherwise mark `Fail` and route to `asset-fallback-strategy`. Escalate any custom or ambiguous terms to legal.131132### Playbook B: Internal / non-commercial review133134Verify documented terms cover internal or non-commercial use. Track all required attribution lines so internal prototypes cannot advance to commercial handoff (`pre-handoff-verification`) without re-running `asset-license-checker`.135136### Playbook C: Redistributed or shared package137138Verify documented redistribution and modification permissions for every external asset row, ensure package-level attribution lines are included in the attribution plan, and escalate cross-license compatibility questions to legal.139140## Mode handling141142### Text-only mode143Evaluate license rows strictly from the provided asset specification and documented source text. No Python and no Blender execution. Set `Runtime status: Not Run` and `Artifact status: Not Produced` (downgrade-only, never upgrade).144145### Runtime-ready mode146Evaluate license rows against user-supplied license files or manifest records. Maintain `Runtime status: Not Run` (this skill never runs Blender) and downgrade truth states if any expected documentation artifact is missing.147148### Blocked runtime mode149If source URLs or license files are unreadable or missing, assign per-asset verdict `Fail` (unknown license blocks use), keep `Artifact status: Not Produced`, and route blocked assets to `asset-fallback-strategy`.150151## Validation checklist152- [ ] Every external asset has a dedicated row in the table.153- [ ] Source URL and documented license name are recorded per row (unknown license marked `Fail`).154- [ ] Permissions per row recorded (`commercial` / `modification` / `redistribution` / `attribution`).155- [ ] Per-asset validation verdict (`Pass` / `Warn` / `Fail`) assigned separately from truth states.156- [ ] Required attribution lines and attribution plan recorded where applicable.157- [ ] Runtime and artifact truth states included (`Artifact status` defaults to `Not Produced`; downgrade-only).158- [ ] Scene gate enforced: downstream handoff allowed only on all-`Pass` or explicitly accepted `Warn`; `Fail` rows routed to `asset-fallback-strategy`.159160## Pass / Warn / Fail rubric161162| Verdict | Criteria |163| --- | --- |164| Pass | License is explicitly documented, permissions match intended use, and required attribution is covered by a concrete attribution plan. |165| Warn | Documented permissions appear compatible, but terms contain ambiguity requiring legal review or the attribution plan needs explicit user confirmation. |166| Fail | License is unknown/missing, documented terms forbid intended use, attribution is required without an attribution plan, or rights are reserved without explicit permission. |167168## Failure handling169- Unknown or missing license → assign `Fail` and block asset use immediately.170- Attribution required without a rendering plan → assign `Fail` and block until an attribution plan is established.171- Vague or unverified assurance ("probably fine") → never assign `Pass`; mark `Warn` (if documented terms exist but need legal review) or `Fail` (if undocumented), and escalate ambiguity to legal.172- Any `Fail` verdict → block downstream scene progression and hand off rejected assets to `asset-fallback-strategy` or `asset-discovery`.173- Truth states → downgrade-only; never upgrade `Runtime status` or `Artifact status`.174175## Troubleshooting176177| Problem | Response |178|---|---|179| License page unreachable / missing | Assign `Fail` (unknown license blocks use); route to `asset-fallback-strategy` or `asset-discovery`. |180| License terms changed since download | Flag as `Warn` or `Fail` depending on whether dated proof of prior terms exists; do not assume grandfathering — escalate to legal. |181| Mixed-license asset bundle | Split bundle so every individual external sub-asset gets its own row and verdict. |182| AI-generated external asset | Treat as unknown/ambiguous unless platform terms are explicitly documented for the intended use; escalate ambiguity to legal. |183184## Best practices185- Record license at acquisition time, not at build time.186- Maintain an internal whitelist for repeat sources.187- Never ship without verifying every external asset's license.188- "Not legal advice" — escalate ambiguity to legal.189190## Good examples191- "Asset: `studio_hdri.exr`, source: documented vendor URL, license: explicitly documented public-domain/permissive terms, commercial: Y, mod: Y, redist: Y, attribution: N. Verdict: `Pass`."192- "Asset: `hero_chair.glb`, source: documented marketplace URL, license: attribution-required license, commercial: Y, attribution plan: credits screen line recorded. Verdict: `Pass`."193194## Bad examples195- "Asset is from internet." — no source, no license.196197## User-facing response template198199```txt200Intended use: <commercial / non-commercial / internal / open-source>201Attribution plan: <where attribution will render or "none">202203| Asset | Source | License | Comm | Mod | Redist | Attribution | Verdict | Notes |204|---|---|---|---|---|---|---|---|---|205206Required attribution lines:207 - <line 1 or "none">208209Assets blocked (Fail — route to asset-fallback-strategy): <list or "none">210Top-line gate verdict: <Pass / Warn / Fail>211Note: Not legal advice; escalate any license ambiguity to your legal team.212213Runtime status: Not Run | Attempted | Produced | Verified | Failed214Artifact status: Not Produced | Produced | Verified | Failed (default: Not Produced)215Evidence used: <links, paths, logs, or "none">216Limitations: <known gaps>217Next: <if all Pass or explicitly accepted Warn: asset-style-check / asset-library-plan / workflow-stage-router | if any Fail: asset-fallback-strategy / asset-discovery>218```219220## Anti-patterns221- "Should be fine" verdicts.222- Skipping the attribution plan.223- Treating "all rights reserved" assets as usable.224- Inventing license terms.225226## Cross-skill handoff227<!-- blendops:generated:start handoffs -->228- [upstream_reference] Upstream asset sourcing → `../asset-discovery/SKILL.md`229- [progression] Visual style validation → `../asset-style-check/SKILL.md`230- [fallback] Rejected/blocked asset handling → `../asset-fallback-strategy/SKILL.md`231- [progression] Asset library organization → `../asset-library-plan/SKILL.md`232- [progression] Stage routing & scene planning gate → `../workflow-stage-router/SKILL.md`233<!-- blendops:generated:end handoffs -->234235## Non-goals236- Give legal advice or interpret complex contracts (escalate ambiguity to legal).237- Source or discover candidate assets (`asset-discovery`).238- Check visual style or aesthetic consistency (`asset-style-check`).239- Plan fallbacks or replacements for failed assets (`asset-fallback-strategy`).240- Organize asset libraries or folder structures (`asset-library-plan`).241- Modify asset files, write Python, or run Blender.242243## References244- `references/common-license-mapping.md`245- `references/license-source-rules.md`246- `references/attribution-rendering-patterns.md`247- `../../docs/skill-system.md`