/suede-rights-passport · Rights and provenance package

Rights evidence, packed like it matters.

Turn a messy creator folder into a validated local rights and provenance package. The schema keeps a musical work and its recording as different objects, because a splits table that conflates them is exactly the gap a registry or a licensee will find first. Assets get inventoried and hashed, credits, splits, license notes, and provenance get normalized into one manifest, and a missing-information report names what is still unknown. It runs on your own machine, offline, and clears nothing.

View skill folder Pair with release linter

"package the rights evidence for this project" /suede-rights-passport Ask in plain words. The router reads the request and loads this lane; MCP agents find it with list_suede_skills.
$ /suede-rights-passport package ./project works / recordings / releases separated · claims scoped identifiers evidence-labelled · privacy review required secrets excluded · hidden files skipped RIGHTS PACKAGE BUILT · REVIEW-READY
Rights package preview card for provenance, splits, license notes, and missing information.

What it produces

  • RIGHTS_PASSPORT.md - project summary, ownership status, contributor facts, and review flags.
  • suede-intake.json - versioned data for works, recordings, releases, parties, identifiers, rights claims, licenses, consent, provenance, privacy, paths, and hashes.
  • suede-intake.schema.json - JSON Schema 2020-12 contract for structural validation and downstream mapping.
  • provenance.md - origin notes, source materials, asset trail, and evidence gaps.
  • credits-and-splits.md - contributors, roles, split status, and unresolved confirmations.
  • license-notes.md - sample, sync, distribution, public URL, and clearance notes.
  • optimization-brief.md - concrete next steps for downstream review and media optimization.
  • missing-info-report.md - the blockers a creator or manager still needs to answer.

Best for

  • Artists preparing a catalog for release, licensing, or review.
  • Labels cleaning up credits, splits, samples, and provenance before licensing.
  • Managers packaging a release for registry-backed media review.
  • Developers building agent-readable media workflows without exposing private files.
  • Creator teams preparing for royalty routing, license review, and programmable IP.

Run it locally

Use the script when the source folder is available on disk. Pass public-safe metadata when known facts should prefill the package.

python3 skills/suede-rights-passport/scripts/create_transfer_package.py \
  /path/to/creator-project \
  --output /path/to/transfer-package \
  --metadata /path/to/creator-project/metadata.json \
  --project-title "Project Title" \
  --artist "Artist Name" \
  --copy-assets

Safety defaults skip hidden files, dependency folders, build outputs, caches, secret-like files, and unrecognized file types. The output folder cannot be the source folder or live inside it. Existing generated files require --force before replacement.

python3 skills/suede-rights-passport/scripts/validate_transfer_package.py \
  --strict-current /path/to/transfer-package

The validator checks structure, references, evidence-state rules, known-share bounds, hashes, and privacy posture. A pass does not prove ownership, clearance, registration, identifier validity, DDEX conformance, C2PA authenticity, or authority to transact.

All skill links

Skill manifestAgent-facing workflow, trigger description, safety rules, package standards, and completion checklist. OpenAI metadataDisplay name, short description, and default prompt for skill-list surfaces. Transfer package scriptInventories files, hashes assets, applies safety skips, writes the transfer package, and can copy selected assets. 0.1 to 0.2 migrationWrites a separate evidence-preserving 0.2 manifest, retains the source digest, and never upgrades claims or fills shares. ReferencesPackage standard, 0.2 field guide, DDEX/C2PA crosswalk boundaries, optimization checklist, creator questions, and review context. Templates and schemaJSON Schema 2020-12 plus Markdown and JSON templates for the generated package and reports.

Install prompts

After copying the skill folder into an agent skill root, use prompts like:

Use $suede-rights-passport to organize this creator project into a rights and provenance package.
Use the suede-rights-passport skill to organize this catalog into a local rights package.

Public safety

The skill should never claim a work is cleared unless the creator provides proof. It should not ask for seed phrases, private keys, full payment credentials, unreleased secrets, or private Suede implementation details. Generated packages are drafts until reviewed and redacted by the creator or operator.

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.

terminal · install the pack
Claude Code 
$ /plugin marketplace add JasonColapietro/suede-creator-skills
$ /plugin install suede-skills@suede
Codex 
$ codex plugin add suede-skills@suede-codex

Cursor, Copilot, and Windsurf install through the skills CLI. Every path is on the install page, and every folder is readable first on GitHub.

Proof is part of the release.

First install takes two commands. After the marketplace is added, install is one. Every skill is plain Markdown.

$ /plugin marketplace add JasonColapietro/suede-creator-skills → /plugin install suede-skills@suede All install paths