trend-to-song
Create songs and content campaigns from trending cultural moments. Use when someone identifies a trending topic, viral moment, reality TV drama, meme, or cultural event and wants to turn it into a song and distribution strategy. Also triggers on "make a song about this trend," "capitalize on this moment," "reverse engineer from the market," "cultural moment to song," "trend-jack," or "burner page strategy." This flips the traditional music workflow — instead of song-first then marketing, you go market-first then song.
What this skill does
# Trend-to-Song Pipeline Turn trending cultural moments into songs and test campaigns in 72 hours or less. ## Why This Exists Traditional music: write a song, then figure out how to market it. This workflow: spot a cultural moment, build a song around it, test market fit fast. AI song generation makes this possible. You can produce a finished track in hours, not weeks. The bottleneck is no longer production — it's speed of trend identification and execution. ## The Core Insight Cultural moments create temporary demand for content. Someone will monetize that demand with music. The question is whether it's you or someone else. Speed wins. **Real example:** When a major reality TV betrayal storyline explodes, fans flood TikTok with edits. Whoever's song soundtracks those edits captures the wave. This happened with Alex Warren and The Ordinary — a song became synonymous with a cultural moment because someone moved fast. ## Pipeline Overview ``` Day 0: Spot the trend Day 0: Extract emotional register + key phrases Day 0: Generate the song Day 1: Create burner/fan page Day 1: Post first edits using the song Day 2-3: Monitor response, iterate ``` ## Step 1: Spot the Trend Identify cultural moments with these qualities: - **High emotional charge** — drama, betrayal, heartbreak, triumph - **Active fan edit community** — people are already making content about it - **No dominant soundtrack yet** — the moment hasn't been "claimed" by a song - **Relatability** — the situation maps to universal emotions (unrequited love, friendship betrayal, coming of age) **Sources to monitor:** - Reality TV discourse (Bravo, Netflix, dating shows) - Celebrity drama and breakups - Viral TikTok storylines - Meme formats with emotional undertones - Seasonal/cultural events (prom season, breakup season, graduation) ## Step 2: Extract the Emotional DNA Before generating lyrics, identify: 1. **Emotional register** — What does the audience *feel* about this moment? (heartbreak, rage, vindication, bittersweet nostalgia) 2. **Key phrases and slang** — What language is the internet using? Specific phrases from the source material, trending slang, inside jokes 3. **The audience** — Who is making edits and engaging? (teenage girls, reality TV fans, a specific fandom) 4. **Comparable songs** — What existing songs are being used in edits right now? Match that vibe **Deliverable:** Send the song creator a brief with: - 3-5 key phrases or words to weave in - The target emotional feel (e.g., "sad girl anthem," "vindication banger," "bittersweet nostalgia") - Reference tracks for vibe - Any specific lyrics or hooks you want included ## Step 3: Generate the Song Use AI music generation to produce the track. **Guidelines:** - Match the emotional register from Step 2 - Weave in the identified phrases naturally — they should feel like lyrics, not forced references - Keep it short — 2:00 to 2:30 is ideal for social content - The hook should be immediately usable as a 15-second clip - Produce in a genre that fits the audience (sad girl pop, lo-fi bedroom, etc.) **Output:** MP3 file ready for content creation ## Step 4: Set Up Distribution **Create a burner/fan page** — not the main artist profile. Why a burner page: - Tests market fit without risking the artist's brand - Can be positioned as a "fan account" or "edits account" - If it flops, no harm done - If it pops, you can connect it back to the artist **Page setup:** - Name it something relevant to the trend or fandom - Bio should reference the cultural moment - Post 2-3 pieces of content before the song content to establish the page ## Step 5: Create and Post Content **Types of content to create:** - Fan edits using clips from the trending moment + the new song - Text-on-screen videos with relatable captions tied to the moment - "POV" style content that puts the viewer in the emotional situation - Duets/stitches with viral posts about the moment **Posting strategy:** - Post 3-5 pieces on Day 1 - Use the song as the audio on every post - Tag relevant hashtags for the trend - Post at peak engagement times for the target audience ## Step 6: Monitor and Learn **Track within 48-72 hours:** - Which edits get the most views? - Is anyone else using the song audio? - What's the save-to-view ratio? (saves = strong signal) - Are people commenting about the song specifically? - Does the audio page show organic usage? **Decision framework:** - **If it catches:** Double down. More content. Consider connecting to artist profile. Create more songs for adjacent moments - **If it's flat:** Analyze why. Wrong emotional register? Bad timing? Oversaturated moment? Learn and move faster next time - **Either way:** You now have data on what this audience responds to ## Speed Benchmarks The value of this workflow is speed. Track your execution time: | Phase | Target | Max | |-------|--------|-----| | Trend spotted to brief sent | 2 hours | 4 hours | | Brief to finished song | 4 hours | 12 hours | | Song to first content posted | 6 hours | 24 hours | | Total pipeline | 12 hours | 48 hours | If you're consistently taking longer than 48 hours end-to-end, the trend may have passed by the time you post. Speed is the entire point. ## What Makes a Good Brief **Good brief:** > Bravo show drama: best friend secretly dating her friend's ex post-divorce. Internet is furious on behalf of the betrayed friend. Audience is women 18-35. Emotional register: vindication + heartbreak. Key phrases: "she knew the whole time," "bestie betrayal." Vibe: Olivia Rodrigo meets Gracie Abrams. Make it a sad girl anthem that sounds like it could be the betrayed friend's internal monologue. **Bad brief:** > Make a song about reality TV drama. The more specific the brief, the better the song fits the moment. ## Case Study Template After each pipeline run, document what happened: ``` ## Trend: [What happened] **Spotted:** [Date/time] **Song delivered:** [Date/time] **First post:** [Date/time] **Total pipeline time:** [X hours] **Results (72h):** - Total views: - Best performing edit: [views, type] - Audio reuses by others: - Save rate: **Learnings:** - What worked: - What didn't: - Next time: ``` ## Integration with Recoupable - Use the content agent to generate video edits once the song exists - The song can be added to an artist's catalog via the standard song pipeline - Burner page content can be cross-posted to the artist's channels if it performs - Track performance data through the standard analytics pipeline
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.