Skills / Blog post
Blog post
Write and publish one blog post on something the person knows. Their words, workshopped, live at a URL by the end of the sitting. Use when they say "I want to start a blog", "help me write a post", or have a project worth writing up.
Use this skill. Nothing to install.
Don't have an agent? · Raw file: skills/blog-post.md
Watch the first two minutes
This is how a session goes, including the moment the topic shows up. Click through it.
Scripted example of a real session.
Have nothing to write about?
You have things you've done; those are the only posts worth writing anyway. The skill steers you away from topic essays about things you've only read about, because the internet already has those, written by people who were there. It digs for what you built, broke, or figured out. If the honest answer is "nothing yet", do a small project first and the post writes itself as a build log.
What you end up with
A post that is live at a URL by the end of the sitting. Here is what the top of a good first post looks like.
- The title is plain and searchable. It names the exact problem, so the next person with the freeze can find it. Clever wordplay would rank for nothing.
- It starts where it gets interesting. No "In this post I will explore". The first sentence is a confession with information in it, and it happened.
- The real error message is in the post. Checkable details are how a post earns trust, and yours are the only ones you can supply. That exact string is what search engines and stuck strangers match on.
Questions people actually ask
Is this free?
The skill is free, no account, no catch. The agent you paste it into may or may not be: Gemini has the widest free tier, Copilot's free tier is enough to try it, ChatGPT and Claude free plans can also run it in a chat. Publishing is free too: Bearblog, GitHub Pages, and dev.to all have honest free tiers.
Will it sound like AI wrote my post?
Not if you follow the skill, because you draft every sentence and the edit pass hunts the machine tells: rhythmic triple lists, "it's not just X, it's Y" constructions, words like "truly" and "seamless". The agent supplies structure and questions; the words are yours, which is the only reliable way to not sound like a machine.
Does the agent write the post for me?
No. It can type the outline with you, because that's scaffolding. The prose you draft yourself, fast and ugly, section by section. If you stall, it asks you to tell it the section in chat, then has you write down what you said.
Where does the post actually live?
If you have a personal site, there. Otherwise the skill helps you pick a free home: Bearblog, GitHub Pages with plain HTML, or dev.to for technical posts. It steers you away from anything demanding a paywall or a phone number. Either way you leave with a URL.
What if nobody reads it?
The first post's job is to exist at a link you can put in a bio, a resume, or a reply. The skill has you send it to one real person who would care. Readers beyond that come from writing the next one; one is a post, three is a blog.
Where to go from here
Post is live? The natural next moves:
Want the blog on your own domain? Build the home for it:
Ideas to use it on
- The explainer classmates keep asking for — You are the one people text before the test: the unit circle, balancing equations, essay structure, whichever it is for you.
- Cover your own team's game — One game your team played, written up like sports journalism: the turning point, quotes collected on the sideline, the box score.
- What my first job taught me — A post about your part-time job that could only have been written by someone who worked it: the customer stories, the boredom, the thing your manager said that stuck.
- Write up the thing you fixed — You fixed something: a bike, a lamp, a laptop, a group project that was sinking.
- Explain your niche to outsiders — The hobby your family does not get, explained so they finally do.
- Every book this year, reviewed honestly — Every book you finished this year, reviewed in two paragraphs each: the assigned ones you hated, the embarrassing one you loved, all of them.
Curious? Read the full skill — the exact instructions your agent gets
--- name: blog-post category: write description: Write and publish one blog post on something the person knows. Their words, workshopped, live at a URL by the end of the sitting. Use when they say "I want to start a blog", "help me write a post", or have a project worth writing up. --- # blog-post Help someone publish their first blog post, or their first good one. They write every sentence; you supply structure, questions, and honest reactions. The post ships today — a draft that sits in a folder teaches nothing. ## Find the post they can actually write The only posts worth writing are ones where they know something the reader does not. Ask what they have done lately that took real effort: a project built, a problem debugged, a thing learned the hard way, a process figured out. "What I learned building X" and "How I fixed Y" are honest first posts. Talk them out of topic essays on things they have only read about — the internet has those already, written by people who were there. Get the one-sentence version before any drafting: "This post tells _who_ _what_." If they cannot fill that in, keep talking. ## Draft at speed 1. Outline together: 4–6 beats, each a plain sentence of what that section says. This scaffolding you may type — it is structure, not prose. 2. They draft each section in their own words, fast, ugly is fine. If they stall, ask them to tell you the section in chat, then write down what they said. Do not draft it for them. 3. Specifics in: the actual error message, the actual number, the actual link, the actual screenshot. Posts earn trust through checkable details, and theirs are the only ones they can supply. 4. First line check: would a stranger keep reading after sentence one? "In this post I will..." is a delete. Start where it gets interesting. ## Edit pass One pass, together, out loud. Cut every sentence that adds no information. Flag the machine-writing tells — rhythmic triple lists, "it's not just X, it's Y" constructions, words like truly and seamless — and have them rewrite in the words they would use telling a friend. Titles: plain and searchable beats clever. "How I built a bus tracker with no budget" outranks wordplay. ## Publish now Publishing is part of this skill, not a follow-up. - If they have a personal site (see build-website), the post goes there — their domain, their archive. - Otherwise free and fine: Bearblog, GitHub Pages with plain HTML or a simple generator, or dev.to for technical posts. Avoid anything that demands a paywall or a phone number. - Ship checklist: title, date, their name, working links, readable on a phone. ## Done - The post is live at a URL they can put in a bio or resume. - Every claim in it is true and every example is theirs. - They send the link to one real person who would care. - Ask what the next post would be — one is a post, three is a blog. Write the next title down where they will see it.