Can AI replace Skribra?

NOT REALLY · don't bother

price $19/moyou'd save $228/yrbuild time weekend for the writer, weeks for the approvalscategory 📈 seo & marketingreplaced by 0 peoplebuild unverified

The writing isn't the hard part · an agent will turn a keyword into a decent long-form article this afternoon, and the prompt below does exactly that. What you can't prompt your way past is permission. Publishing to WordPress is open to anyone with an application password, but every other destination is gatekept by the platform: Shopify wants your app through App Store review, Webflow wants a marketplace submission, Notion wants a public integration, Search Console wants verified OAuth scopes. That's someone else's review queue, measured in weeks, and no model clears it for you. The other half is that content only compounds if something keeps touching it · a generator ships posts and forgets them, and the value here is the unglamorous machinery that comes back to article 14 in week nine because its ranking slipped.

the prompt

Build me a single-article SEO writer that publishes to WordPress. Requirements:

- WordPress only, deliberately: it authenticates with an application password the
site owner generates alone, while Shopify or Webflow need a platform-approved
OAuth app; budget weeks of review before one post goes live elsewhere.
- Stack: one Node + TypeScript CLI, no web UI and no accounts, with SQLite via
better-sqlite3 to remember what's been written. Config in .env.
- Input: a target keyword plus a short site description. Output: one published post.
- Generate in explicit stages, persisting each stage's output to SQLite so a failed run
resumes instead of restarting: outline · section drafts · intro/conclusion · FAQ · title ·
meta description · slug.
- Aim for 1500-2500 words of specific prose. Ban the usual tells in the prompt: no 'in today's
fast-paced world', no 'delve', no section that just restates the one above it.
- Internal links: query the WordPress REST API for existing posts, pick the 3-5 genuinely
related ones, and link them inline with descriptive anchor text.
- One generated header image, uploaded to the media library and set as featured image.
- Emit JSON-LD Article plus FAQPage, and a real meta description rather than a truncated
first sentence.
- Publish via the REST API with an application password · draft by default, --publish to go live.
- Log every run's token cost to SQLite and print a per-article total, so the metered cost is
visible instead of arriving as a surprise.
- Out of scope, and these are the hard parts: keyword research, scheduling, any other CMS,
and post-publish monitoring or refresh. Pretending a one-shot build covers those would be
dishonest.

$ open in your agent (prompt prefilled, you press enter) or copy it raw

why people still pay

Two reasons, and neither is that the writing is difficult. First, the integrations aren't a coding problem · publishing to Shopify or Webflow means shipping an app through their review, and you can write perfect code and still be three weeks from a published article. Second, the DIY version has its own bill: every article is a stack of paid LLM calls and useful keyword data is a paid API, so this isn't a weekend versus a subscription, it's a weekend plus a metered cost versus a subscription. What's left after that is maintenance nobody enjoys owning · deciding what to write next, not writing the same thing twice, and going back to old posts when the numbers move.

what you lose

xpermission to publish anywhere but WordPress · Shopify sits behind App Store review, Webflow behind a marketplace submission, Notion behind a public integration · not code you can write, a queue you wait in

xa bespoke adapter per destination · HTML converted into Notion's block tree with its character and per-request batch limits respected, Webflow field mapping plus a second call to actually publish the item, Shopify find-by-handle upsert

xthe feedback loop · Search Console deciding which live posts get refreshed, retitled or relinked, with guards so a page already earning clicks never gets rewritten on a whim

xa pipeline that survives its own failures · every stage retried and resumable, stuck jobs requeued after a deploy kills a worker, and a breaker that trips before the API call so a runaway loop costs zero tokens

xthe tuned prompt library and the checks around it · dozens of purpose-built prompts, title coherence and uniqueness gates, and cannibalisation detection so post 20 doesn't quietly compete with post 3

prior art · use these instead of building, if you'd rather

Nothing worth pointing at — that's why the prompt exists.