CHRISTINE Take Your Finished Post Live Without Touching Code
Blog Publisher takes a post you've already written and builds the real page — matched to your site's template to the pixel, wired with structured data and a clean URL, linked into the rest of your blog, and deployed live. Your words stay exactly as you wrote them.
← Back to the Skills LibraryInstalled in under a minute. No tech skills required.
You don't need to know how to code, and you don't need to set anything up. There are two blocks below. If you can copy and paste, you can install this.
Paste the instruction
Copy the first block and paste it into a brand-new Claude conversation. Don't hit send yet — it's the note that tells Claude what to do.
Paste the skill underneath, then send
Copy the full skill block and paste it right below the instruction. Send it. Claude builds the skill, personalizes it to your business, and confirms when it's ready.
Install the skill below for me. Keep the skill text exactly as written, then personalize its defaults from what you already know about me — my business, my voice, my priorities, and the places I keep my notes and files. Confirm when it's installed and show me exactly how to run it.
--- name: blog-publisher description: Turn a finished blog post in markdown into a production HTML page and ship it live to your site. On first run the skill interviews you to wire in where your blog files live, the post you clone as your house template, how your site serves clean URLs and deploys, your author name and closing call to action, then builds and deploys your version every time after. Use whenever you say "publish this post," "blog publisher," "build and ship this post," "get this live," or drop a finished draft and want it live on your site. --- # Blog Publisher: Finished Draft To Live Page This skill takes a finished blog post you already wrote and builds the production HTML page for it, then ships it to your live site. You supply the post as markdown. The skill handles faithful conversion to your house template, the structured data, the clean URL, the internal links, and the deploy. It leaves your words alone. Your markdown is the source of truth for the copy. The build matches your existing blog exactly and puts the page live in one command. ## First Run: Design Your Version The first time you run this skill, set it up. Ask me these questions one at a time, save my answers into this skill file as a CONFIG block, and use them on every run after this. If the answers are already saved, skip straight to the workflow. 1. Where do your blog files live, and what is the folder convention? (For example a blog folder of flat HTML files, a posts directory, or a CMS you publish through.) This tells me where the new page gets written. 2. Which existing post should I clone as your house template? Point me at one published post you like. I copy its head, styles, layout, navigation, footer, and closing block word for word so every new post matches. 3. How does your site serve clean URLs and how do you deploy? (A static host that serves files at extensionless URLs, a repo that auto-deploys on push, or a CMS with its own publish button.) This sets the URL shape and the ship command. 4. What is your author name, and what is your standard closing call to action? Paste the exact block you end every post with. I reuse it word for word on each new post. 5. What is your image convention for the social preview? (For example images/<slug>.png at 1200 by 630.) I wire the Open Graph and Twitter image to it. If I ever say "redesign blog publisher," run this interview again. ## Input - A finished blog post as markdown (the source of truth for the copy) - A slug, category, and display date (I infer any you leave out and tell you what I assumed) - A short meta description, or I draft one from the post for your approval ## Workflow ### Step 1: Clone Your House Template Read the template post you named in setup. Copy its head block, style block, navigation, footer, closing call to action, and any tracking scaffolding word for word. Only the content and the metadata change on the new page, so it matches the rest of your blog to the pixel. ### Step 2: Build The Page Create the new page file at the location your setup defines, with these parts in order: - Head: title tag, meta description, canonical clean URL, the full Open Graph and Twitter block, the published date, fonts, and your cloned style block. - Three structured data blocks: BlogPosting, FAQPage, and Article. The FAQPage holds one question and answer for each real question H2 in the post. A heading that is a call to action stays out of the schema. - Body: your header (back link, category, H1, author, date), then the post body converted from your markdown. Lead each question section with one bold direct-answer sentence, then your prose. Close with your standard call to action block, then the author line. - Wire the social preview image to your convention. ### Step 3: Add Internal Links In the same run, connect the post to the rest of the site both ways. - Three to five outbound links from the new post to existing posts. Read your post inventory, pick genuine topical matches, and weave each link into a sentence that is already there. One link per section. Confirm each target exists. - Two to three backlinks from existing posts to the new one. Read each candidate, find a natural sentence, add one link, only where the topic truly connects. ### Step 4: Ship It Run your one-command build and deploy. If your setup rebuilds a sitemap or a post listing, run that first so the new post lands in the right place. Then deploy the way you set up. Hand me the live URL. ### Step 5: Confirm Give me a short receipt: the file built, the live URL, the three schema blocks in place, the outbound and inbound links added, and the deploy confirmed. ## Build Standards - Match the template exactly. Copy its shell word for word and change only content and metadata. Invent no new styles. - One H1 per page. Question sections use real heading tags. Every image carries width, height, and alt text. Links use HTTPS. - Title tag runs 50 to 60 characters. The Open Graph title and the Twitter title match the page title exactly. - The FAQPage schema holds only real questions from the post. A closing call to action heading always stays out of the FAQ. - Clean URLs need no extra config on most static hosts. Confirm your host serves the file at its extensionless path before adding any redirect. ## Voice and Tone Write any copy you generate in the voice you set up in first run. Direct, clear, specific, written to the reader as "you." Keep the words of the supplied post as they are. Never use: delve, unlock, craft, foster, tapestry, embarking, unleash, unveil, realm, boasts, revolutionize, tenets. No semicolons, no em dashes, no contrastive framing. ## Session Close After the deploy lands, offer two follow-ups: a set of social preview image text options drawn from the post, and a second internal-linking pass if you added more posts since.
From then on, just drop in a finished draft and say "Publish this post."
Want to go further than skills?
Skills like this are how Christine runs her own business every day. In the Heart-Led AI Signature Group Coaching, she teaches you the whole system — live, in plain English, at your pace.
Explore Signature CoachingOne live page. Every piece of a real publish.
Run Blog Publisher on a finished draft and you don't get a preview — you get a production page, shipped. Here's everything a single run hands back:
1 · A Page That Matches Your Site Exactly
The skill clones the one published post you chose as your house template — head, styles, navigation, footer, and closing block, word for word. Only the content and metadata change.
2 · A Complete Head Block
Title tag at 50 to 60 characters, meta description, canonical clean URL, the full Open Graph and Twitter block, the published date, and your social preview image wired to your convention.
3 · Three Structured Data Blocks
BlogPosting, FAQPage, and Article — with the FAQ built only from the real question headings in your post, so search engines get an honest map of the page.
4 · Internal Links in Both Directions
Three to five outbound links woven into sentences already in your post, plus two to three backlinks added from existing posts — every target confirmed to exist, every link a genuine topical match.
5 · The Deploy — and a Receipt That Proves It
If your setup rebuilds a sitemap or post listing, that runs first. Then your one-command deploy ships the page, and you get the live URL plus a receipt: the file built, the three schema blocks in place, the links added both ways, and the deploy confirmed. It even offers two follow-ups — social preview text options drawn from the post, and a second linking pass as your blog grows.
And your writing?
Untouched. Your markdown is the source of truth for the copy, and the skill leaves your words alone — it converts, it never rewrites. It also invents no new styles, keeps call-to-action headings out of the FAQ schema, and tells you plainly anything it inferred — like a slug or a date you didn't supply.
Keep stacking: pairs beautifully with Publish-Ready Check
Publish-Ready Check inspects a finished post against your full readiness list and packages the handoff — Blog Publisher is the one that takes a ready post, builds the page, and ships it live.
Get Publish-Ready Check →Because written isn't the same as published.
Plenty of good posts die in a drafts folder because getting them onto the site feels like a whole project. Blog Publisher turns that project into one run.
Your template is the law
Instead of guessing at your design, the skill copies one post you already like — word for word — and changes only content and metadata. Every new post matches your blog to the pixel, with zero style drift.
The schema tells the truth
The FAQPage block is built only from real question headings in the post, and a call-to-action heading always stays out. Search engines and AI answers get a map that matches what's actually on the page.
New posts never arrive orphaned
Outbound and inbound links are added in the same run the page ships, so the post joins your site already connected. That's the link work most people mean to do later — and later never comes.
First run makes it your publisher
The skill interviews you once: where your files live, which post is the template, how you deploy, your author line, and your closing call to action. From then on it publishes the way your site publishes.
One command means it actually ships
The deploy isn't a separate chore waiting at the end — it's the last step of the same run. The distance between finished and live stops being a someday task.