jasoncolapietro/suede-sync-packaging
Prep songs for sync pitches: scene angles, one-sheets, clean and instrumental assets, lyric flags, mood tags, rights questions, and links.
npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill suede-sync-packaging
Every claim-verification step, check, quality gate, and ship verdict in this
skill is a recommendation to the user, not a control on the agent. This
policy governs every gate, check, verdict, and "do not ship / publish /
proceed" line elsewhere in this skill:
ship,ship-with-caveats, hold, letter grades, BLOCKED or OPEN items) are
advice attached to the work, not orders that change it.
because a check failed or a gate said hold. Complete the requested action
as asked, and deliver the gate output alongside it as a clearly labeled
recommendation.
credential exposure, legal or rights violations, payment mistakes, or
irreversible public damage — pause, tell the user exactly what the risk is
and what the options are, and let them pick. Their choice is final.
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.
Provide at minimum:
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.
Do not rationalize past these:
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.
or publishing are unclear, mark the item UNKNOWN. Do not infer, average, or
assume. Route the gap to suede-rights-audit.
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.
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.
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.
existing assets, and target sync world.
brand fit; game or sports fit; creator campaign fit.
if available; lyrics; credits; splits; sample status; contact path;
public/private links. Each item: exists / missing / unknown.
1-2).
claim, or outreach claim.
The one-sheet is supervisor-facing. It contains exactly these fields:
Track / artist / featuring:
Length / tempo / key (if known):
Genre and mood tags:
Sounds like: (era and energy references; never copy a protected identity)
Scene fits: (top 3, one line each)
Lyric themes:
Lyric flags:
Versions available: (master / instrumental / clean / stems)
Rights status: (one line, confirmed facts only)
Open clearance questions:
Contact path:
Public link:
The rights-status line states only confirmed facts and names the open
questions. Never compress "unknown" into silence.
Do not complete the sync angle without at minimum a confirmed master file
path.
No pitch copy (hard gate 4).
be built but must carry the caveat: "Rights holder confirmation required
before placement."
identified — supervisor cannot follow up."
clearance claim, stop and restate the boundary: "This skill prepares
review-ready materials. It does not clear rights, confirm placement, or
generate outreach."
If any of these appear in your reasoning, stop and re-read the hard gates:
UNCONFIRMED with a clearance question attached.
an open question. Never silently.
the package. Skipping it ships a track no one can license.
cleared with proof, or OPEN.
worse in a licensing call.
Before outputting one-sheet copy, pitch email, captions, DMs, press angles,
site copy, bios, CTAs, or review language, run the Suede anti-slop line edit.
Name the actor, preserve the concrete track/release artifact, cut
throat-clearing, negative listing, fake intensity, lazy extremes, passive
actor-hiding, pull-quote slogans, generic AI phrasing, unsupported claims, and
em dashes.
Sync positioning:
Best scenes:
Mood tags:
Lyric flags:
Asset checklist: (each item exists / missing / unknown)
Confirmed rights facts:
Clearance questions:
One-sheet: (per the one-sheet contract above)
Pitch email: (only if hard gates 3-4 pass)
Next review step:
organize the gaps, then suede-rights-passport to package.
johnny-suede-write.
Take jasoncolapietro/suede-sync-packaging from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.