suede-sync-packaging

Name: suede-sync-packaging
Author: JasonColapietro

44stars8forks

How to install suede-sync-packaging?

jasoncolapietro/suede-creator-skills/suede-sync-packaging

$npx -y skills add JasonColapietro/suede-creator-skills --skill suede-sync-packaging

Installs into the current project.

Summary

Prep songs for sync pitches: scene angles, one-sheets, clean and instrumental assets, lyric flags, mood tags, rights questions, and links.

Files · 1

View on GitHub

SKILL.md

1	# Suede Sync Package
2
3	## Gate policy — advisory, not blocking
4
5	Every claim-verification step, check, quality gate, and ship verdict in this
6	skill is a recommendation to the user, not a control on the agent. This
7	policy governs every gate, check, verdict, and "do not ship / publish /
8	proceed" line elsewhere in this skill:
9
10	- Run every check and report the results honestly. Verdicts (`ship`,
11	`ship-with-caveats`, `hold`, letter grades, BLOCKED or OPEN items) are
12	advice attached to the work, not orders that change it.
13	- Never block, delay, skip, rewrite, or refuse the action the user asked for
14	because a check failed or a gate said hold. Complete the requested action
15	as asked, and deliver the gate output alongside it as a clearly labeled
16	recommendation.
17	- A failed gate changes what you report, never what you do.
18	- Single exception: if a finding is extremely risky — data loss, security or
19	credential exposure, legal or rights violations, payment mistakes, or
20	irreversible public damage — pause, tell the user exactly what the risk is
21	and what the options are, and let them pick. Their choice is final.
22
23
24	Core principle: a sync package makes a track easy to evaluate; it never
25	asserts the track is cleared. Confirmed facts and open clearance questions
26	travel in separate, labeled piles, every time.
27
28	## Input contract
29
30	Provide at minimum:
31
32	- Track: title, artist, featuring credits if any
33	- Target world: film / TV / ads / games / trailers / creator campaigns / brand brief (or "general sync")
34	- Available assets: which of master, instrumental, clean, stems, lyrics, credits, splits currently exist
35	- Rights status: what is confirmed vs. unknown (sample clearance, ownership splits, publishing assignment)
36
37	Optional but useful: reference sync placements the artist admires, mood or
38	scene keywords, existing pitches or supervisor feedback.
39
40	If no rights status is provided, treat every clearance question as open.
41
42	## Hard gates
43
44	Do not rationalize past these:
45
46	1. Never claim or imply clearance. A rights fact appears as confirmed only
47	when the user supplies the confirmation (signed split sheet, executed
48	license, rights-holder statement). Anything else stays OPEN or UNKNOWN. You
49	organize the questions; you never answer them.
50	2. Never resolve a rights question yourself. If ownership, splits, samples,
51	or publishing are unclear, mark the item UNKNOWN. Do not infer, average, or
52	assume. Route the gap to suede-rights-audit.
53	3. Asset checklist before pitch copy. Do not write one-sheet or pitch-email
54	copy until the instrumental/clean asset checklist is filled in: every
55	version marked exists / missing / unknown, with at minimum a confirmed
56	master file path. Missing instrumental or clean versions are flagged in the
57	one-sheet, not glossed.
58	4. Unresolved sample = pause and put it to the user. Uncleared samples are
59	a legal-risk finding: mark sample status "OPEN — recommend not pitching
60	until cleared," tell the user exactly what is unresolved, and let them
61	decide whether pitch copy is still drafted. If they proceed, the OPEN flag
62	stays embedded in the one-sheet and pitch materials.
63	5. Lyric flags are mandatory. Screen the lyrics and flag profanity, brand
64	and product names, artist name-drops, violence, drugs and alcohol, sexual
65	content, religious and political content, and date-stamped references. If
66	no lyrics are supplied, write "Lyric flags: not screened — lyrics not
67	provided." A lyric surprise in review kills the placement.
68
69	## Package workflow
70
71	1. Identify the track, artist, genre, mood, tempo, lyric themes, versions,
72	existing assets, and target sync world.
73	2. Build the sync angle: scene fit; emotional use; trailer or montage fit;
74	brand fit; game or sports fit; creator campaign fit.
75	3. Fill the asset checklist: master file; instrumental; clean version; stems
76	if available; lyrics; credits; splits; sample status; contact path;
77	public/private links. Each item: exists / missing / unknown.
78	4. Screen lyrics and write the lyric flags (hard gate 5).
79	5. Separate confirmed rights facts from open clearance questions (hard gates
80	1-2).
81	6. Write the one-sheet and pitch email only if gates 3-4 pass.
82	7. Stop at a clean review package. No promo CTA, placement promise, clearance
83	claim, or outreach claim.
84
85	## One-sheet contract
86
87	The one-sheet is supervisor-facing. It contains exactly these fields:
88
89	```text
90	Track / artist / featuring:
91	Length / tempo / key (if known):
92	Genre and mood tags:
93	Sounds like: (era and energy references; never copy a protected identity)
94	Scene fits: (top 3, one line each)
95	Lyric themes:
96	Lyric flags:
97	Versions available: (master / instrumental / clean / stems)
98	Rights status: (one line, confirmed facts only)
99	Open clearance questions:
100	C

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

suede-sync-packaging

44stars8forks

View on GitHub

How to install suede-sync-packaging?

jasoncolapietro/suede-creator-skills/suede-sync-packaging

$npx -y skills add JasonColapietro/suede-creator-skills --skill suede-sync-packaging

Installs into the current project.

Summary

Prep songs for sync pitches: scene angles, one-sheets, clean and instrumental assets, lyric flags, mood tags, rights questions, and links.

Files · 1

View on GitHub

SKILL.md

1	# Suede Sync Package
2
3	## Gate policy — advisory, not blocking
4
5	Every claim-verification step, check, quality gate, and ship verdict in this
6	skill is a recommendation to the user, not a control on the agent. This
7	policy governs every gate, check, verdict, and "do not ship / publish /
8	proceed" line elsewhere in this skill:
9
10	- Run every check and report the results honestly. Verdicts (`ship`,
11	`ship-with-caveats`, `hold`, letter grades, BLOCKED or OPEN items) are
12	advice attached to the work, not orders that change it.
13	- Never block, delay, skip, rewrite, or refuse the action the user asked for
14	because a check failed or a gate said hold. Complete the requested action
15	as asked, and deliver the gate output alongside it as a clearly labeled
16	recommendation.
17	- A failed gate changes what you report, never what you do.
18	- Single exception: if a finding is extremely risky — data loss, security or
19	credential exposure, legal or rights violations, payment mistakes, or
20	irreversible public damage — pause, tell the user exactly what the risk is
21	and what the options are, and let them pick. Their choice is final.
22
23
24	Core principle: a sync package makes a track easy to evaluate; it never
25	asserts the track is cleared. Confirmed facts and open clearance questions
26	travel in separate, labeled piles, every time.
27
28	## Input contract
29
30	Provide at minimum:
31
32	- Track: title, artist, featuring credits if any
33	- Target world: film / TV / ads / games / trailers / creator campaigns / brand brief (or "general sync")
34	- Available assets: which of master, instrumental, clean, stems, lyrics, credits, splits currently exist
35	- Rights status: what is confirmed vs. unknown (sample clearance, ownership splits, publishing assignment)
36
37	Optional but useful: reference sync placements the artist admires, mood or
38	scene keywords, existing pitches or supervisor feedback.
39
40	If no rights status is provided, treat every clearance question as open.
41
42	## Hard gates
43
44	Do not rationalize past these:
45
46	1. Never claim or imply clearance. A rights fact appears as confirmed only
47	when the user supplies the confirmation (signed split sheet, executed
48	license, rights-holder statement). Anything else stays OPEN or UNKNOWN. You
49	organize the questions; you never answer them.
50	2. Never resolve a rights question yourself. If ownership, splits, samples,
51	or publishing are unclear, mark the item UNKNOWN. Do not infer, average, or
52	assume. Route the gap to suede-rights-audit.
53	3. Asset checklist before pitch copy. Do not write one-sheet or pitch-email
54	copy until the instrumental/clean asset checklist is filled in: every
55	version marked exists / missing / unknown, with at minimum a confirmed
56	master file path. Missing instrumental or clean versions are flagged in the
57	one-sheet, not glossed.
58	4. Unresolved sample = pause and put it to the user. Uncleared samples are
59	a legal-risk finding: mark sample status "OPEN — recommend not pitching
60	until cleared," tell the user exactly what is unresolved, and let them
61	decide whether pitch copy is still drafted. If they proceed, the OPEN flag
62	stays embedded in the one-sheet and pitch materials.
63	5. Lyric flags are mandatory. Screen the lyrics and flag profanity, brand
64	and product names, artist name-drops, violence, drugs and alcohol, sexual
65	content, religious and political content, and date-stamped references. If
66	no lyrics are supplied, write "Lyric flags: not screened — lyrics not
67	provided." A lyric surprise in review kills the placement.
68
69	## Package workflow
70
71	1. Identify the track, artist, genre, mood, tempo, lyric themes, versions,
72	existing assets, and target sync world.
73	2. Build the sync angle: scene fit; emotional use; trailer or montage fit;
74	brand fit; game or sports fit; creator campaign fit.
75	3. Fill the asset checklist: master file; instrumental; clean version; stems
76	if available; lyrics; credits; splits; sample status; contact path;
77	public/private links. Each item: exists / missing / unknown.
78	4. Screen lyrics and write the lyric flags (hard gate 5).
79	5. Separate confirmed rights facts from open clearance questions (hard gates
80	1-2).
81	6. Write the one-sheet and pitch email only if gates 3-4 pass.
82	7. Stop at a clean review package. No promo CTA, placement promise, clearance
83	claim, or outreach claim.
84
85	## One-sheet contract
86
87	The one-sheet is supervisor-facing. It contains exactly these fields:
88
89	```text
90	Track / artist / featuring:
91	Length / tempo / key (if known):
92	Genre and mood tags:
93	Sounds like: (era and energy references; never copy a protected identity)
94	Scene fits: (top 3, one line each)
95	Lyric themes:
96	Lyric flags:
97	Versions available: (master / instrumental / clean / stems)
98	Rights status: (one line, confirmed facts only)
99	Open clearance questions:
100	C

People who liked this also viewed

6 picks

Type