suede-rights-audit

Organize creator-rights gaps into a confirmed-versus-unknown evidence trail before packaging.

123|10|Updated May 24, 2026
One-click install
npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-rights-audit-jasoncolapietro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: suede-rights-audit
Source: https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-rights-audit
Command: npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-rights-audit-jasoncolapietro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Before a song, release, or creative project can be registered, licensed, or paid out, someone must know who owns what, which splits are confirmed, and which samples are cleared. This Skill finds and organizes those rights gaps into a structured evidence table so licensing, registry, and royalty-routing work builds on documented facts instead of guesses. ## Core Features & Use Cases - Four audit lanes: rights-gap audit (ownership, contributors, splits, samples, licenses, provenance, public context), provenance mapping, licensing-discussion readiness, and royalty-routing readiness, run in A→B→C→D order. - Shared evidence and severity gate: every item is marked confirmed, inferred, unconfirmed, disputed, or unknown with a risk rating, and the ship gate maps mechanically to ready-for-review, blocked, or unknown. - Strict evidence boundaries: the audit never clears rights, confirms ownership, moves money, or writes to any registry; it organizes evidence and flags gaps for human and legal decision-makers. - Use Case: Before pitching a track for sync licensing, run the audit to produce a licensing brief listing confirmed rights facts, open questions, restrictions, and unsafe claims removed. ## Quick Start Use suede-rights-audit to find and organize the rights gaps in this release folder, covering ownership, contributors, splits, samples, licenses, and provenance, and report each item as confirmed or unknown.

Frequently Asked Questions about suede-rights-audit

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

FAQPage Schema
How do I audit music rights before licensing a song?

Run the rights-gap audit lane to sweep ownership, contributors, splits, samples, licenses, provenance, and public context. Each item is recorded in an evidence table with a confirmed, unconfirmed, or unknown status, plus blockers and questions for the rights holder.

How to check royalty split readiness before a payout?

Use Lane D, royalty-routing readiness, which verifies that splits total cleanly, all contributors are confirmed, and payment destinations are documented. It reports readiness only and never approves, schedules, or moves any money.

Does this skill clear sample rights or confirm ownership?

No. The audit only organizes evidence and marks items confirmed or unknown against an evidence trail. Clearing rights, confirming ownership, and legal decisions stay with humans and legal counsel; status promotion to confirmed requires user-supplied documentation.

What is the difference between suede-rights-audit and suede-rights-passport?

The audit finds and organizes rights gaps and produces the evidence trail. suede-rights-passport builds the actual transfer package afterward; the audit hands off to it once gaps are organized and the user wants the package.

Can the rights audit run as multiple agents?

Yes, it can run as a multi-agent team with one agent per lane, capped at four agents. The skill asks the user first, requires naming the model on every dispatch, and states the cost before spawning agents.