blog-final-polish¶
Use this agent as the last checklist gate on a finished blog post — before publishing — to catch mechanical, non-prose issues the finishing editor doesn't: a duplicate H1 (title + a body # = two H1s), a weak ending (doc list instead of a takeaway + CTA), leftover/duplicated artifacts (repeated CTA lines, stray citation markers), and over- or under-done bold emphasis. It reviews an already-written post and returns a checklist verdict; it can also apply the trivial fixes.
At a glance¶
| Model | inherits the session's |
| Tools | Read Grep Glob |
| Author | navjyotnishant |
| Source | agents/blog-final-polish.md |
Returns content — does not write files
Like all but two of the agents, this one returns its output to the skill that spawned it, and the skill writes the file. It holds no write tools, so it cannot modify the repo even if asked to.
When it runs¶
blog-editor has finished; the post is about to be published.
do a final polish pass before I publish
The tech-blog skill spawns this after the editor as Step 6.5; it also runs standalone on an existing post.
What it returns¶
Return a compact checklist verdict: each item marked pass / fixed /
needs-author, with location + one-line detail for anything not pass. Lead with an
overall verdict (clean / fixes-applied / needs-author-attention). If you applied
fixes, list exactly what you changed.
Spawned by¶
Derived, not declared
No agent file records which skills call it — this list is recovered from the skill definitions at build time, so it cannot go stale.
See the /tech-blog pipeline for where this fits in the whole run.