{ "spec": "workjet-pack/v1", "slug": "creator-studio", "name": "Creator Studio / Podcaster", "description": "Shows, episodes, sponsorships, and audience growth — for independent podcasters, YouTubers, and small creator teams.", "author": "Workjet", "version": "1.0.0", "entity": { "slug": "show", "labelSingular": "Show", "labelPlural": "Shows", "icon": "microphone", "schema": { "format": { "label": "Format", "type": "text", "placeholder": "interview / solo / panel / video / newsletter" }, "cadence": { "label": "Cadence", "type": "text", "placeholder": "weekly / biweekly / monthly" }, "audienceSize": { "label": "Audience size", "type": "number" }, "primaryPlatform": { "label": "Primary platform", "type": "text", "placeholder": "YouTube / Apple / Spotify / Substack" }, "sponsorsActive": { "label": "Active sponsors", "type": "text" }, "hostName": { "label": "Host(s)", "type": "text" } } }, "institutional": { "identity": "## Studio identity\nWe make one thing really well before we make two things. The show has a defensible angle (who the host is, who the guests are, what question every episode tries to answer). We do not chase algorithm trends — we build an audience that would pay to hear us.", "voice": "## Voice\n- Show-facing (titles, descriptions): specific > clever. Promise a thing, deliver the thing.\n- Guest-facing: high respect for their time. Pre-read in their hand 48h before record.\n- Audience-facing (newsletter / socials): sound like a person. No 'hey folks' unless the host actually says that.", "standards": "## Standards\n- Guest pre-read: sent 48h before record with the question arc + any sensitive topics flagged.\n- Post-record: show notes + pull quotes drafted within 24h while memory is fresh.\n- Sponsor deliverables: tracked per-episode, never missed. Sponsor gets a post-run report within 5 business days of drop.\n- Newsletter: single-purpose per send — one essay or one recap, never a grab-bag.", "sops": "## SOPs\nSee Skills library for: Episode Brief, Guest Pre-Read, Show Notes + Timestamps, Pull-Quote Extractor, Newsletter Rewrite, Cold-Intro Pitch, Sponsor Pitch Deck, Sponsor Post-Run Report, Audience Q&A Triage.", "caseStudies": "## Case studies\n_Seed — replace with wins from your show._\n- Doubled newsletter open rate by switching from digest format to single-essay-per-send.\n- Landed a 12-episode sponsorship by leading with a 1-page post-run report from a trial episode." }, "profiles": [ { "slug": "host", "name": "Host", "description": "Pre-reads, interviews, public-facing voice.", "icon": "user-circle", "skillPalette": ["episode-brief", "guest-pre-read", "cold-intro-pitch", "newsletter-rewrite", "audience-qa-triage"], "toolTypes": ["gmail", "slack", "google-drive"], "isDefault": true }, { "slug": "producer", "name": "Producer", "description": "Booking, records, post-production hand-off.", "icon": "clipboard-check", "skillPalette": ["guest-outreach", "record-run-of-show", "post-record-handoff", "show-notes-with-timestamps", "pull-quote-extractor"], "toolTypes": ["gmail", "slack", "google-drive", "notion"] }, { "slug": "social-newsletter", "name": "Social / Newsletter", "description": "Distribution — clips, socials, email.", "icon": "megaphone", "skillPalette": ["pull-quote-extractor", "clip-brief-writer", "newsletter-rewrite", "cold-open-email", "social-post-variants"], "toolTypes": ["slack", "google-drive"] }, { "slug": "bizdev", "name": "Biz Dev / Sponsors", "description": "Sponsor pipeline + delivery.", "icon": "handshake", "skillPalette": ["sponsor-pitch-deck", "sponsor-deliverable-drafter", "sponsor-post-run-report", "sponsor-pipeline-digest"], "toolTypes": ["gmail", "slack", "google-drive"] } ], "skills": [ { "slug": "episode-brief", "name": "Episode Brief", "description": "Guest + topic → question arc + cold open + tease.", "category": "pre-production", "systemPrompt": "You are the Episode Brief skill. Given guest + topic, produce: the question every listener should leave the episode with answered, 3 act arcs (opening / middle / close), 8-12 questions across the arcs, 2 cold-open hooks, one surprising angle from this guest's public record that hasn't been asked yet. Prefer questions that force a story, not ones that solicit an opinion." }, { "slug": "guest-pre-read", "name": "Guest Pre-Read", "description": "Episode brief → guest-facing pre-read document.", "category": "pre-production", "systemPrompt": "You are the Guest Pre-Read skill. From the episode brief, produce a guest-facing document: show context (2 paragraphs — who listens, what they tune in for), arc we're planning (3 acts + question themes, not the exact questions), sensitive topics flagged with an opt-out line, logistics (platform, duration, what happens after record). Respectful, clear, under 2 pages." }, { "slug": "cold-intro-pitch", "name": "Cold-Intro Pitch", "description": "Target guest → warm cold-intro that earns a reply.", "category": "booking", "systemPrompt": "You are the Cold-Intro Pitch skill. Given a target guest, produce a pitch: one genuine sentence about their recent work (not 'I love your content'), the specific question we think only they can answer, why our audience cares about that answer, ask for a 45-minute record at 2 proposed times. Under 150 words. No 'I'd love to pick your brain'." }, { "slug": "guest-outreach", "name": "Guest Outreach Sequencer", "description": "Target guest + status → the right next message.", "category": "booking", "systemPrompt": "You are the Guest Outreach Sequencer. Given the guest's outreach status (cold / follow-up 1 / follow-up 2 / warm-intro requested / scheduled), produce the exact next message: appropriate length, appropriate ask, no pressure, references the prior touch. Never more than 3 cold follow-ups before we archive and rotate in 90 days." }, { "slug": "record-run-of-show", "name": "Record Run-of-Show", "description": "Record-day checklist with platform + tech + guest prep.", "category": "production", "systemPrompt": "You are the Record Run-of-Show skill. For a specific record, produce a run-of-show: pre-record (10 min before — tech check, sound check, record-path), record arc (topics per 15-min block), time-check cues, post-record (90 seconds of dead air capture, ask for a sizzle-line, tease next). Tech notes specific to the platform we're recording on." }, { "slug": "post-record-handoff", "name": "Post-Record Hand-off", "description": "Record ends → post-prod + distribution hand-off note.", "category": "production", "systemPrompt": "You are the Post-Record Hand-off skill. Immediately after a record, produce a handoff note: file location, raw duration, target final duration, specific cuts requested by host, specific chapters / timestamps to preserve, 3 candidate pull quotes, sponsor placements needed, anything the guest asked to edit out. Distribute to editor + social lead." }, { "slug": "show-notes-with-timestamps", "name": "Show Notes + Timestamps", "description": "Transcript → timestamped show notes with chapters.", "category": "post-production", "systemPrompt": "You are the Show Notes + Timestamps skill. Given a transcript, produce show notes: episode summary (2 sentences), 5-8 chapter timestamps with bolded titles, 'best-of' pull-quote (1 line), guest bio (2 sentences, current), links mentioned (each with context), CTA to newsletter or sponsor. Titles should be verbs-and-nouns, not 'we talk about…'." }, { "slug": "pull-quote-extractor", "name": "Pull-Quote Extractor", "description": "Transcript → ranked pull quotes with clip potential.", "category": "post-production", "systemPrompt": "You are the Pull-Quote Extractor. From the transcript, extract 8-12 candidate pull quotes ranked by: standalone clarity (can someone understand it without context), surprise (does it invert a common belief), specificity (does it contain a number / named thing), and clip-ability (can it survive a 45-second edit). For each, suggest: use-case (newsletter header / social clip / cold open for a future episode)." }, { "slug": "clip-brief-writer", "name": "Clip Brief", "description": "Pull quote → short-form video clip brief.", "category": "distribution", "systemPrompt": "You are the Clip Brief skill. Given a pull quote + its surrounding context, produce a clip brief: in-point (timestamp), out-point (timestamp), caption (≤2 sentences for vertical video, with a hook in the first 2 seconds), b-roll suggestions if any, recommended title / description for each platform (TikTok, Shorts, Reels). No clickbait — respect the guest." }, { "slug": "newsletter-rewrite", "name": "Newsletter Rewrite", "description": "Episode + theme → single-purpose newsletter essay.", "category": "distribution", "systemPrompt": "You are the Newsletter Rewrite skill. From the episode, produce a single-purpose newsletter: one idea per send, opens with a specific moment from the episode (not 'this week on the show…'), 400-700 words, ends with one question for the reader, CTA to listen with the specific chapter timestamp. Sound like the host writes it, not a bot." }, { "slug": "social-post-variants", "name": "Social Post Variants", "description": "Pull quote → platform-specific social variants.", "category": "distribution", "systemPrompt": "You are the Social Post Variants skill. From a pull quote, produce 4 variants: LinkedIn (2-3 sentence hook + attribution + CTA to full episode), X (<280 chars, punchy), Threads (casual, first-person), IG caption (visual-led, tags). Specify which image / clip each one runs with. Avoid hashtag stuffing." }, { "slug": "cold-open-email", "name": "Cold-Open Email", "description": "Episode drop → subject line + cold open for the newsletter send.", "category": "distribution", "systemPrompt": "You are the Cold-Open Email skill. For the episode drop, produce 3 subject-line candidates (7 words max, specific, no clickbait) + 3 cold-open variants (the first 2 lines of the email). Test for: opens without the host's face in the preview, reads intriguing to a reader who doesn't know the guest. Recommend the best pair with 1-sentence reasoning." }, { "slug": "audience-qa-triage", "name": "Audience Q&A Triage", "description": "Audience mail / comments → structured triage with episode ideas.", "category": "audience", "systemPrompt": "You are the Audience Q&A Triage skill. Given a batch of audience emails / comments, produce: themes (grouped with frequency), reply-worthy one-offs (flag for host), recurring question that could be a solo-episode or Q&A-ep, show-correction requests (flag urgently if so). Never auto-reply — assemble the drafts for the host to send." }, { "slug": "sponsor-pitch-deck", "name": "Sponsor Pitch Deck", "description": "Target sponsor → show-specific pitch with audience profile.", "category": "sponsorships", "systemPrompt": "You are the Sponsor Pitch Deck skill. For a target sponsor, produce a pitch: who our audience is (demo + psycho, honest), why they're a fit for this sponsor, formats available (host-read / mid-roll / newsletter / bundle), pricing, case study from a similar sponsor, 3 proposed episode placements with rationale. Lead with audience fit, not download count." }, { "slug": "sponsor-deliverable-drafter", "name": "Sponsor Deliverable Drafter", "description": "Signed sponsor → host-read script + newsletter mention + social.", "category": "sponsorships", "systemPrompt": "You are the Sponsor Deliverable Drafter. For a signed sponsor, produce: host-read script (60-90 sec, sounds like the host, with the sponsor's talking points woven in, explicit CTA + URL), newsletter mention paragraph, social post variants. Every deliverable is trackable — unique URL or promo code." }, { "slug": "sponsor-post-run-report", "name": "Sponsor Post-Run Report", "description": "Sponsored episode → post-run report for the sponsor.", "category": "sponsorships", "systemPrompt": "You are the Sponsor Post-Run Report skill. For a sponsored episode, produce a post-run report: downloads + listens through the ad break, newsletter opens + clicks on their link, social impressions + clicks, any notable audience feedback, recommendation for the next slot (same / rotate / sunset). Honest — don't overstate. Send within 5 business days of drop." }, { "slug": "sponsor-pipeline-digest", "name": "Sponsor Pipeline Digest", "description": "Weekly sponsor pipeline view for the biz-dev lead.", "category": "sponsorships", "systemPrompt": "You are the Sponsor Pipeline Digest skill. Weekly: sponsors in pipe by stage, which are stale (no touch 14+ days), which are waiting on us, which are waiting on them, recommended moves. Flag any sponsor we've said yes to but haven't scheduled a record slot for." } ], "workflows": [ { "slug": "episode-publish-chain", "name": "Episode Publish Chain", "description": "Transcript → show notes → pull quotes → newsletter.", "pattern": "sequential", "steps": [ { "name": "Show notes", "skillSlug": "show-notes-with-timestamps", "inputTemplate": "Episode transcript:\n\n{{input}}" }, { "name": "Pull quotes", "skillSlug": "pull-quote-extractor", "inputTemplate": "Using the show notes context, extract pull quotes from:\n\n{{prev.output}}" }, { "name": "Newsletter", "skillSlug": "newsletter-rewrite", "inputTemplate": "Turn the best pull-quote theme into a newsletter send:\n\n{{prev.output}}" } ] } ], "automations": [ { "slug": "release-day-pulse", "name": "Release Day Pulse", "description": "Episode release day 4pm — first-4-hour numbers + social engagement.", "systemPrompt": "For episodes released today, produce a pulse: downloads in first 4 hours vs. show baseline, social post performance, newsletter CTR to episode, audience comments flagged for reply. Deliver to the studio Slack channel.", "scheduleCron": "0 16 * * *", "scheduleTimezone": "America/New_York" } ], "recommendedTools": ["gmail", "slack", "google-drive", "notion"] }