Skip to content
Marketing
Skill

/suede-sync-packaging

Suede Labs skill that prepares a song for sync pitching: scene and emotional angles, a supervisor-facing one-sheet, an exists/missing/unknown asset checklist covering master, instrumental, clean, and stems, screened lyric flags, mood tags, and the open clearance questions kept

BOOST
From plugin
suede-skills
12576 skills1 MCP
Install
$ npx -y skills add JasonColapietro/suede-creator-skills --skill suede-sync-packaging --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/suede-sync-packaging

Context preview

The summary Claude sees to decide when to auto-load this skill.

Suede Labs skill that prepares a song for sync pitching: scene and emotional angles, a supervisor-facing one-sheet, an exists/missing/unknown asset checklist covering master, instrumental, clean, and stems, screened lyric flags, mood tags, and the open clearance questions kept

SKILL.md

suede-sync-packaging.SKILL.md
name: suede-sync-packaging
description: "Suede AI skill that prepares a song for sync pitching: scene and emotional angles, a supervisor-facing one-sheet, an exists/missing/unknown asset checklist covering master, instrumental, clean, and stems, screened lyric flags, mood tags, AI-involvement disclosure, and the open clearance questions kept in their own labeled pile. Use when a track is headed for film, TV, ads, games, trailers, or creator campaigns; when a music supervisor, sync agent, or brand asks what a song is and whether it can be used; or when someone asks for a one-sheet, pitch email, or sync package for a release. Prepares review-ready materials only: never claims clearance, promises placement, or sends outreach. NOT FOR: investigating the rights gaps behind an open clearance question or building the rights transfer package (use suede-rights-passport); linting the release folder itself (use suede-release-linter); a full rollout campaign (use suede-campaign-in-a-box)."

Suede Sync Package

Gate policy

Every check and verdict here is advice to the user, not a control on the agent. Run the checks, report results honestly, and complete what the user asked. A failed gate changes the report, never the work. The one exception: a finding that risks data loss, credential exposure, a legal or rights violation, a payment mistake, or irreversible public damage. Pause, name the risk, give the options, and let the user choose.

**Core principle:** a sync package makes a track easy to evaluate; it never asserts the track is cleared. Confirmed facts and open clearance questions travel in separate, labeled piles, every time.

Input contract

Provide at minimum:

  • **Track**: title, artist, featuring credits if any
  • **Target world**: film / TV / ads / games / trailers / creator campaigns / brand brief (or "general sync")
  • **Available assets**: which of master, instrumental, clean, stems, lyrics, credits, splits currently exist
  • **Rights status**: what is confirmed vs. unknown (sample clearance, ownership splits, publishing assignment, one-stop or not)
  • **AI involvement**: none, or which elements used generative AI (vocals, instrumentation, composition, lyrics, post-production)

Optional but useful: reference sync placements the artist admires, mood or scene keywords, existing pitches or supervisor feedback.

If no rights status is provided, treat every clearance question as open. If AI involvement is not stated, it is an open clearance question too.

Read `references/sync-norms.md` for deliverable specs, one-stop, and why AI involvement now sits in the clearance pile.

Hard gates

Do not rationalize past these:

1. **Never claim or imply clearance.** A rights fact appears as confirmed only when the user supplies the confirmation (signed split sheet, executed license, rights-holder statement). Anything else stays OPEN or UNKNOWN. You organize the questions; you never answer them. 2. **Never resolve a rights question yourself.** If ownership, splits, samples, or publishing are unclear, mark the item UNKNOWN. Do not infer, average, or assume. Route the gap to suede-rights-passport (audit mode). 3. **Asset checklist before pitch copy.** Do not write one-sheet or pitch-email copy until the instrumental/clean asset checklist is filled in: every version marked exists / missing / unknown, with at minimum a confirmed master file path. Missing instrumental or clean versions are flagged in the one-sheet, not glossed. 4. **Unresolved sample = pause and put it to the user.** Uncleared samples are a legal-risk finding: mark sample status "OPEN: recommend not pitching until cleared," tell the user exactly what is unresolved, and let them decide whether pitch copy is still drafted. If they proceed, the OPEN flag stays embedded in the one-sheet and pitch materials. 5. **Lyric flags are mandatory.** Screen the lyrics and flag profanity, brand and product names, artist name-drops, violence, drugs and alcohol, sexual content, religious and political content, and date-stamped references. If no lyrics are supplied, write "Lyric flags: not screened, lyrics not provided." A lyric surprise in review kills the placement. 6. **Sync fit is an assessment, not a compliment.** "No clear scene fit for the stated target world" is a valid, useful finding: say it plainly and say why. Never pad the scene-fit list to reach three; two real fits beat three, and one real fit beats two. Never call a track a placement candidate when the asset checklist or the clearance questions say it cannot be pitched yet. The supervisor will find the weak angle faster than the artist will.

Package workflow

1. Identify the track, artist, genre, mood, tempo, lyric themes, versions, existing assets, and target sync world. 2. Build the sync angle: scene fit; emotional use; trailer or montage fit; brand fit; game or sports fit; creator campaign fit: assessed, not flattered (hard gate 6). 3. Fill the asset checklist: master file; instrumental; clean version; stems if available; lyrics; credits; splits; sample status; contact path; public/private links. Each item: exists / missing / unknown. 4. Screen lyrics and write the lyric flags (hard gate 5). 5. Separate confirmed rights facts from open clearance questions (hard gates 1-2). 6. Write the one-sheet and pitch email only if gates 3-4 pass. 7. Second pass: re-read the draft against the one-sheet contract, field by field, before it ships. Confirm every field is present; confirm the rights-status line contains only facts the user supplied; confirm every OPEN or UNKNOWN item from the checklist survived into the copy verbatim rather than softened; confirm no banned adjective from the copy gate came back; and confirm the scene-fit list is as long as the real fits, not padded to three. Fix what fails, then re-read once more. 8. Stop at a clean review package. No promo CTA, placement

Read more
Ships withsuede-skills

Open-source AI skills for SEO, AI search visibility, conversion copy, marketing strategy, and business operations. Reusable workflows for Claude Code and Codex, plus code review, app delivery, and creator tools.

Get the whole plugin

Other skills on suede-skills.