My Automated Content Pipeline

•One anchor script per week: a 15-second topic intro ("This week we're talking about X, because Y") + a 2-3 minute body.

•The body is pitched to "a sharp business owner who isn't a marketer" (Voice DNA video-script standard): plain language, lower density. The blog and newsletter keep their fuller depth.

•The body carries at least 3 self-contained hook-pattern moments (Open Loop, Specific Number, Pattern Break, Name the Pain), each marked '# HOOK MOMENT: <pattern>' and able to stand alone as a 20-40 second clip Opus can pull. The throat-clear anti-pattern is a hard reject anywhere in the body.

•Stage 1 self-check (brand-standards SKILL > Shorts Hook Framework > Anchor Script Self-Check) must pass before filming.

•Prompter files (effective W27): run `python3 scripts/shorts-renderer/extract_prompter_clips.py --week N --targets repo` to emit W{N}-intro.txt + W{N}-body.txt (words-only, the two takes) + W{N}-full.txt (consolidated) into scripts/produced/shorts/prompter/. Pure derivatives of the master; never hand-edited. The Mac Mini launchd watcher mirrors them into iCloud tools/shorts-processor/prompter/ for filming.

•Push content: each post stays on its scheduled slot, fired by the host platform on the calendar day

•Distribution via Postiz Cloud CLI to YouTube, TikTok, and LinkedIn (PL company + WD personal). X is killed (see hub/decisions/2026-06-01-kill-x-channel.md).

•Schedule grid: YouTube anchor Mon + intro-teaser Short Mon + meat Shorts Mon/Wed/Fri; TikTok meat Shorts Mon/Wed/Fri; LinkedIn anchor Tue (both accounts) + meat Shorts Wed/Fri (Personal only)

•Shorts on-screen CTAs: the intro teaser says 'click the link in the description to see more' (drives to the anchor); the meat Shorts say 'Follow for more'

•The 3 meat Shorts intentionally cross-post to YouTube + TikTok + LinkedIn Personal the same day; the no-duplicate-same-day rule is retired for Shorts (the no-repost rule still holds)

•Custom YouTube thumbnail (1280x720, generated from the canonical base + the week's headline) is attached to the anchor. Postiz-first; if Postiz can't attach a custom thumbnail to a scheduled long-form, the anchor publishes via YouTube Studio. See reference/skills/brand-standards/SKILL.md > Thumbnail.

•Opus renders (reframe + captions + picks); Postiz distributes. Runs in a local Claude Code session only (Opus UI + downloaded files + Postiz CLI are all local).

•The YouTube anchor description and LinkedIn anchor body carry the blog URL with a compelling description and a CTA to the blog + Beehiiv; never 'link in comments'

•Short captions carry the on-screen CTA's written companion + #ProfessorLeads as the first hashtag

•Every external URL pointing back to professorleads.com is UTM-tagged per the convention in reference/skills/brand-standards/SKILL.md (utm_source, utm_medium, utm_campaign=w{N}-{theme}, utm_content). Effective W20.

•Every piece of copy passes both Voice DNA and Brand Standards checks

•Drafted in hub/pipeline/weekN-upload-prep.md for traceability before being applied to scheduled posts

•Long-form blog post tied to the week's content theme, at the existing McKinsey-level depth

•Includes the Forbes Further Reading section and the discoverability triad per brand-standards

•Passes Voice DNA and Brand Standards before moving to Stage 8

•Drafted into content-drafts/blog/, then promoted to content/blog/ in Stage 8

•Full edition drafted for Beehiiv email subscribers, scheduled for the Tuesday 10:00 AM ET send

•Teaser edition drafted for LinkedIn Newsletter (The Playbook Preview), scheduled for 10:05 AM ET

•Both scheduled via Chrome MCP in the same session as the drafting (single-session pattern)

•The 5-minute lag exists so the LinkedIn body's archive link resolves to a populated Beehiiv archive page on first click

•Playbook Preview body includes a prominent single-sentence Beehiiv cross-over CTA at peak interest (effective Issue 9, per 2026-04-23 health-check rule in brand-standards/SKILL.md)

•Beehiiv issue must have a one-sentence post description (Excerpt / Subtitle field) populated before the Schedule click; the field renders on every archive card at newsletter.professorleads.com (effective 2026-04-23, after the audit caught multiple blank cards)

•Beehiiv email Subject Line caps at 60 characters so the hook lands before Gmail / Apple Mail / Outlook truncation; the Beehiiv counter reads /200 but the rule is 60 (effective 2026-04-27, after the Apr 21 108-char send lost ~16pp open rate)

•Beehiiv email Subject Line and LinkedIn Newsletter headline are separate instruments effective W19 (2026-05-05): write the Subject Line for inbox curiosity-gap framing and the LinkedIn headline for article-card payoff framing; they can match, but only on purpose. Evidence: W17 curiosity gap opened 34.88% on Beehiiv vs W18 numbers/dollar at 22.73% on the same 44-recipient list, while W18 numbers/dollar tripled LinkedIn Newsletter impressions WoW (487 vs 173) on the same audience arc

•Publish-on-completion: fires the moment Voice DNA + Brand Standards self-checks pass AND all links verify live

•Frontmatter date stays at the canonical week-of date even when the file lands earlier

•Markdown committed and pushed to main; Vercel auto-deploys within 60 seconds

•Pull content has no audience notification, so early publish is invisible to subscribers and improves SEO indexing time

•After Vercel deploy: submit the new blog URL to Google Search Console for indexing via the URL Inspection tool (see CLAUDE.md > Google Search Console Indexing)

•Push content: drafted and scheduled in advance, fired by LinkedIn on the Monday morning slot

•LinkedIn text post with a direct link to the new blog article, posted from the William DeCourcy personal profile

•Drafted and scheduled in the same Chrome MCP session that publishes the blog (single-session pattern)

•Voice DNA and Brand Standards self-checks gate the draft before scheduling

•Not event-triggered by the blog publish: the calendar slot is the source of truth

•Host platforms fire scheduled content on their slots — nothing new is created here

•15-minute daily engagement routine: respond to comments, engage with others, reach out for collaborations

•No manual intervention needed unless the health check flags something