explaingit

unclejobs-ai/blog-posting-auto

31ShellAudience · writerComplexity · 2/5ActiveLicenseSetup · moderate

TLDR

A Korean-language blog pipeline on Claude Code that chains six agents from research and fact-checking through writing and posts the result as a Notion Draft.

Mindmap

mindmap
  root((blog-posting-auto))
    Inputs
      Topic line
      Notion database ID
      Style rules
    Outputs
      Notion draft page
      Verified claims file
      Article markdown
    Use Cases
      Korean blog drafting
      Fact checked posts
      Notion publishing
      Multi agent writing
    Tech Stack
      Shell
      Claude Code
      Notion MCP
      Haiku
      Sonnet

Things people build with this

USE CASE 1

Draft Korean SEO blog posts with a built-in fact-checking step

USE CASE 2

Push generated posts into a Notion database as drafts for human review

USE CASE 3

Swap the Korean style rules for English or technical writing presets

USE CASE 4

Reuse the six-agent pipeline pattern for a different writing domain

Tech stack

ShellClaudeCodeNotionMCPHaikuSonnetOpus

Getting it running

Difficulty · moderate Time to first run · 30min

You need Claude Code installed, the Notion MCP connector configured globally, and a target Notion database before any slash command will publish.

MIT license, so you can use, modify, and ship it commercially as long as you keep the copyright notice.

In plain English

blog-posting-auto is a Korean-language blog writing pipeline built on top of Claude Code, the command-line coding agent. You give it a single topic line, and a chain of six small agents takes over: one researches the topic, one fact-checks what the researcher found, one plans the article, one writes the draft, one reviews and polishes it, and the last one pushes the result into a Notion database as a Draft page. The author says the part that sets this apart from other blog automations is the fact-checker step. The researcher gathers raw claims, and the fact-checker re-visits the original source URLs to see if each claim really holds up. Only claims that pass survive into a verified file, and the writer is only allowed to read that verified file. The aim is to stop hallucinations and fake first-person stories from sneaking into the final post. To run it you need Claude Code installed, the Notion connector set up as a global MCP server, and one Notion database to drop posts into. Setup is a git clone, a copy of the example env file, and filling in the Notion parent page ID and database ID. Then from inside a Claude Code session you call a slash command like /blog-pipeline followed by your topic. The pipeline assigns different Claude models to different jobs, with the cheaper Haiku model for routine search and posting calls, Sonnet for fact-checking, planning, and writing, and Opus for the final review. Style rules, banned phrases, and a checklist live in a separate folder so you can swap them out for English or technical writing. Publishing to Notion always asks for your explicit OK first.

Copy-paste prompts

Prompt 1
Explain the role of each of the six agents in blog-posting-auto and which Claude model runs each one
Prompt 2
Show the exact files I need to edit to switch blog-posting-auto from Korean style rules to English ones
Prompt 3
Walk me through how the fact-checker reads source URLs again and writes only verified claims to disk
Prompt 4
Write a /blog-pipeline command invocation that posts a draft about Notion MCP setup
Prompt 5
Modify blog-posting-auto so the final agent posts to Ghost instead of Notion
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.