Keep organic, paid, and partnership-ad permissions distinct for every supplied asset.
v0.1.0
Example draft · Input and output · How to useExample draft
A fictional permission packet with asset, proposed use, date, territory and permission evidence.
cup-photo / organic: ready for owner review cup-photo / paid: blocked, organic-only scope old-release: blocked, expired before the use date music-reel: pending, music rights unresolved The checker preserves scope, dates, editing permissions, and evidence references for each component.
An executed example using fictional releases. Public post metadata is not consent; ready for owner review is not legal clearance.
Asset references, proposed use/date/territory, and permission evidence with scope and conditions.
A use-specific permission ledger, missing-evidence queue, and draft permission questions.
An Agent and Node.js 18+. Supplied permission packets work offline; optional post metadata lookup requires SandBase.
Download and unpack the complete Skill folder, keep its references, and use it with a local Agent that supports Skills.
Use instagram-ugc-rights with my supplied material. Keep organic, paid, and partnership-ad permissions distinct for every supplied asset.