$npx -y skills add JasonColapietro/suede-creator-skills --skill suede-campaign-in-a-boxTurn a song or release into a full artist campaign: hooks, rituals, visuals, merch, rollout calendar, email, site copy, and fan actions.
| 1 | # Suede Campaign In A Box (Whole Enchilada) |
| 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 | The all-in-one artist campaign skill: it turns a song, release, era, catalog |
| 25 | moment, show, or drop into a complete campaign an artist can actually execute. |
| 26 | Every campaign capability lives here as a labeled lane. Pick the lane you need, |
| 27 | or run the full package that stitches them together. |
| 28 | |
| 29 | **Core principle:** you organize and prepare. You do not clear rights, confirm |
| 30 | ownership, approve payouts, write to any registry, secure placements, |
| 31 | manufacture cosigns, or guarantee that anything will go viral or sell. Say what |
| 32 | to test; never promise the result. |
| 33 | |
| 34 | ## Pick the lane (router) |
| 35 | |
| 36 | Read the request and route to the lane that fits. You can chain lanes — most |
| 37 | real campaigns use several. If the request is "do the whole rollout," run |
| 38 | **Lane 0 (Full Campaign Package)** and pull the other lanes in as sections. |
| 39 | |
| 40 | | If the user wants... | Go to lane | |
| 41 | |---|---| |
| 42 | | The whole rollout packaged: announce, teaser, release week, post-drop, fan proof, catalog afterlife | **0 — Full Campaign Package** | |
| 43 | | The artist to feel recognizable before any bio/campaign/site is written — identity, world, voice, anti-references, fan promise | **1 — Identity Forge** | |
| 44 | | A release turned into a recognizable world: visual language, symbols, color, wardrobe, content behavior, rollout tone | **2 — Era Builder** | |
| 45 | | One track expanded into a creative universe: scenes, characters, imagery, captions, drop ideas, mechanics | **3 — Song To Universe** | |
| 46 | | The 5-15 second moments that people clip, duet, remix, chant, or share | **4 — Hook Hunter** | |
| 47 | | A memorable launch moment: stunt, fan mission, puzzle, timed drop, geo clue, unlock, collector action, street-team mechanic | **5 — Release Stunt Lab** | |
| 48 | | Repeatable fan behavior: phrases, gestures, comments, unlock actions, live moments, collector rituals, trackable tasks | **6 — Fan Rituals** | |
| 49 | | Visual direction: visualizer, lyric video, canvas loop, stage loop, cover motion, AI video prompts, teaser edits, scene boards | **7 — Visualizer Director** | |
| 50 | | Merch and physical/collector objects beyond generic logo shirts, tied to lyrics, lore, and fan behavior | **8 — Merch Object Lab** | |
| 51 | | A live set shaped like a show: arc, intros, transitions, crowd moments, visual cues, encore, talk breaks, merch tie-ins | **9 — Setlist Theater** | |
| 52 | | Old songs, demos, takes, covers, stems, live clips, unreleased folders, anniversaries, or forgotten assets revived | **10 — Catalog Resurrection** | |
| 53 | | Collaborator, remixer, producer, visual artist, venue, brand, or creator matchmaking with outreach angles | **11 — Collab Matchmaker** | |
| 54 | |
| 55 | Default starting order when identity is fuzzy: Lane 1 → Lane 2 → (Lane 3 if it |
| 56 | is one song) → hooks/stunts/rituals/visuals/merch/live as needed → Lane 0 to |
| 57 | package. If the artist already has a clear world, jump straight to the lane the |
| 58 | request names. |
| 59 | |
| 60 | ## Multi-agent vs single-agent (ask up front) |
| 61 | |
| 62 | This skill can run as a coordinated multi-agent team — one agent per lane, plus |
| 63 | a packager that reconciles them into one campaign. Before spawning any fleet, |
| 64 | ASK: "Run this as a multi-agent team (more thorough, may use more tokens) or as |
| 65 | a single agent (faster, one pass)?" Never silently spawn a fleet. If the user |
| 66 | does not choose, default to single-agent and offer to escalate. In multi-agent |
| 67 | mode, keep one shared identity/era spine so the lanes do not contradict each |
| 68 | other, and have the packager resolve conflicts before output. |
| 69 | |
| 70 | --- |
| 71 | |
| 72 | ## Lane 0 — Full Campaign Package (announce / teaser / release-week / post-drop) |
| 73 | |
| 74 | Use this to turn scattered release ideas into a campaign an artist can actually |
| 75 | execute. |
| 76 | |
| 77 | 1. Identify the release, artist state, audience, platforms, timeline, assets, |