Create a Blog Post

What It Does

You paste in some raw stuff — a Facebook post you wrote, a video transcript, voice notes, a messy first draft — and the tool turns it into a finished blog post on The Marketing Show. It makes the writing sound like you (not like a robot), cuts out filler words, adds headings so it is easy to scan, links to other pages on your site where it makes sense, drops in affiliate links if any are relevant, and credits whoever originally said what you are writing about. Then it opens the new page in your browser so you can read it and decide whether to publish.

When To Use

Right after a conversation, Facebook post, or YouTube video that contains a reusable idea.
When you paste a big blob of text into the chat with no instructions — Claude will ask if you want to run this.
When you say: “turn this into a blog post”, “create a blog post from this”, “write an article about”.

How To Invoke

Say any of the trigger phrases, or run the slash command:

/create-blog-post

Claude will ask clarifying questions before writing:

What category should this go in?
What slug should we use?
Is there a featured image?
Any specific affiliate links or CTAs beyond the defaults?

Prerequisites

Requirement	Where
The Marketing Show repo	`~/apps/themarketingshow/`
Voice profile master reference	`~/apps/james-voice/voice-profile.md`
Affiliate link config	`~/apps/themarketingshow/src/config/affiliates.ts`
AI-tell linter	`~/apps/cc/ai-tell-check.sh` (catches AI-fingerprint phrases)
Dev server running (for preview)	`cd ~/apps/themarketingshow && npm run dev -- -p 3100`
`yt-dlp` or `curl` (for YouTube thumbnails)	system

Where It Lives

Skill definition: ~/.claude/commands/create-blog-post.md
Target repo: ~/apps/themarketingshow/ (content under content/<category>/)
Related skills: /propagate (runs wiki-link propagation after the post is saved)

Writing Rules (Enforced)

Match the solo extended tutorial voice — conversational, analogy-heavy, proof by personal experience, honest about downsides, credit others by name.
Strip AI-tell patterns — no em dashes, no staccato tricolons, no “genuinely/leverage/robust/seamless”, no “Not X. Not Y. Just Z.” fragments. Enforced by the AI-tell linter before saving.
First-hand knowledge only. Do not invent anecdotes or unsourced claims.
Title 50-60 chars. Excerpt 120-150 chars. Exact.
No H1 in body. The template renders H1 from frontmatter.
No self-referential wiki-links. Never wiki-link to a page that does not exist — use plain text instead.
Attribution. If the content came from someone else (Facebook post, interview, transcript), name them clearly in the opening.
PII scrubbing. Real customer names, phone numbers, emails, addresses get replaced with fictional examples.

Example Session

James: [pastes a long Facebook post about why he switched from Zapier to n8n]

Claude: Looks like you pasted some content — want me to run /create-blog-post
        and turn this into a blog post?
James: yes
Claude: Running /create-blog-post. A few questions before I write.
        - Category: I suggest "Automation". OK?
        - Slug proposal: "why-i-switched-from-zapier-to-n8n"
        - Featured image?
James: no image, automation is fine, slug looks good
Claude: [searches existing content for wiki-link candidates]
        [drafts the post]
        [runs AI-tell linter, fixes 3 violations, re-runs]
        [proposes file path: content/automation/zapier-to-n8n.md]
James: save it
Claude: [saves, opens in browser with the changed section highlighted]
        Draft is live at http://localhost:3100/automation/zapier-to-n8n
        Want me to run /propagate to add wiki-links from other pages?

Quality Checklist (Enforced)

AI-tell linter passes (no AI fingerprints)
No self-referential wiki-links
All wiki-link targets exist (plain text if not)
Affiliate URLs match affiliates.ts
Title 50-60 chars, excerpt 120-150 chars
No H1 in body
At least one mid-article CTA
Original author is properly attributed
No PII
Featured image not duplicated in body (template renders as hero)

Known Gaps / TODOs

No auto-publish. Claude saves to content/ but does not commit and push without asking. By design — James reviews every post before deploy.
Propagation is a separate skill. /propagate runs AFTER the post is saved. The two should probably be chained, but for now they are manual.