New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Suede Sync Packaging

by JasonColapietro in JasonColapietro/suede-creator-skills

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…

MITAuto-check passedDevelopment

Install Suede Sync Packaging

skills CLI
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-sync-packaging -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install JasonColapietro/suede-creator-skills suede-sync-packaging --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/suede-sync-packaging .claude/skills/suede-sync-packaging && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
suede-sync-packaging
GitHub stars
127
Token cost
~2.6k tokens
SKILL.md length
1,265 words
Files
3
Skills in repo
78
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 6 steps: Never claim or imply clearance. A rights… → Never resolve a rights question… → Asset checklist before pitch copy. Do… → …
  • A track is headed for film
  • SKILL.md covers Gate policy: advisory, not…, Input contract, Hard gates and Package workflow, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Suede Sync Packaging is an agent skill from JasonColapietro/suede-creator-skills. 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 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…

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `CARD.md` and `agents/openai.yaml`).

It sits in Development, covering Linting and formatting. The repository describes itself as: 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… The licence is MIT.

When your agent uses it

  • A track is headed for film
  • Creator campaigns
  • A music supervisor
  • Brand asks what a song is and whether it can be used

Example prompts

  • “/suede-sync-packaging”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Never claim or imply clearance. A rights fact appears as confirmed only
  2. Never resolve a rights question yourself. If ownership, splits, samples,
  3. Asset checklist before pitch copy. Do not write one-sheet or pitch-email
  4. Unresolved sample = pause and put it to the user. Uncleared samples are
  5. Lyric flags are mandatory. Screen the lyrics and flag profanity, brand
  6. Sync fit is an assessment, not a compliment. "No clear scene fit for the

What it can do on your machine

Read from SKILL.md and the folder at commit a9bf55e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Suede Sync Packaging loads about 2.6k tokens when it runs. Until then it costs about 245 tokens; SKILL.md has 1,265 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~245
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from JasonColapietro/suede-creator-skills at commit a9bf55e, republished under its MIT licence (© JasonColapietro). 1,265 words, ~2,551 tokens.

Download SKILL.mdSave it as .claude/skills/suede-sync-packaging/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
suede-sync-packaging
description
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 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: finding and organizing the rights gaps behind an open clearance question (use suede-rights-audit); 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: advisory, not blocking

Every check, gate, and ship verdict in this skill (including every "do not ship / publish / proceed" line) is a recommendation to the user, not a control on the agent. Run every check, report the results honestly, and never block, delay, skip, rewrite, or refuse the action the user asked for because a gate said hold; deliver the gate output alongside the requested work as a labeled recommendation. A failed gate changes what you report, never what you do. Single exception: extreme risk (data loss, credential exposure, legal or rights violations, payment mistakes, irreversible public damage): pause, name the risk exactly, give the options, and let the user 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.

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)

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.

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-audit.
  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.
Show full SKILL.md (513 more words)Show less

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

Failure modes

  • Missing master or instrumental: flag in the asset checklist as a blocker. Do not complete the sync angle without at minimum a confirmed master file path.
  • Unresolved sample: sample status is "OPEN, do not pitch until cleared." No pitch copy (hard gate 4).
  • Unknown splits or ownership: flag in clearance questions. The package can be built but must carry the caveat: "Rights holder confirmation required before placement."
  • No contact path: the package is complete but note: "No contact path identified: supervisor cannot follow up."
  • Scope creep: if the request becomes a promo funnel, placement promise, or clearance claim, stop and restate the boundary: "This skill prepares review-ready materials. It does not clear rights, confirm placement, or generate outreach."

Red flags: stop

If any of these appear in your reasoning, stop and re-read the hard gates:

  • "The artist says it's cleared." A claim is not clearance. Status stays UNCONFIRMED with a clearance question attached.
  • "We'll sort splits later." Splits sort before pitching, or the gap ships as an open question. Never silently.
  • "The supervisor is waiting: skip the instrumental check." The checklist is the package. Skipping it ships a track no one can license.
  • "It's a small indie film, nobody checks samples." Sample status is binary: cleared with proof, or OPEN.
  • "Soften the sample note so the one-sheet reads better." Hidden risk reads worse in a licensing call.

Public copy gate

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: suede-deslop owns that pattern list in full; name the actor and keep the concrete track artifact.

Sync copy has its own cliché attractor that a general anti-slop pass does not catch, because the sentences are clean: they just say nothing. These are banned in one-sheet and pitch copy:

cinematic · anthemic · haunting · soaring · driving · epic · ethereal · raw and honest · infectious · cuts through the mix · builds to an emotional payoff · perfect for the moment when the hero…

Replace a banned word with a concrete musical fact drawn from the facts the user supplied: tempo, key, instrumentation, an arrangement turn ("drums drop out at 1:48, vocal and room noise only"), or a quoted lyric line. Never a synonym, and never a fact you inferred: if the input contract did not supply it, leave it out rather than invent it. The substitution is descriptive copy only: it may never introduce rights, ownership, or clearance language, which stays governed by hard gates 1-2 and 5. A supervisor skims twelve one-sheets an hour; the concrete one is the one they can picture against a scene.

Output

text
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:

Routing

  • Rights gaps or missing provenance → suede-rights-audit to find and organize the gaps, then suede-rights-passport to package.
  • This grows into a release campaign → suede-campaign-in-a-box.
  • Release folder or metadata gaps → suede-release-linter.
  • Standalone public copy beyond the one-sheet → suede-copy or johnny-suede-write.

Family order: suede-release-linter → suede-rights-audit → suede-rights-passport → suede-sync-packaging; this skill is step 4.

© JasonColapietro, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in skills/suede-sync-packaging of JasonColapietro/suede-creator-skills.

  • SKILL.md
  • CARD.md
  • agents/openai.yaml

Open the folder on GitHubat commit a9bf55e

Compare with similar skills

Suede Sync Packaging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Suede Sync Packaging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Suede Sync Packaging this skillJasonColapietro/suede-creator-skills127—~2.6kAutomated safety check: PassMIT
Minimizing Ty Ecosystem Changesastral-sh/ruff50k—~4.6kAutomated safety check: PassMIT
Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop5.3k—~2.2kAutomated safety check: PassMIT
Babysit PR To Pass CIsgl-project/sglang37k2 repos~3kAutomated safety check: PassApache-2.0
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT
Summarise Ecosystem Resultsastral-sh/ruff50k—~2.2kAutomated safety check: PassMIT

Similar skills

  • Minimizing Ty Ecosystem Changes

    astral-sh/ruff

    Official

    A skill your agent uses when a user says "minimize this ty ecosystem change", "reproduce this ecosystem result", "investigate a primer difference", "investigate a mypyprimer difference"…

    50k GitHub stars~4.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Install Anti-Slop Oxlint Rules

    dmmulroy/anti-slop

    Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.

    5.3k GitHub stars~2.2k tokensUpdated 29 days ago
    DevelopmentAuto-check passed

  • Babysit PR To Pass CI

    sgl-project/sglang

    Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.

    37k GitHub starsUsed in 2 repos~3k tokens
    DevelopmentAuto-check passed

  • Rust Best Practices

    farm-fe/farm

    Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.

    5.6k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Summarise Ecosystem Results

    astral-sh/ruff

    Official

    A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…

    50k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Go Pedantry

    chromedp/chromedp

    This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…

    13k GitHub stars~3.7k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

More from JasonColapietro/suede-creator-skills

All 78 skills in this repo

  • Suede Release Linter

    JasonColapietro/suede-creator-skills

    Lints a local music or media release folder and scores its readiness, flagging missing files, weak metadata, artwork and stem problems, split gaps and rights blockers.

    127 GitHub stars~2.3k tokensUpdated today
    Auto-check: notes

  • Creator Rights Passport

    JasonColapietro/suede-creator-skills

    Turns messy creator materials into an offline rights-and-provenance transfer package: hashed asset inventory, intake manifest, credits, license notes and a missing-information report.

    127 GitHub stars~3.7k tokensUpdated today
    Auto-check: notes

  • Suede Clip to Guide

    JasonColapietro/suede-creator-skills

    Turns a video clip, interview moment or transcript into a package that bridges viewers to a long-form guide, with rights, claim and approval gates along the way.

    127 GitHub stars~4.1k tokensUpdated today
    Auto-check passed

  • Suede MCP Release QA

    JasonColapietro/suede-creator-skills

    Checks a Suede AI MCP server release against a live process: the full JSON-RPC lifecycle, schemas, annotations, malformed input, catalog agreement and install docs.

    127 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Android App Factory

    JasonColapietro/suede-creator-skills

    Takes a native Android app from product idea to Google Play release, covering Compose architecture, policy checks, privacy, billing, testing, signing and rollout.

    127 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Suede Ad Creative

    JasonColapietro/suede-creator-skills

    Suede-owned paid-media creative system for hooks, headlines, primary text, static and motion concepts, platform specs, review pages, and test-ready variant batches.

    127 GitHub stars~5k tokensUpdated today
    Auto-check passed

Categories

Questions about Suede Sync Packaging

What does Suede Sync Packaging do?

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…. Suede Sync Packaging is an agent skill from JasonColapietro/suede-creator-skills. 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 in their own labeled pile.

When should I use Suede Sync Packaging?

Suede Sync Packaging fits situations like: A track is headed for film; creator campaigns; A music supervisor; brand asks what a song is and whether it can be used.

How do I install Suede Sync Packaging in Claude Code?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-sync-packaging -a claude-code`. Or copy the skill folder (skills/suede-sync-packaging in JasonColapietro/suede-creator-skills) into .claude/skills/suede-sync-packaging in your project. Claude Code loads it when a task matches its description.

How do I install Suede Sync Packaging in Codex?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-sync-packaging -a codex`. Or copy the skill folder (skills/suede-sync-packaging in JasonColapietro/suede-creator-skills) into .agents/skills/suede-sync-packaging in your project. Codex loads it when a task matches its description.

Can I use Suede Sync Packaging in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JasonColapietro/suede-creator-skills --skill suede-sync-packaging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/suede-sync-packaging, .gemini/skills/suede-sync-packaging, .github/skills/suede-sync-packaging and .opencode/skills/suede-sync-packaging in your project.

What does Suede Sync Packaging need to run?

SKILL.md names no scripts, command-line tools or credentials: Suede Sync Packaging is instructions for the agent only.

Does Suede Sync Packaging access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Suede Sync Packaging safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Suede Sync Packaging use?

Suede Sync Packaging is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Suede Sync Packaging use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Suede Sync Packaging?

Skills that share tags, products or a category with Suede Sync Packaging: Minimizing Ty Ecosystem Changes (astral-sh/ruff, 50k stars), Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.3k stars), Babysit PR To Pass CI (sgl-project/sglang, 37k stars) and Rust Best Practices (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Suede Sync Packaging?

JasonColapietro (a GitHub user) maintains it in JasonColapietro/suede-creator-skills, which has 127 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 9, 2026.

Source: JasonColapietro/suede-creator-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.