← ClaudeAtlas

docs-sales-conversionlisted

Make generated documentation sell instead of merely inform. Classifies the product's monetization model from real signals (crawled pricing page, repo, description), then applies the matching conversion pattern — a pricing page and plan-comparison table when the product charges, a persistent "start free" CTA ladder when the funnel opens with free access, a self-host-vs-cloud split for open-source products. Every page gets a next action; no page dead-ends. Use during first generation and whenever docs read informative but never ask for the sale.
Docsbook-io/docs-skills · ★ 1 · AI & Automation · score 75
Install: claude install-skill Docsbook-io/docs-skills
# docs-sales-conversion — Docs That Ask for the Sale Documentation is the highest-intent surface a product has: the visitor reading it is already trying to succeed with the product. Most generated docs waste that — they explain the product perfectly and never tell the reader what to do next, never name the price, never mention that there is a free tier at all. This skill fixes that in one pass. It is a **content** skill: it decides which pages exist, what each page's closing action is, and how the money story is told. It never invents prices, plans, or limits. --- ## Step 0 — Read the CTA the owner already set (do this first) Before classifying anything, ask the platform whether this project already has a declared call to action. On Docsbook that is the **Call To Action URL** (Branding tab) — `cta_url` on `get_workspace_info` / `get_workspace`, saved by `update_branding(cta_url: …)`. Any other platform: whatever field records "the page this documentation should drive readers to". **When it is set, it wins over anything you infer.** The owner typed it; a `/pricing` page you found by crawling is a guess about their funnel, and their answer is not. Concretely: - Every page's primary CTA points **there**, unless a page has an obviously better-matching destination already observed on the source (a docs-internal next step, an install command for an OSS install page). - The classification in Step 1 still runs — the CTA tells you *where* to send the reader, not *how* the produ