/tech-blog — orchestrator¶
Runs 9 agents. Runs a multi-agent pipeline (writer → fact-checker → reviewer → editor → optional poster), grounds every claim in the actual repo (the fact-checker BLOCKS on anything it can't verify), embeds architecture diagrams if present, writes the post to docs/blog/, and produces publish-ready Markdown + HTML. Posts via an MCP only if one is connected and you opt in.
The pipeline¶
What it runs, in order¶
| # | Agent | What it does |
|---|---|---|
| 1 | blog-writer |
Write the first draft of an expert-level technical blog post about a project, grounded in… |
| 2 | blog-fact-checker |
Verify every technical claim in a draft blog post against the actual repository — APIs… |
| 3 | blog-reviewer |
Critique a fact-checked technical blog draft for structure, clarity, technical depth… |
| 4 | blog-editor |
Produce the final, polished version of a technical blog post — applying the… |
| 5 | blog-final-polish |
Use this agent as the last checklist gate on a finished blog post — before publishing —… |
| 6 | blog-platform-lint |
Use this agent right before publishing a finished blog post to an external platform… |
| 7 | blog-poster |
Use this agent when the user has opted in to publishing a finished blog post to an… |
| 8 | social-post |
Draft promotional social copy (LinkedIn / X) for a PUBLISHED thing — a blog post, repo… |
| 9 | diagram-architect |
Turn a project's docs and code structure into an architecture diagram — it reads the repo… |
At a glance¶
| Class | authoring |
| Cost | a 6-agent pipeline (writer → fact-checker → reviewer → editor → final-polish → platform-lint), plus one extra writer+fact-checker round per fact-check retry (capped at 2, §C) |
| Skill page | /tech-blog |
| Source | skills/tech-blog/SKILL.md |