skills/content/blog-post/SKILL.md
Use this skill when the user says 'write blog post', 'blog post about', 'write article', 'create blog', 'content for blog', 'write post', or is creating long-form written content for a blog or publication. Do NOT use for landing page copy, email sequences, or social media posts.
npx skillsauth add cwinvestments/memstack memstack-content-blog-postInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Produces a complete, publish-ready blog post with SEO metadata, structured sections, readability optimization, and internal linking suggestions.
When this skill activates, output:
✍️ Blog Post — Gathering topic and audience details...
Then execute the protocol below.
| Context | Status | |---------|--------| | User says "write blog post" or "blog post about" | ACTIVE | | User says "write article" or "create blog" or "write post" | ACTIVE | | Creating long-form content for a website or publication | ACTIVE | | Writing landing page copy (short-form, conversion-focused) | DORMANT — use landing-page-copy | | Writing email content | DORMANT — use email-sequence | | Writing social media posts | DORMANT |
| Trap | Reality Check | |------|---------------| | "Write about everything related to the topic" | Focus on one angle. Broad posts rank for nothing. Narrow posts rank for one keyword. | | "The intro should provide context" | The intro should hook. Context bores. Open with a bold claim, stat, or question. | | "Longer is better for SEO" | Comprehensive beats long. 1,500 focused words outrank 3,000 padded words. | | "Stuff the keyword everywhere" | Use the keyword naturally 3-5 times. Search engines penalize stuffing. Readers hate it. | | "Anyone who finds it will read it" | You have 3 seconds. If the title and intro don't hook them, the rest doesn't matter. |
If the user hasn't provided details, ask:
I need a few details for the blog post:
- Topic — what's this post about?
- Target audience — who are you writing for? (developers, business owners, beginners, etc.)
- Target keyword — what search term should this rank for?
- Tone — casual/conversational, professional, technical, inspirational?
- Desired length — short (800 words), standard (1,200-1,500), long-form (2,000+)?
If the user provides partial info, infer what you can and ask only for what's missing.
Before writing, build a structured outline:
Outline template:
## Outline
**Angle:** [What makes this post different]
**Target keyword:** [primary keyword]
**Secondary keywords:** [2-3 related terms]
1. Hook intro — [opening strategy: bold claim / stat / question / story]
2. [Section H2] — [key point + supporting evidence]
3. [Section H2] — [key point + supporting evidence]
4. [Section H2] — [key point + supporting evidence]
5. [Section H2] — [key point + counterargument addressed]
6. Actionable takeaways — [summary of what to do next]
7. CTA conclusion — [what you want the reader to do]
Present the outline for user approval before writing the full post.
**Title:** [60 characters max — include target keyword, power word, specific benefit]
**Meta description:** [155 characters max — summarize the value, include keyword, end with implicit CTA]
**URL slug:** [target-keyword-in-slug — lowercase, hyphens, no filler words]
Title formula options:
Title rules:
Meta description rules:
The intro must accomplish three things in three paragraphs (or fewer):
[Hook sentence — bold claim or surprising stat]
[1-2 sentences connecting to reader's situation]
[Promise: "In this post, you'll learn..." or "Here's exactly how to..."]
Do NOT:
Each section follows this structure:
## [H2: Keyword-rich, benefit-oriented heading]
[Opening sentence that states the section's key point]
[Supporting evidence: stat, example, case study, or expert quote]
[Practical explanation — how this applies to the reader]
[Specific example or actionable step]
> [Optional: pull quote or callout box with key insight]
[Transition sentence leading to the next section]
Body writing rules:
| Metric | Target | Why | |--------|--------|-----| | Flesch-Kincaid Grade | 8 or below | Accessible to 80% of readers | | Sentence length | Average 15-20 words | Longer sentences lose readers | | Paragraph length | Max 3-4 sentences | Short paragraphs feel faster | | Passive voice | Below 10% | Active voice is direct and clear | | Adverb usage | Minimal | "Ran quickly" loses to "sprinted" | | Jargon | Define or avoid | Unless audience is technical |
## [Takeaway heading — not "Conclusion"]
[Summarize the 3 most important points in 2-3 sentences]
[Restate the benefit: what the reader can now do]
**[CTA — what you want them to do next:]**
- Subscribe/newsletter: "Get [topic] tips weekly — subscribe below"
- Product: "Try [product] free — [link]"
- Share: "Found this useful? Share it with your team"
- Next post: "Read next: [related post title]"
- Comment: "What's your experience with [topic]? Drop a comment"
## Internal Linking Opportunities
| Anchor Text | Link To | Location in Post |
|-------------|---------|-----------------|
| "[related concept]" | /blog/[related-post-slug] | Section 2, paragraph 3 |
| "[tool or feature mentioned]" | /features/[feature-page] | Section 4, paragraph 1 |
| "[previous post reference]" | /blog/[previous-post-slug] | Conclusion |
**External links (for credibility):**
| Anchor Text | Link To | Rationale |
|-------------|---------|-----------|
| "[stat source]" | [authoritative source URL] | Backs up claim in Section 1 |
| "[expert quote source]" | [source URL] | Attribution |
Linking rules:
## Image Placements
| Position | Image Concept | Alt Text | Purpose |
|----------|--------------|----------|---------|
| After intro | [Relevant hero image or infographic] | "[Descriptive alt text with keyword]" | Visual hook |
| Section 2 | [Screenshot, diagram, or example] | "[Descriptive alt text]" | Illustrate concept |
| Section 4 | [Chart, comparison, or data visualization] | "[Descriptive alt text]" | Support data point |
| Before CTA | [Product shot or action image] | "[Descriptive alt text]" | Reinforce CTA |
Image rules:
Output the complete blog post in clean markdown:
---
title: "[SEO title]"
description: "[Meta description]"
date: YYYY-MM-DD
author: "[Author]"
tags: ["keyword1", "keyword2", "keyword3"]
image: "/blog/[slug]/hero.jpg"
---
# [Post Title]
[Full post content with H2 sections, formatting, links]
Output summary:
✍️ Blog Post — Complete
Title: [title] ([character count] chars)
Meta description: [description] ([character count] chars)
Target keyword: [keyword]
Word count: [count]
Sections: [count] H2s, [count] H3s
Reading time: ~[count] minutes
Readability: Flesch-Kincaid Grade [score]
SEO checklist:
✅ Keyword in title (first 40 chars)
✅ Keyword in meta description
✅ Keyword in 2+ H2 headings
✅ Keyword in first 100 words
✅ Internal links: [count]
✅ External links: [count]
✅ Image alt text with keyword: [count]
Next steps:
1. Review and add personal voice/anecdotes
2. Source or create images for suggested placements
3. Add internal links to existing content
4. Publish and submit to Google Search Console
tools
Use when the user says 'save diary', 'log session', 'wrapping up', or at end of a productive session.
tools
Use when the user says 'submit to marketplace', 'publish my skill', 'share this skill', 'list on marketplace', 'submit plugin', 'publish to community', or needs to submit a skill or plugin to a community marketplace via PR. Do NOT use for building skills or writing plugin code.
development
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
development
Use when the user says 'teach me', 'explain as you go', 'mentor mode', 'walk me through', 'help me learn', 'explain why', 'learning mode', or wants real-time plain language narration of decisions and tradeoffs while building. Do NOT use for code review or debugging.