[verdict][curated prompt][source: skribra.com]

Can I vibecode Skribra?

// the value is the network, the data or the infrastructure

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.

confidence: medium

what it is: Picks the keyword, writes the article, publishes it to your CMS, then keeps it ranking

Buildability index · an editorial game

Price 19 $/month weight: plus 2
Time weekend for the writer, weeks for the approvals weight: minus 2
Category seo and marketing no weight
Moat integrations · execution quality weight: minus 2
Confidence medium weight: zero
What you lose 5 items weight: minus 2
Site skribra.com (si apre in una nuova scheda) no weight

think twice

The moat outweighs the price: rebuilding this is a project, not an evening.

Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.

What you build

One keyword in, one structured long-form article out, published to WordPress · the one destination that doesn't need a platform's permission.

what you need

an LLM API key with real per-article spend · this build is metered, not free
a keyword data source (paid API) or manual keyword picking
an approved OAuth app per destination beyond WordPress · weeks of someone else's review
an always-on host with a queue, since one article is dozens of chained calls

The writer is a weekend · the publishing permissions and the keep-it-ranking machinery are not.

The prompt

The verdict is NOT REALLY, and the prompt stays anyway: it does not replace the app, it rebuilds the part that really is code. The rest is the moat.

One-shot prompt EN

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.

Curated prompt: written and reviewed by hand for this app. In English on purpose — it is the language coding agents work best in.

What you lose

permission 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
a 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
the 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
a 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
the 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

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.

moat: Integrations Execution quality what a moat is

platform approvals/data access/ongoing maintenance