Skip to content

JasonColapietro/suede-creator-skills / skills/suede-sync-packaging

suede-sync-packaging

Verified

Prepare a song for sync review: scene fit, supervisor one-sheet, asset checklist, lyric flags, mood tags, AI disclosure, and open clearance questions. Use when asked to "make a sync one-sheet" or package a track for film, TV, ads, games, trailers, or creator campaigns. Drafts pitch materials with open clearance questions labeled. NOT FOR: rights investigations or transfer packages (use suede-rights-passport), folder linting (use suede-release-linter), or rollouts (use suede-campaign-in-a-box).

FileKindSize
CARD.mdmarkdown4.6 KB
SKILL.mdskill md10.1 KB
agents/openai.yamlconfig417 B
references/sync-norms.mdmarkdown3.2 KB
references/worked-handoff.mdmarkdown1.7 KB

references/sync-norms.md

View on GitHub
# Sync Deliverables and Clearance Norms

Checked on **2026-10-23**. These are working norms for pitching a track to music
supervisors, trailer houses, ad agencies, game studios, and brand teams. Every
brief overrides them; ask for the spec when one exists.

## What a supervisor needs to say yes fast

- **One-stop or a clear path to both sides.** Every sync needs a master use
  license (the recording) and a synchronization license (the composition).
  "One-stop" means one party can grant both. When publishing and master sit with
  different people, the one-sheet names both contacts. Unknown publishing is an
  open clearance question, never silence.
- **Versions.** Full mix, instrumental, and a clean edit when lyrics carry
  profanity or brand names. Stems or a short edit (30 or 60 seconds) win
  trailer and ad work. Missing versions go on the checklist as missing.
- **Files.** Lossless WAV for delivery; picture work commonly runs at 48 kHz,
  24-bit, so offer that or say what you have. A streaming link or high-bitrate
  MP3 is fine for the first listen.
- **Embedded metadata.** Title, artist, writers with splits and PRO
  affiliations, publisher, master owner, ISRC, contact email, and one-stop
  status in the file tags and the filename. Supervisors pull files into a
  library and lose the email.
- **Lyrics.** A lyric sheet with flags. A lyric surprise in review kills the
  placement.

## AI involvement

AI involvement is now a standard clearance question:

- Productions and their errors-and-omissions insurers ask the licensor to
  warrant the track does not infringe. That warranty is hard to give for
  material from an AI tool whose terms or training data the artist cannot
  speak to.
- The US Copyright Office's position (January 2025 report) is that purely
  AI-generated material is not copyrightable and prompts alone do not make
  someone an author. A track whose melody, lyrics, or vocal came straight from a
  generator may have thin or no copyright in those elements, which weakens what
  the licensor can actually license.
- A synthetic or cloned voice needs written consent from the person whose voice
  it is, scoped to this use.
- DSP AI-credit fields (for example Spotify's, supplied through distributors
  since late 2025) mean a supervisor may already see the disclosure. Match it.

So the one-sheet states AI involvement per element (vocals, instrumentation,
composition, lyrics, post-production) or "none," using only what the user
supplied, and an unknown answer becomes an open clearance question.

Sources:

- U.S. Copyright Office, *Copyright and Artificial Intelligence, Part 2:
  Copyrightability* (January 2025):
  <https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf>
- Spotify, AI protections and AI credits in music credits (2025-09-25):
  <https://newsroom.spotify.com/2025-09-25/spotify-strengthens-ai-protections/>

## What not to put in the package

- Fee quotes or "we can do it for X." Price comes from the rights holders once
  the use (media, term, territory, duration) is known.
- Placement history that the user did not supply.
- Any statement that the track is cleared, pre-cleared, or "easy to clear"
  without signed paperwork behind it.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall