Skribra
Picks the keyword, writes the article, publishes it to your CMS, then keeps it ranking
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.
Build verification: not recorded. How we judge buildability
What you give up
- 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.
Your build guide
The stack, security requirements, and agent rules for a focused replacement.
Before you start
- 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
Use these project rules and optional skill references alongside the prompt. Review each skill before adding it to your agent; the AGENTS.md export includes the same guidance.
Project rule, data: Model sites, crawl pages, keyword snapshots, audit findings, and report dates; keep stable source IDs and timestamps.
Project rule, behavior: Input: a target keyword plus a short site description. Output: one published post.
Project rule, recovery: 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.
Implementation plan
Phase 1, architecture and data
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. Model sites, crawl pages, keyword snapshots, audit findings, and report dates; keep stable source IDs and timestamps.
Phase 2, implement
Input: a target keyword plus a short site description. Output: one published post.
Phase 3, implement
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.
Phase 4, review and output
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. Publish via the REST API with an application password · draft by default, --publish to go live.
Phase 5, recovery and acceptance
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. Verify this invariant with a saved fixture: A failed crawl retains its last dated snapshot; a report must not imply backlink or keyword coverage the input lacks. State the practical limit: 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.
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), copy the prompt or copy AGENTS.md
prompt copied. want to know what dies next week?
new verdicts + top votes, weekly. free. one-click out.
No prior-art project is listed yet. Compare the scoped build with the paid product before choosing.
Explore related apps
Skribra pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| starter | $19/workspace | — | 5 articles/month; 1,700–3,300 words/article.Annual billing advertises 17% savings, but the exact annual total was not reliably exposed. |
| growth | $39/workspace | — | 12 articles/month; 1,700–3,300 words/article.Annual billing advertises 17% savings, but the exact annual total was not reliably exposed. |
| pro | $75/workspace | — | 30 articles/month; 1,700–3,300 words/article.Annual billing advertises 17% savings, but the exact annual total was not reliably exposed. |
| byok lifetime | — | — | Up to 10 projects; 30 articles/month/project; all agents; 20 seats.One-time $199 purchase; requires the customer's own OpenAI API key and usage charges. |
free tierno free tier (3-day trial only)
billingmonthly + annual for subscriptions; exact annual totals are not public; BYOK is a one-time lifetime purchase
hidden costsSubscription pricing is per project. The $199 BYOK option shifts ongoing OpenAI token charges to the customer.
pricing sources checked 2026-08-14 · pricing source ↗
Questions about Skribra
Can you build your own Skribra with AI?
A full replacement is not the recommended project. 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.
What does the Skribra build prompt cover?
The prompt starts with this scope: One keyword in, one structured long-form article out, published to WordPress · the one destination that doesn't need a platform's permission. Full-product capabilities excluded from the comparison include: 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. Follow the implementation plan and its prerequisites before expanding the build.
How do I use the prompt, AGENTS.md and agent skills?
Start with the Skribra prerequisites and stack, then copy the prompt into your coding agent. Save the project rules as AGENTS.md in the project root. Linked skills are optional packages or source instructions for specific tasks; review their current contents and install only those matching the chosen stack. A skill does not supply API credentials or verify the finished app.
How long will this Skribra project take?
The catalogue estimate is weekend for the writer, weeks for the approvals for the limited scope. Setup, integration approvals, debugging, deployment and ongoing maintenance can add time. This is an estimate, not a delivery guarantee.
What would I give up by replacing Skribra?
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. 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 price is this guide comparing against?
The recorded Starter plan is $19/mo (monthly), checked 2026-07-31. Check the linked pricing source before buying. Building your own also has hosting, API and maintenance costs; the recorded amount is not a guaranteed saving.
What can I use instead of building Skribra?
No alternative is listed in this entry yet. That is a gap in this catalogue, not proof that no suitable product exists. Compare the paid product and the proposed scope before committing to a build.