JasonColapietro/suede-creator-skills / skills/suede-rights-passport
suede-rights-passport
FlaggedAudit rights gaps in ownership, contributors, splits, samples, licenses, provenance, and AI involvement, or assemble a hashed offline handoff package with a validated manifest. Use when asked to "prepare a rights handoff" or assess release, licensing, or royalty-routing evidence. Keeps confirmed facts separate from open questions. NOT FOR: release file linting (use suede-release-linter), sync pitching (use suede-sync-packaging), or rollout campaigns (use suede-campaign-in-a-box).
references/creator-questions.md
View on GitHub# Creator Intake Questions
Ask only questions that resolve missing or risky information. Prefer grouped questions when many fields are missing.
## Identity
- What is the official project or song title?
- What artist/creator name should appear publicly?
- Who is submitting this package, and are they authorized to do so?
- Is there a public payment destination (or, for on-chain workflows, a public wallet address) to associate with the creator?
## Files
- Which file is the final master?
- Are stems available?
- Are there separate lyrics, cover art, project files, or split sheets?
- Are any files drafts that should not be used for registry, licensing, or public cataloging?
## Contributors And Splits
- Who contributed to the work?
- What role did each contributor have?
- Are publishing/master splits confirmed in writing?
- Are any contributors unresponsive, disputed, or missing?
- Should any manager, label, publisher, or collective be listed?
## Rights And Licenses
- Does the work contain samples, loops, interpolations, covers, or third-party beats?
- Are those materials cleared?
- Are there beat leases, exclusivity restrictions, sync restrictions, or platform restrictions?
- Has the work already been distributed, registered, minted, licensed, or sold?
## AI Involvement
- Was generative AI used for vocals, instrumentation, composition, lyrics, artwork, or post-production? Which tool, and under which plan or terms?
- For an AI or cloned voice: whose voice is it, and is there written consent covering this use?
- What did a human write, perform, or arrange, and what evidence shows it (session files, drafts, lyric sheets)?
## Optimization
- What should be improved first: mastering, stems, lyrics, artwork, metadata, registry, royalty routing, licensing, or agent commerce?
- Is this intended for private optimization, public cataloging, licensing, agent commerce, or a future release?
- Are there deadlines, launch dates, takedown concerns, or confidentiality limits?
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |