🇺🇸English

Blog Post

Research, draft, and polish publication-ready blog posts.

Workflow

Blog post progress:
- [ ] Step 1: Clarify topic and format
- [ ] Step 2: Research and gather sources
- [ ] Step 3: Extract key insights and outline
- [ ] Step 4: Write the post
- [ ] Step 5: SEO and polish
- [ ] Step 6: Validate quality

Step 1: Clarify topic and format

Determine the post type before writing. Ask the user if unclear:

Step 2: Research and gather sources

Read files, fetch URLs, or accept pasted text. If the user provides a topic without sources, research the topic before writing. Read every source completely before outlining.

Accept messy input — scattered thoughts, bullet points, brain dumps, random observations. The mess is the input; structure is the output.

Step 3: Extract key insights and outline

• Identify the most surprising, counter-intuitive, or impactful takeaways.
• Rank insights by reader value — lead with the strongest.
• Select 2-4 powerful quotes for blockquotes (only the best).
• Find a relatable problem or curiosity gap to anchor the introduction.
• Check for narrative potential: is there a journey from one understanding to another?

Create a section outline before drafting. Each section should have a clear purpose.

Step 4: Write the post

Load the matching template from references/format-templates.md and follow its structure. Only load the template for the chosen format — not all four.

Step 5: SEO and polish

• Title : under 60 characters, include the main keyword.
• Meta description : 150-160 characters summarizing the post's value.
• Keyword placement : naturally in the title, first paragraph, and 2-4 times throughout.
• Headers : descriptive H2/H3 tags that work as standalone scan points.
• Internal links : suggest 2-3 related links if the user has other content.

Step 6: Validate quality

Before finalizing, verify:
- [ ] Hook grabs attention in the first 1-2 sentences
- [ ] Headline is specific and delivers on its promise
- [ ] Every paragraph is 2-4 sentences maximum
- [ ] Each section has analysis or insight, not just summary
- [ ] Blockquotes are limited to 2-4 total
- [ ] Conclusion looks forward with a question, CTA, or provocative takeaway
- [ ] Tone is conversational throughout — no academic language
- [ ] Title is under 60 characters with the main keyword
- [ ] Post includes a meta description (150-160 chars)
- [ ] Markdown renders correctly (headings, blockquotes, bold, code)

Blog-specific voice

• Write to a smart friend, not a committee. Authenticity beats authority.
• Bold key phrases for scannability — readers skim before they read.
• Show, don't tell: specific examples with real details beat vague claims.
• Admit uncertainty when genuine. Never bluff expertise.

Headline patterns

• Number + insight : "7 Things [Sources] Reveal About [Topic]"
• Surprising tension : "Why [Common Belief] Gets [Topic] Wrong"
• How-to framing : "How to [Achieve Outcome] with [Method]"
• Question format : "What If [Provocative Reframe]?"

Under 60 characters for SEO. Sentence case, no trailing period. Must deliver on its promise.

Anti-patterns

• Generic headlines ("Interesting Findings About X").
• Conclusions that just summarize what was already said.
• Clickbait headlines the content does not deliver on.
• Blockquoting every source instead of choosing the 2-4 most powerful.
• Skipping research and writing from assumptions.

Skill handoffs

Weekly Installs

52

Repository

mblode/agent-skills

GitHub Stars

20

First Seen

Feb 22, 2026

Security Audits

Gen Agent Trust HubPassSocketPassSnykWarn

Installed on

opencode51

gemini-cli51

github-copilot51

codex51

cursor51

amp50