← ClaudeAtlas

publish-blog-content-to-nextjs-repolisted

Ships refreshed or net-new blog content straight into a client's Next.js / Vercel repo and gets it live, end to end, with no terminal driving from the user. Covers repo recon, learning the site's actual Markdown renderer subset, an in-place apply script, four verification gates, the PR, the merge and the Vercel deploy, then the content tracker update. Use when asked to publish, push or deploy blog changes to a repo, update the posts on the live site yourself, open the PR for a content refresh, get a refresh deployed, or when a content refresh has drafts ready and needs to reach production.
savenjudesajen/seo-aeo-agent-skills-tools · ★ 0 · Web & Frontend · score 73
Install: claude install-skill savenjudesajen/seo-aeo-agent-skills-tools
# Publish blog content to a Next.js / Vercel repo Home page: [unilytics.ai/skills/publish-blog-content-to-nextjs-repo](https://unilytics.ai/skills/publish-blog-content-to-nextjs-repo/), the canonical source of this skill. Takes finished drafts and puts them on the live site. The drafts come from a writing or refresh workflow, checked against the brand's own writing guidelines if it has them; this skill is only the shipping half. **The governing rule: the site's renderer decides the content format, not you.** Most of the ways this task fails come from assuming the repo accepts HTML or full CommonMark. It usually does not. Learn the parser first, author to it, then prove it with the gates. **Second rule: the user should not have to drive a terminal.** The only steps that legitimately go back to them are the ones gated on credentials they hold. Everything else is yours. See `reference/autonomy-boundary.md`. ## Before you start 1. Load whatever earlier runs recorded for this client's repo (which file holds which slug, which git identity deploys, which team owns the deploy project), so you skip rediscovering it. 2. Confirm the drafts are final and verified as content. This skill does not re-check facts or sourcing; that belongs to the writing or refresh step. Do a quick readiness check per draft anyway: it has a final title, slug, meta title and meta description (in the draft or its publishing notes); no placeholder text (`TK`, `[insert ...]`, `lorem`), editor co