book-sales-optimization
Optimize useful nonfiction book sales after the book is already working, including Amazon or retailer funnels, cover thumbnail clarity, store descriptions, authentic reviews, extra formats, pricing, upsells, piracy hooks, and fan engagement. Use when improving a book product page, purchase funnel, format strategy, pricing, direct sales, or post-launch growth.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- book-sales-optimization
- license
- MIT
- metadata
- { "tags": "marketing,books,nonfiction,sales,pricing", "version": "0.1.0", "category": "Writing", "displayName": "Book Sales Optimization" }
- description
- Optimize useful nonfiction book sales after the book is already working, including Amazon or retailer funnels, cover thumbnail clarity, store descriptions, authentic reviews, extra formats, pricing, upsells, piracy hooks, and fan engagement. Use when improving a book product page, purchase funnel, format strategy, pricing, direct sales, or post-launch growth.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 5
- 参考文档references/core/checklist.md2.2 KB
- 参考文档references/core/examples.md2.7 KB
- 参考文档references/core/knowledge.md3.9 KB
- 参考文档references/core/rules.md3.5 KB
- 参考文档workflows/audit-retailer-funnel.md2.3 KB
03 SKILL.md 正文
Book Sales Optimization
Core Lens
Sales optimization helps an already useful and recommendable book sell more. It should not be used to compensate for weak promise, poor reader experience, or missing seed audience.
Because retailer rules, royalty terms, advertising interfaces, and review policies change, verify current platform-specific guidance before giving precise operational instructions.
Reference Routing
| Need | Read |
|---|---|
| Core funnel and optimization concepts | references/core/knowledge.md |
| Optimization rules and current-info caveats | references/core/rules.md |
| Example audits and positioning patterns | references/core/examples.md |
| Fast audit checklist | references/core/checklist.md |
| Audit a retailer funnel | workflows/audit-retailer-funnel.md |
Workflow
1. Confirm Optimization Is The Right Lever
Check whether the book already has:
- A specific reader promise.
- Evidence of reader value.
- Some traffic, search, audience, or word of mouth.
- A retailer page, direct-sales page, or purchase path to improve.
If the book is not yet working, route to planning, reader experience, beta reading, or seed marketing first.
2. Audit The Purchase Funnel
Evaluate:
- Thumbnail cover clarity.
- Title and subtitle promise.
- Review count and rating quality.
- Store description.
- Editorial review or endorsement fields.
- Look-inside/sample pages.
- Product images and author profile.
3. Improve Conversion Before Expanding Distribution
Start with the biggest controllable bottlenecks:
- Make the promise legible at thumbnail size.
- Rewrite the description around reader outcomes.
- Use reader language from conversations and beta feedback.
- Encourage authentic reviews without gaming policies.
4. Consider Percentage Boosts
Evaluate extra formats, platforms, partnerships, and support offers by:
Increased reach + increased profit
vs.
Time cost + financial cost + stress cost
5. Optimize Pricing And Relationship Value
Consider:
- Standard ebook and paperback pricing norms.
- Direct-sales bundles.
- Complementary upsells.
- The long-term value of a reader relationship.
- Whether the book supports consulting, teaching, software, or services.
Output Format
Return:
- Main sales bottleneck.
- Funnel audit table.
- Highest-leverage changes, ordered by expected impact.
- Current-info checks needed for platform-specific details.
- Pricing, format, or upsell recommendations when relevant.
- Fan and reader-relationship opportunities.
Quality Bar
Recommendations should improve honest conversion and reader fit. Do not suggest fake reviews, misleading positioning, fake scarcity, policy violations, or tactics that reduce the book's standalone value.
04 同仓库更多 Skills
migrate-to-e2e
Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for /migrate-to-e2e, "migrate our tests to e2e", "port these Maestro flows", "move our TesterArmy tests", or when a project has an e2e config and an older suite still running.
e2e
Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.
create-verification-skill
Generate a project-local verify-<app> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for /create-verification-skill, "make a verification skill for this repo", or when a project has no scripted way to prove UI behavior.
deja-search
deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.
deja-reflect
End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.
revid
Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.