Sign up
← all tools

cc-skill:blog-post-writer

Claude Code skill · anthropic · active

0
last 30 days
0 calls
0 of 30 days active
explain like I am new to this
what it does

Creates a complete, ready-to-publish blog post in markdown format. It structures the piece with a strong hook, clear sections, concrete examples, and a closing. The output goes straight into your blog editor or Medium.

who it is for

Founders, marketers, and subject matter experts who want to publish long-form thought leadership or educational content without hiring a writer.

when it fires

When you ask Claude to write a blog post, long-form article, or piece for Medium or Substack (as opposed to structured data for a CMS).

say something like
  • "Write a blog post about how to price consulting services for first-time consultants"
  • "Blog post for our SaaS on why most automation projects fail, audience is operations managers, medium length"
  • "Long-form article on the psychology of pricing decisions"
what you might get back
# Why Most Automation Projects Fail (And How to Pick the Right One). A lede with a specific story or number. Three to five H2 sections like 'The hidden cost of picking the wrong tool' and 'How to audit your current workflow before buying anything.' Each section is 2-3 paragraphs. A concrete example with real numbers or a script. A closing paragraph with a clear next step. All formatted in clean markdown ready to paste.
how to know it worked

You see a complete, skimmable blog post in markdown with a strong title, short paragraphs, clear H2 headings, and at least one concrete example or number. It feels like something you could publish today.

is this skill working for me
never used
cloud runs
0
0 deployments
local fires
0
Claude Code (optional)
posts published
0
from drafts
attributed
$0.00
signups + revenue
Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/blog-post-writer/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when generating long-form blog posts in markdown for direct publication on a blog, Medium, Substack, or company website. Triggers on "blog post", "write a blog about", "long-form article" (when output should be markdown, not JSON). Dif

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/blog-post-writer/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity
never used
2026-04-03today
cost model
unitincluded
capabilities
{
  "source": "global",
  "description": "Use this skill when generating long-form blog posts in markdown for direct publication on a blog, Medium, Substack, or company website. Triggers on \"blog post\", \"write a blog about\", \"long-form article\" (when output should be markdown, not JSON). Different from seo-article-writer (which outputs JSON for CMS ingestion)."
}
how it gets called
{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/blog-post-writer/SKILL.md"
}
This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.