Skip to content
Agentmart
Submit a tool

suede-sync-packaging

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…

Skill by JasonColapietro

IndexedMIT★ 125
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/jasoncolapietro-suede-sync-packaging

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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).

Use cases: spreadsheets, design, marketing, sales

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/suede-sync-packaging

What's inside

Skill 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).
License
MIT
Instructions
198 lines in SKILL.md · view on GitHub

Files (4)

  • CARD.md
  • SKILL.md
  • openai.yaml · agents/
  • sync-norms.md · references/

SKILL.md (first lines)

# Suede AI Sync Packaging Skills

## Compatibility

Uses supplied track facts, lyrics, rights evidence, and a confirmed master path. Media inspection needs an available local viewer or supplied timecodes; no distributor or outreach integration is required.

For a concrete input, expected handoff, and failure check, read
[the worked handoff](references/worked-handoff.md).

## 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 promise, clearance
   claim, or outreach claim.

## One-sheet contract

The one-sheet is supervisor-facing. It contains exactly these fields:

```text
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)
AI involvement: (none, or per element; only what the user supplied)
Rights status: (one line, confirmed facts only; one-stop yes / no / unknown)
Open clearance questions:
Contact path:
Public link:
```

The rights-status line states only confirmed facts and names the open

From JasonColapietro/suede-creator-skills, MIT.

More from JasonColapietro/suede-creator-skills

Signals

Stars
125
Forks
12
Open issues
4
Contributors
3
Last commit (this folder)
Oct 24, 2026 (3 days ago)
Last release
Aug 4, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from JasonColapietro

Cite this page

suede-sync-packaging skill. Agent Mart. https://agentmart.dev/skills/jasoncolapietro-suede-sync-packaging (last updated 2026-10-24)