suede-rights-passport

Builds validated, offline rights-and-provenance transfer packages from creator project folders.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyYAML, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Creators handing a song, release, or project to a collaborator, registry, marketplace, or label often have scattered files and unconfirmed rights facts. This Skill turns messy creator materials into a structured, offline transfer package with hashed assets, a normalized manifest, and an explicit record of what is confirmed versus unknown. ## Core Features & Use Cases - Package Builder: Inventories a source folder, hashes every asset with SHA-256, and generates the seven required package files including RIGHTS_PASSPORT.md and suede-intake.json. - Schema Validation: A stdlib-only validator checks the 0.2.0 manifest against a bundled JSON Schema, verifying evidence states, share totals, identifier placement, and privacy posture. - Evidence-Scoped Rights Model: Separates works, recordings, releases, parties, rights claims, licenses, third-party material, and consents so unconfirmed facts stay flagged instead of being guessed. - Use Case: A musician preparing to hand a release to a label runs the builder on their project folder, answers the blocking questions, and delivers a validated package with a missing-info report instead of a folder of untracked files. ## Quick Start Ask the agent to use suede-rights-passport to turn your project folder into a validated rights transfer package, providing the source folder path and an output location.

Frequently Asked Questions about suede-rights-passport

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

FAQPage Schema
How do I create a rights transfer package for a music project?

Run the bundled create_transfer_package.py script with your source folder and an output path. It inventories files, computes SHA-256 hashes, and generates the seven required reports including suede-intake.json and missing-info-report.md.

How do I validate a suede-intake.json manifest?

Run validate_transfer_package.py with --strict-current against the package folder. It checks the manifest against the bundled Draft 2020-12 JSON Schema, verifies evidence on confirmed records, share totals, and privacy posture, exiting non-zero with specific errors on failure.

Does a passing validation mean the rights are cleared?

No. The validator confirms only structural completeness and referential integrity, not rights clearance. Unconfirmed ownership, splits, or samples still pass because they belong in risk_flags and missing_information.

Can I migrate an old 0.1.0 manifest to schema 0.2.0?

Yes, run migrate_intake_v1_to_v2.py on the 0.1.0 manifest. It writes a separate suede-intake.v0.2.json file, records the source digest in the chain of custody, and never upgrades evidence states or fills missing shares.

Does the package builder upload files or contact external services?

No. The skill is offline-first: it never uploads files, writes to registries, or calls live services unless the user explicitly requests it with an authenticated workflow. Secret-like files and symlinks are rejected by default.

When should I use a rights audit instead of the package builder?

Use a rights audit when ownership gaps, splits, or sample clearances still need investigation and evidence gathering. The package builder only organizes and packages facts; it never resolves rights questions.