CHRISTINE Catch the Missing Piece Before Your Readers Do
Publish-Ready Check runs a finished post through every required element — nine checks, one clean verdict — then packages exactly what your publisher needs to take it live. Anything missing gets named plainly, and the package holds until it's fixed.
← 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: publish-ready description: Verify a finished post has every required part before it ships, then package the publishing handoff and update your tracker. On first run the skill interviews you to wire in where your drafts live, your required elements, your closing call to action, and how you publish, then runs your version every time after. Use whenever you say "publish-ready check," "is this post ready," "check this post," "run the readiness check," or drop a finished draft and want to know if it is ready to ship. --- # Publish-Ready Check: Your Pre-Publish Quality Gate Run a finished post through one readiness check before it goes out. The skill verifies every required part is present, flags exactly what is missing, packages the handoff your publisher expects, and readies the update for your tracker. The work is checking and packaging. Building the page and deploying it live stay with your publisher. ## 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 finished drafts live? (A content tracker, a folder, a doc, a database, or pasted straight to you.) This is where I pull the post and its details from. 2. What are your required post elements? Name the parts every post of yours must carry before it ships. A strong default set: a title with your primary keyword, a TL;DR block, a keyphrase-rich intro, question-based H2 sections, outbound internal links in the body, actionable steps, a strong close, and a meta description. 3. What is your closing call to action? Name the one block every post ends with so I can confirm it is present. This is your standard close, the same on every post. 4. How do you publish, and what does your publisher expect in the handoff? (The tool you paste into, the file path shape, the URL shape, and any schema or social tags it needs.) This is the package I hand back. 5. What is your default OG image, and where do you track post status? This sets the image every post ships with and the place I update once a post goes live. If I ever say "redesign publish ready," run this interview again. ## Input - A finished draft from the place you named in setup (I pull it and its details) - A pasted draft plus its meta description - "Check my latest draft" (I find the most recent finished post in your tracker) ## Workflow ### Step 1: Pull the Post Get the full draft from the place you set up, or use the one you paste. Read the body, the meta description, the primary keyword, and the list of outbound internal links the creation step recorded. ### Step 2: Run the Readiness Checklist Confirm every required element is present. Check each one and mark it pass or flag: 1. Title (H1) carrying the primary keyword. 2. TL;DR block, three to four bullets. 3. Keyphrase-rich intro, with the story as evidence in the second paragraph. 4. Question-based H2 sections. 5. Outbound internal links in the body, matching the count the creation step recorded, live URLs only. 6. Actionable steps. 7. Strong close. 8. Closing call to action, your standard closing block, present and correct. 9. Meta description. Report the result as a clean pass-or-flag list. Name every flagged item plainly. **Hard rule:** If the outbound internal links are missing from the draft body, flag it and stop. The post is not ready. Do not package the handoff. Linking belongs to creation, and it never happens after publish. This one is a hard gate. Treat it as a full stop. For any other missing element, flag it and hold the package until it is fixed. Do not fix the content yourself. That belongs to your creation pipeline. Your job is to name what is missing. ### Step 3: Give the Verdict State it in one line: READY or HOLD. If READY, move to packaging. If HOLD, list the flagged items and stop. ### Step 4: Package the Handoff Once the post passes, build the package your publisher expects, using the handoff shape you set up. Include the file path shape, the clean URL shape, the meta description, the schema and social tags your publisher needs, the default OG image, and the closing call to action confirmed present. Hand this package back ready to paste into your publisher. You do not deploy it. Your publisher does. ### Step 5: Ready the Tracker Update Prepare the update for your tracker so it is ready the moment the post goes live: status set to published, the publish date, and the live URL. Apply it once you confirm the post is live. ## Internal Linking Design Two jobs, two owners, nothing after publish. - Outbound links, from the new post out to existing posts, belong to creation. They are written into the draft body before the post ever reaches this skill. - Inbound links, from existing posts to the new post, belong to publish. They land in the same deploy as the new post, handled by your publisher. This skill verifies the outbound links exist as part of the checklist and confirms the inbound-link instruction is in the handoff. It never adds outbound links itself, and there is no linking step after publish. The post is fully optimized the moment it goes live. ## What This Skill Does Not Do - Writing or editing post content stays with your creation pipeline. - Outbound links arrive in the draft already written, so the skill never adds them. - Building the page and the HTML belongs to your publisher. - Deploying and pushing live is your publisher's job. - After publish it only readies the tracker update. ## Voice and Tone Write direct, clear, and specific, to the reader as "you." 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 check, give a short receipt: the post, the verdict, the flagged items if any, and whether the handoff is packaged. If READY, remind me to apply the tracker update once the post is live.
From then on, just drop in a finished post and say "Is this post ready?"
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 verdict. Nothing left to wonder about.
Run Publish-Ready Check on a finished post and you get a complete answer — what passed, what got flagged, and what happens next. Here's what every check hands back:
1 · The Pass-or-Flag List
All nine required elements, checked one by one — the keyword in the title, the TL;DR block, the keyphrase-rich intro, question-based headings, internal links, actionable steps, the strong close, your closing call to action, and the meta description. Every flag named plainly.
2 · A One-Line Verdict
READY or HOLD. No 'pretty close,' no 'should be fine.' READY moves straight to packaging — HOLD lists the flagged items and stops right there.
3 · The Publishing Handoff Package
When a post passes, you get the package your publisher expects: the file path shape, the clean URL shape, the meta description, the schema and social tags, the default OG image, and your closing call to action confirmed present — ready to paste.
4 · The Tracker Update, Staged
The status, publish date, and live URL are prepared in advance, so the moment your post goes live, your tracker is one confirmation away from current.
5 · A Short Receipt
The post, the verdict, the flagged items if any, and whether the handoff is packaged — plus a reminder to apply the tracker update once the post is confirmed live.
One check can stop the whole train
If the internal links are missing from the draft body, the check stops cold — no package, no workaround. Linking belongs to the writing step and never happens after publish, so a post without its links simply isn't ready. And this skill won't quietly fix content, either: it names what's missing and hands it back. Checking and packaging is the whole job — and that's exactly what makes the verdict trustworthy.
Keep stacking: pairs beautifully with Blog Publisher
Publish-Ready Check proves a post is truly ready and packages the handoff — Blog Publisher is the one that takes that handoff, builds the real page, and ships it live.
Get Blog Publisher →Because 'it looks done' isn't a standard.
Every post that ever shipped with a missing meta description felt finished at the time. Publish-Ready Check replaces the feeling with a checklist — the same nine checks, in the same order, every single time.
A named list beats a once-over
Rereading a post catches typos. A checklist catches structure — the missing TL;DR, the absent call to action, the intro that never states the reader's question. Nine named elements, each marked pass or flag, so nothing rides on memory.
The verdict has no middle setting
READY or HOLD, in one line. A post can't limp across the finish at 80 percent, because HOLD stops the packaging entirely — and that protects the quality of everything you publish.
The links rule protects your post's future
Outbound links get written during creation, inbound links land at publish, and nothing gets bolted on afterward. That's why missing links are a full stop: the post should be fully optimized the moment it goes live, not eventually.
It refuses to grade its own homework
This skill doesn't write, doesn't edit, doesn't build the page, and doesn't deploy. A checker that also fixes things ends up approving its own work — keeping the jobs separate is what keeps the check honest.
Your setup defines 'ready'
On first run it interviews you: where your drafts live, your required elements, your closing call to action, and what your publisher needs in the handoff. The gate it holds every post to is the one you designed.