Drop in a finished blog post and get back a production page that ships live to your site. On first run it wires into where your files live, the template it clones, and how you deploy, then builds and ships your version every time after.
← All Claude SkillsYou write great posts, and getting each one live is a stack of fiddly steps: match the template, add the schema, set the clean URL, wire the links, run the deploy. This skill does all of it from your finished markdown. The first time you run it, it interviews you and designs itself into your world: where your files live, the post you clone as your template, how you deploy, your author line, and your image convention. Every run after that, it just builds and ships. Copy the two blocks below and give them to your Claude.
Step 1. Copy the skill block below.
Step 2. Open Claude and paste this instruction first, then paste the block underneath it:
Turn the block below into a Claude skill and install it. Create the skill file exactly as written. Then personalize it with smart defaults from what you know about me: my business, my voice, my current priorities, and where I keep my work. Confirm when it is installed and tell me 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.
Claude reads the block, builds the skill file, and installs it. From then on, you just run the skill in any conversation. No folders to find, no code to write.
Every week you see what's working, build it live, and put it to work in your business.
Here's the shape of what this skill hands you when it runs. Copy it, use it, keep moving.
You don't need to hold any of this in your head. That's the skill's job. If you're curious what it's doing for you, here's the idea underneath it.
A finished draft still sits between you and a live page, and that gap is full of fiddly work: matching the template, writing the schema, wiring the URL, adding the links, running the deploy. This skill does all of it in one pass. A draft becomes a published page.
The first time you run it, the skill interviews you and wires into where your files live, your house template, your deploy method, your author line, and your image convention. Every run after that just works.
It copies the head, styles, layout, and closing block from a post you already published, so a new page matches the rest of your blog exactly. Readers see one consistent site.
Every page ships with BlogPosting, Article, and FAQPage. The FAQPage is built only from the real question headings in the post, so search engines and answer engines read it cleanly.
The page serves at an extensionless URL with a canonical tag that matches. Your links stay tidy and your posts stay easy to share.
Outbound links to related posts and backlinks from older posts land in the same run, and one command deploys the whole thing live.
It clones your house template. On first run you point it at one post you already published, and it copies that post's head, style block, layout, navigation, footer, and closing call to action word for word. When it builds a new post, only the content and the metadata change, so the page matches every other post on your site down to the spacing. You get a consistent blog without touching the design each time.
Three JSON-LD blocks go on every page: BlogPosting, Article, and FAQPage. The FAQPage is built only from the real question headings inside your post, so each question maps to a concise answer drawn from that section. A closing call to action heading stays out of it. Search engines and answer engines read clean, accurate schema, which is how your post earns rich results and gets quoted.
Your post publishes at an extensionless URL with a matching canonical tag, so the link stays clean and easy to share. In the same run the skill weaves three to five outbound links from the new post into related posts you already have, and adds two to three backlinks from older posts pointing to the new one. Then one command builds any listing or sitemap and deploys the page live. Build, link, and ship happen in a single pass.