Every ownership, contributor, split, sample, license, provenance, and metadata fact comes back marked confirmed or unknown against an evidence trail, so nobody packages a release on an inference. Run it before a registry, licensing, sync, or payout conversation; the gaps it finds feed the rights passport and the licensing and royalty-routing prep. It reports; it does not clear rights or confirm ownership.
"find the ownership gaps in my catalog"->/suede-rights-auditAsk in plain words. The router reads the request and loads this lane; MCP agents find it with list_suede_skills.
claude code · sample session
$ /suede-rights-audit scan the catalog23 works scanned · chain of title traced2 works missing split confirmation2 GAPS FOUND · FIX LIST ATTACHED
Rights-gap audits across ownership, contributors, credits, splits, samples, licenses, provenance, and public context.
A shared evidence table with status, evidence, path or hash, risk, blockers, and next action for each item.
Provenance maps for sessions, masters, stems, artwork, lyrics, documents, metadata files, public URLs, hashes, conflicts, and do-not-share items.
Licensing-discussion readiness briefs that separate confirmed facts, open questions, restrictions, unsafe claims removed, and next steps.
Royalty-routing readiness summaries for contributor roles, split percentages, payment destinations, unresolved parties, and payout caveats.
Mechanical ship gates: blocked for high-risk items, unknown for unknown risk or status, and ready-for-review when no blockers remain.
When to use it
Before rights passporting, provenance mapping, licensing prep, registry readiness, royalty routing, payment-destination layout, or Suede creator intake.
Before a sync, brand, or partner licensing discussion where clearance gaps must stay visible.
When a project has thin source files, unclear samples, missing contributors, disputed splits, or public URLs that need review notes.
When the user needs confirmed facts, missing facts, blockers, creator questions, safe public wording, and the next lane or skill.
Not for: building the transfer package itself (use suede-rights-passport).
Not for: linting release folders for files and metadata (use suede-release-linter).
Not for: sync one-sheets (use suede-sync-packaging).
Best prompt
Use $suede-rights-audit to run a rights-gap audit and provenance map on this creator project, separate confirmed facts from unknowns, flag blockers, list questions for the creator, and give safe public wording plus the next lane or skill.
Related skills
Use Suede Rights Passport when the gaps are organized and the user wants the package. Use Suede Release Linter for folder, file, and metadata lint before or after the audit.
Safety boundary
This skill finds and organizes rights gaps as local evidence. It does not clear rights, confirm ownership, adjudicate chain of title, grant or imply a license, approve or schedule a payout, move money, write to any registry, or provide legal advice.
Install this skill
It ships inside the Suede Creator Skills pack, so one install brings the whole pack and this skill with it. Claude Code takes two commands the first time and one after that; Codex installs the same pack natively.