| name | marketing-content-blog-post |
| description | Write an 800-1500 word B2B blog post in Markdown from a content idea. Use when content_type is blog_post. Applies stage-specific frameworks and Exa reference articles. Output to workspace/marketing/content/drafts/blog/. For LinkedIn or X use marketing-content-linkedin-post or marketing-content-x-post instead. |
| license | MIT |
| metadata | {"version":"1.0.0","category":"marketing"} |
Blog Post Generation
Long-form draft pipeline for a content idea of type blog_post.
When to Use
- Idea file has
content_type: blog_post
- User asks to write/expand a blog idea
Prerequisites
- Content idea:
workspace/marketing/content/ideas/blog_post--{buying_stage}--{slug}.md
- Firm, service, ICP, persona context in workspace
- Current agent/LLM session
- Optional: Exa reference notes via
tool-exa for market-informed long-form drafts
Prompt layering (order matters)
- Base writer — style, storytelling, anti-AI-slop (no length)
- Quality layer — universal quality + buying-mode tone
- Blog format layer — authoritative length/structure →
references/format-requirements.md
Optional: workspace/firm/content-guidelines/blog-post.md if exists (company overrides).
Follow the shared draft gate and writing quality rules in docs/content-generation.md.
Research
Optional Exa reference articles: search 5 results on idea title via tool-exa;
include highlights for benchmarking. Do not plagiarize.
Skip this step when the user wants a quick internal-context draft.
User prompt template
Write a Blog Post based on this content idea. Follow FORMAT REQUIREMENTS exactly.
=== CONTENT IDEA ===
Title: {title}
Description: {description}
Buying Stage: {stage label}
Buyer question: {buyer_question}
Unique angle: {unique_angle}
Proof source: {proof_source}
Next action: {next_action}
Research mode: {research_mode}
Target keyword: {if any}
=== CONTEXT ===
{company, service, ICP, persona from workspace}
=== REFERENCE ARTICLES ===
{exa results or none}
Requirements:
- 800-1500 words, Markdown H2/H3
- Match buying stage framework (see format requirements)
- Brand voice from firm profile
- Hook opening — no generic intro
- Use proof only from workspace, idea proof_source, or reference notes
- CTA aligned to buying stage
- Language: {language}
Return JSON: { "title": "...", "body": "markdown..." }
Output
workspace/marketing/content/drafts/blog/{slug}.md
Frontmatter: idea, content_type, buying_stage, service, icp, persona,
target_keyword, generated_at.
Run scripts/validate-content-draft.sh {output}. Update idea frontmatter to
status: generated after the draft validates.
Related Skills
marketing-content-ideas (upstream) | other marketing-content-* for different types
