CHRISTINE The Blog Post Is Already Sitting in Your Notes
Notes To Blog reads the insights you've already captured and turns each one into a search-ready draft in your voice — matched to a real keyphrase, run through a publish gate, and marked used so the same note never becomes two posts.
← 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: notes-to-blog description: Turn notes and insights you have already captured into a sourced, search-ready blog draft. Because your notes are already extracted, this skill skips the extraction step and writes fast, and it never turns the same note into a second post. On first run it interviews you to wire in where your notes live, your keyphrase list, your blog, and your voice, then runs your version every time after. Use whenever you say "notes to blog," "draft a post from my notes," "turn this insight into a blog post," or point it at your saved notes and want a post. --- # Notes to Blog: Captured Notes Into Search-Ready Posts Turn a note you already captured into a finished blog draft that answers a real search question in your voice. Because the thinking is already extracted, this skill goes straight to writing. It writes every draft against a validated keyphrase, holds it to a publish-ready quality gate, and marks each note used so nothing gets posted twice. ## 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 captured notes and insights live? (A Notion database, an Obsidian vault, a notes app, a Google Doc, a folder, or notes you paste.) This is where I read your source material. 2. Do you keep a validated list of keyphrases or topics you want to rank for, and where does it live? If yes, I write each draft against a phrase from that list. If no, I name the search question each note answers and flag it for you to validate. 3. Where does your blog live and how does it publish? (WordPress, Ghost, Webflow, a static site, or a drafts folder.) This tells me the format to hand back and where drafts should land. 4. Whose voice should the draft be written in, and are there any words to avoid? This keeps every post on-brand and safe to publish. 5. Where should finished drafts land for your review? (A drafts database, a doc, a folder, or back to you in the chat.) Everything lands here for you first, so nothing publishes on its own. Save the answers as a CONFIG block in this file. If I ever say "redesign notes to blog," run this interview again. ## Input - A single captured note or insight from wherever you keep them - A batch: "draft posts from my new notes" (I pull every note marked ready and not yet turned into a post) - A note you paste directly ## What Makes This Skill Different Your notes are already captured and cleaned up, so the gold is extracted before I ever run. I skip the extraction pass that a raw transcript needs and move straight to writing. I also track what I have already turned into a post, so one note produces one post and stays out of the queue after. ## Workflow ### Step 1: Read the Notes and Filter Pull the eligible notes from where you keep them. A note is eligible when it is marked ready and has not already been turned into a post. Skip anything flagged as used. This dedup step is non-negotiable. It is what keeps the same insight from becoming two posts. ### Step 2: Match a Keyphrase Read the note. Find the one or two strongest teaching moments in it. Match each against your keyphrase list. - A match means the note can fully answer the keyphrase in the keyphrase's own words. If the note is only adjacent, do not force it. Pick the next ranked phrase or hold the note. - If the note has a strong through-line but no phrase on your list fits, name the search question it actually answers, log it as a proposal for you to validate, and write the draft against that proposed phrase, held for review. - Before writing, check that a post on this topic does not already exist on your blog. If it does, skip and note it. ### Step 3: Write the Draft Build the post from the note. Structure: 1. Title (H1) using the keyphrase. 2. A short summary up top, three to four bullets. 3. Intro that opens with the reader's question in the keyphrase's words. The reader knows within two sentences what this post answers. Your story enters in paragraph two as the proof. 4. Five to seven headings, each a real search-form question someone would type into a search engine. Every heading answer pulls from the note with real moments. 5. Actionable steps the reader can take. 6. A strong close. Source grounding: the draft carries at least three real moments from the note. Never invent a moment. If a section cannot be sourced from the note, flag it and write it thin for your review. Keyphrase Contract: the exact keyphrase appears in the H1, the first 100 words, at least two headings, and naturally through the body. If the draft cannot honestly do this, the match was wrong, so return to Step 2. Internal links: add three to five inline links to posts already live on your blog. Confirm each URL is live before you link it. Keep every link inline where the topic connects. ### Step 4: Polish One clean revision pass. Separate spoken rhythm from written rhythm. Give each idea room. Cut filler words. Title-case headings, sentence-case body. Tighten the close. One voice check against the voice you set up. ### Step 5: Run the Publish Gate Before the draft lands, run every check: 1. Keyphrase Contract met. 2. Intro opens with the reader's question, story is the proof in paragraph two. 3. The post uses the keyphrase's literal vocabulary throughout. 4. Every heading is a real search question, and the keyphrase or a close variant appears in at least two of them. 5. Three to five live internal links present. 6. Voice holds and none of the banned words, semicolons, or em dashes appear. Pass every check, mark it Ready to Publish. Miss one, mark it Draft and name what it missed. A draft that missed a check is never marked Ready to Publish. ### Step 6: Mark the Note Used After the draft is written, flag the source note as turned into a post so it never gets drafted again. Leave the note itself in place for your reference and future ideas. ### Step 7: Hand It Back Save the finished draft to your review destination with its status set. Give me a short receipt: the post title, the keyphrase, how many notes became posts, how many were held, and where the drafts landed. Every draft waits for you. ## Voice and Tone Write in the voice you set up in first run. Direct, clear, specific, written 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, no starting an idea through negation. ## Hard Rules - No note means no draft. Every post traces to real captured material. - The same note becomes one post and only one. The used flag is law. - A draft that missed a gate check is never marked Ready to Publish. - A partial keyphrase match gets held for a better fit. - Every quote traces to the note. Invented moments are banned. - Every draft lands at your review first. Nothing publishes on its own.
From then on, just point it at your saved notes and say "Notes to blog."
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 finished draft. Every part accounted for.
Run Notes To Blog on a captured note and you get back a complete draft built to be found in search — not a rough outline. This is the real structure of every post it hands you:
1 · A Title Built on the Keyphrase
The H1 carries the exact phrase your reader is searching — the same words they'd type into a search engine.
2 · A Short Summary Up Top
Three to four bullets before the post even starts, so a skimmer gets the answer and a reader wants the rest.
3 · An Intro That Opens With the Reader's Question
Within two sentences, the reader knows exactly what this post answers. Your story enters in paragraph two — as the proof, not the opener.
4 · Five to Seven Search-Question Headings
Every heading is a real question someone would actually type — and every answer pulls real moments from your note.
5 · Actionable Steps and a Strong Close
The reader leaves with something to do, not just something to think about — and the post ends on purpose instead of trailing off.
6 · Three to Five Live Internal Links
Inline links to posts already on your blog, woven in where the topic connects — every URL confirmed live before it's linked.
7 · A Status and a Receipt
Every draft is marked Ready to Publish or Draft — and if it's Draft, the skill names exactly which check it missed. You also get a short receipt: the post title, the keyphrase, how many notes became posts, how many were held, and where everything landed.
And if the fit isn't right?
Notes To Blog never forces it. If a note only sort-of matches a keyphrase, the note gets held for a better fit instead of stretched thin. If a post on the topic already exists on your blog, it skips and tells you. And a draft that misses even one publish-gate check is never marked Ready to Publish. Every draft waits at your review — nothing publishes on its own.
Keep stacking: pairs beautifully with Field Notes
Field Notes captures what you learned in a session as a clean, stackable reference card — Notes To Blog is how those captured insights graduate into published posts.
Get Field Notes →Because the thinking is already done.
You already did the hard part when you captured the note. Notes To Blog exists so the distance between 'I wrote that down' and 'I published that' stops being measured in months.
It skips the step you already did
Raw transcripts need an extraction pass to find the gold. Your notes are the gold — already captured and cleaned up — so this skill goes straight to writing. That's why it's fast.
The used flag means no accidental reruns
Every note that becomes a post gets marked used, and used notes never enter the queue again. One note, one post — so your blog never quietly repeats itself.
The Keyphrase Contract keeps every post honest
The exact keyphrase has to appear in the title, the first 100 words, and at least two headings — naturally. If a draft can't honestly do that, the match was wrong, and the skill goes back and picks a better one.
Real moments only, or it says so
Every draft carries at least three real moments from your note, and invented ones are banned. If a section can't be sourced, it's written thin and flagged for your review — never padded to look finished.
It's wired to your world on the first run
The first time you run it, the skill interviews you: where your notes live, your keyphrase list, your blog, your voice, and where drafts should land. It saves your answers and runs your version every time after.