Skip to content
Skill Authoring
Skill

/blog-post

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.

BOOST
From plugin
memstack
42587 skills2 commands4 hooks
Install
$ npx -y skills add cwinvestments/memstack --skill blog-post --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/blog-post

Context preview

The summary Claude sees to decide when to auto-load this skill.

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.

SKILL.md

blog-post.SKILL.md
name: memstack-content-blog-post
description: "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."
version: 1.0.0
license: "Proprietary, MemStack™ Pro by CW Affiliate Investments LLC. See LICENSE.txt"

✍️ Blog Post: Writing SEO-optimized blog post...

*Produces a complete, publish-ready blog post with SEO metadata, structured sections, readability optimization, and internal linking suggestions.*

Activation

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 |

Anti-patterns

| 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. |

Protocol

Step 1: Gather Topic Details

If the user hasn't provided details, ask:

> I need a few details for the blog post: > 1. **Topic**: what's this post about? > 2. **Target audience**: who are you writing for? (developers, business owners, beginners, etc.) > 3. **Target keyword**: what search term should this rank for? > 4. **Tone**: casual/conversational, professional, technical, inspirational? > 5. **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.

Step 2: Research and Outline

Before writing, build a structured outline:

1. **Identify 3-5 key points** the post must cover 2. **Find supporting data**: statistics, examples, or case studies that strengthen each point 3. **Note counterarguments**: addressing objections builds credibility 4. **Determine the unique angle**: what perspective makes this post different from the top 10 results?

**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.

Step 3: Write SEO Metadata

**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:**

  • Number + Adjective + Keyword + Promise: "7 Proven Ways to [Keyword] Without [Pain Point]"
  • How to + Keyword + Benefit: "How to [Keyword]: A Step-by-Step Guide for [Audience]"
  • Question format: "Why Does [Keyword] Matter? [Provocative Answer]"
  • Contrarian: "[Common Belief] Is Wrong. Here's What [Keyword] Actually Means"

**Title rules:**

  • Include target keyword within the first 40 characters
  • Use a power word (proven, essential, complete, ultimate, simple)
  • Promise a specific outcome (not vague "improve")
  • Max 60 characters to avoid Google truncation

**Meta description rules:**

  • Include target keyword naturally
  • Summarize the unique value of this post
  • Create curiosity or promise a benefit
  • Max 155 characters to avoid truncation

Step 4: Write the Post

Intro (100-150 words)

The intro must accomplish three things in three paragraphs (or fewer):

1. **Hook**: bold claim, surprising stat, relatable pain point, or provocative question 2. **Relevance**: why this matters to the reader right now 3. **Promise**: what they'll know or be able to do after reading

[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:**

  • Start with "In today's fast-paced world..." or any throat-clearing
  • Define the obvious ("What is marketing?")
  • Summarize the entire post upfront (that's what the outline is for)

Body Sections (3-5 H2 sections)

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:**

  • Paragraphs: max 3-4 sentences each (walls of text kill readability)
  • Sentences: vary length, mix short punchy sentences with longer explanatory ones
  • Use H
Read more
Ships withmemstack

The structured skill framework for Claude Code: 131 professional skills for deployment, security, databases, content, marketing, and more. Skills activate automatically when you need them. Say "deploy this to Railway" and the right skill loads on demand.

Get the whole plugin

Other skills on memstack.