book-market-research

Assess commercial viability of book concepts for Amazon KDP self-publishing. Use when the user has a Book Concept Document and wants to understand market demand, competition, pricing, and positioning before committing to write. Produces a Market Research Report with viability scorecard and Go/No-Go recommendation. Works standalone (commercial analysis only) or after idea-validator (integrated assessment). Nonfiction only.

56 stars

Best use case

book-market-research is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Assess commercial viability of book concepts for Amazon KDP self-publishing. Use when the user has a Book Concept Document and wants to understand market demand, competition, pricing, and positioning before committing to write. Produces a Market Research Report with viability scorecard and Go/No-Go recommendation. Works standalone (commercial analysis only) or after idea-validator (integrated assessment). Nonfiction only.

Teams using book-market-research should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/book-market-research/SKILL.md --create-dirs "https://raw.githubusercontent.com/robertguss/claude-code-toolkit/main/skills/non-fiction-book-factory/book-market-research/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/book-market-research/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How book-market-research Compares

Feature / Agentbook-market-researchStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Assess commercial viability of book concepts for Amazon KDP self-publishing. Use when the user has a Book Concept Document and wants to understand market demand, competition, pricing, and positioning before committing to write. Produces a Market Research Report with viability scorecard and Go/No-Go recommendation. Works standalone (commercial analysis only) or after idea-validator (integrated assessment). Nonfiction only.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Market Research

Determine if a book is worth writing from a business perspective, specifically
for Amazon KDP self-publishing.

## Core Philosophy

**Commercial viability is separate from intellectual merit.** A brilliant idea
can fail commercially. A mediocre idea can succeed. This skill assesses the
market, not the idea itself.

**Better to know the odds now.** Authors deserve realistic expectations before
investing months in writing.

**Author intent shapes interpretation.** A 5/10 viability score means different
things to someone seeking income versus someone writing for legacy. Same data,
different recommendations.

**Claude does the analysis; human gathers the data Claude can't access.** Claude
performs qualitative research via web search. For quantitative data (BSR,
prices, review counts), Claude provides a pre-filled spreadsheet and field
guide—human gathers the numbers and brings them back.

## Dependency Model

**Standalone Mode:** Book Concept Document only → pure commercial analysis.
Claude flags that intellectual validation hasn't been done and recommends
`idea-validator` if concerns arise.

**Post-Validation Mode:** Book Concept Document + Validation Report → integrated
assessment. Combines intellectual merit with commercial viability for definitive
pipeline gate.

## Author Intent

**Ask before researching.** Author intent determines how to interpret the
viability score.

| Intent               | Description                              | Score Interpretation                               |
| -------------------- | ---------------------------------------- | -------------------------------------------------- |
| **Income**           | Book must generate meaningful revenue    | Score is decisive—low score means revise or kill   |
| **Authority**        | Position as expert, book is a credential | Moderate score acceptable if positioning is strong |
| **Passion/Legacy**   | "This book needs to exist"               | Low score = proceed with eyes open, not a blocker  |
| **Lead Generation**  | Funnel for services/consulting           | Score less critical if book serves the funnel      |
| **Audience Service** | Serving existing followers               | Platform strength matters more than market size    |

## Session Modes

**Quick Assessment (single session):**

- Claude-only qualitative analysis via web search
- Identifies competitors, positioning gaps, review themes
- Produces preliminary viability assessment
- No manual data gathering required
- Best for: early-stage filtering, passion/legacy authors, authors with KDP
  experience

**Deep Dive (multi-session):**

- Full qualitative analysis PLUS quantitative data
- Claude provides pre-filled CSV with competitor URLs
- Human gathers BSR, prices, review counts from Amazon
- Claude analyzes completed data for full scorecard
- Best for: income-focused authors, competitive categories, first-time KDP
  authors

**Claude recommends mode** based on author intent, validation status, category
competitiveness, and KDP experience.

## Session Flow

### Starting Research

1. Ask for Book Concept Document (and Validation Report if available)
2. Read carefully, note the core thesis and target reader
3. Ask about author intent (Income/Authority/Passion/Lead Gen/Audience Service)
4. Recommend session mode with reasoning
5. User confirms mode
6. Proceed to research

### Quick Assessment Flow

1. Search for competing books in the category
2. Analyze search results for:
   - Competitor titles, authors, positioning
   - Bestseller badges (indicator of demand)
   - Publisher patterns (traditional vs. self-pub)
   - Review themes from Goodreads/snippets
3. Identify market gaps from complaint patterns
4. Assess author credibility fit
5. Produce preliminary Market Research Report

### Deep Dive Flow

**Phase 1: Qualitative Research**

1. Perform Quick Assessment steps
2. Identify 5-8 key competitors for quantitative analysis
3. Generate pre-filled `competitor-analysis.csv` with:
   - Title, Author, Amazon URL (filled by Claude)
   - BSR, prices, reviews, rating, pages, KU status (for human to fill)
4. Provide Amazon Field Guide (see `references/amazon-field-guide.md`)
5. Output CSV file for user

**Phase 2: Human Data Gathering**

- User opens CSV in Excel/Sheets
- User visits each Amazon URL (~10 min for 5-8 books)
- User fills in the quantitative fields
- User uploads completed CSV

**Phase 3: Quantitative Analysis**

1. Parse completed CSV
2. Calculate market indicators:
   - Average BSR (demand signal)
   - Price range and median
   - Review velocity patterns
   - KU saturation
3. Score each criterion
4. Produce full Market Research Report with viability scorecard

### Ending Any Session

1. Summarize what was accomplished
2. Output all documents as files
3. State clearly what comes next
4. If mid-Deep-Dive: remind about CSV and field guide

## Viability Scorecard

| Criterion              | Weight | What It Measures                                                        |
| ---------------------- | ------ | ----------------------------------------------------------------------- |
| Market Demand          | 25%    | Are people buying books in this space? BSR patterns, bestseller signals |
| Review Landscape       | 15%    | Review counts/ratings, gap signals from complaints                      |
| Competition Gap        | 15%    | Differentiation opportunity, positioning white space                    |
| Author Credibility     | 15%    | Does author's background match the claims?                              |
| Pricing Viability      | 10%    | Can price competitively and maintain margin?                            |
| Author Platform        | 10%    | Existing audience for launch velocity                                   |
| Timing                 | 5%     | Trend momentum vs. evergreen stability                                  |
| Production Feasibility | 5%     | Can this realistically be written?                                      |

**Scoring:** Each criterion rated 1-10. Weighted average produces overall score.

## Score Interpretation

| Score   | Label              | Meaning                                       |
| ------- | ------------------ | --------------------------------------------- |
| 7.0+    | **Strong Go**      | Market conditions favor success               |
| 5.5–6.9 | **Conditional Go** | Viable with strategic adjustments             |
| 4.0–5.4 | **Revise**         | Significant concerns—reposition or reconsider |
| <4.0    | **Kill**           | Market conditions unfavorable                 |

**Intent Overlay:**

- Income authors: Follow score literally
- Authority authors: Conditional Go sufficient if positioning is strong
- Passion authors: Even Kill score = "proceed with eyes open"
- Lead Gen authors: Platform fit matters more than raw score

## Research Methods

Claude performs qualitative research via web search. See
`references/research-methods.md` for detailed methodology.

**What Claude CAN assess via search:**

- Competitor titles, authors, positioning
- Bestseller badges (demand indicator)
- Publisher patterns
- Review themes and complaints
- Market gaps and opportunities
- Author credibility signals

**What requires human data gathering:**

- Best Sellers Rank (BSR)
- Exact prices (Kindle, paperback, hardcover)
- Review counts and star ratings
- Page counts
- Kindle Unlimited status
- Category rankings

For human data gathering, Claude provides a pre-filled CSV and the Amazon Field
Guide from `references/amazon-field-guide.md`.

## Market Research Report Structure

Use template from `assets/templates/market-research-report.md`.

1. **Executive Summary** — 2-3 sentences, overall assessment, recommendation
2. **Author Intent & Interpretation** — how intent shapes the recommendation
3. **Viability Scorecard** — weighted scores with reasoning
4. **Competitive Landscape** — top competitors, their positioning, gaps
5. **Target Reader Analysis** — refined reader persona, underserved needs
6. **Positioning Recommendation** — how to differentiate
7. **Pricing Recommendation** — based on market analysis
8. **Title/Subtitle Direction** — market-informed suggestions
9. **Platform Fit Assessment** — author's existing audience leverage
10. **Timing Assessment** — trend vs. evergreen
11. **Key Risks** — what could derail commercial success
12. **Recommendation** — Go / Conditional Go / Revise / Kill with reasoning

## Handoff

**To book-architect (if Go):**

- Market Research Report
- Competitor Analysis (qualitative findings)
- Positioning and differentiation guidance

**Back to idea-validator (if concerns):**

- Flag if intellectual validation needed
- Specific concerns about claims or credibility

**Back to book-ideation (if Revise):**

- Specific repositioning suggestions
- Reader persona refinements

## Scope Boundaries

This skill assesses **commercial viability**, not:

- Intellectual merit (that's `idea-validator`)
- Book structure (that's `book-architect`)
- Writing quality (that's the editing pipeline)

Commercial viability is necessary but not sufficient. A book can be commercially
viable but intellectually weak, or intellectually strong but commercially
doomed.

Related Skills

book-research-assistant

56
from robertguss/claude-code-toolkit

Plan, orchestrate, and validate deep research for nonfiction books. Use when an author has completed book architecture and needs to fill research gaps before outlining chapters. Triggers include requests to plan research, generate research prompts, validate research quality, or prepare for drafting. This skill does everything around deep research—planning, prompting, validating, synthesizing—but the actual research execution happens externally via Claude and Gemini deep research. Requires upstream documents from book-architect (Research Gaps Document, Master Architecture Document, Section Blueprints) and book-ideation (Book Concept Document).

book-ideation

56
from robertguss/claude-code-toolkit

Develop raw book ideas into structured nonfiction book concepts. Use when the user wants to develop a book idea, has brainstorm documents to refine into a book concept, wants to articulate a book's thesis/promise/reader/transformation, or needs to prepare a book concept for validation and market research. Nonfiction only. Produces a Book Concept Document with all elements needed for downstream skills (idea-validator, market-research, book-architect).

book-idea-validator

56
from robertguss/claude-code-toolkit

Stress-test book concepts against existing research before committing to architecture. Use when the user has a Book Concept Document ready for validation, wants to verify their thesis is defensible, needs to understand the competitive intellectual landscape, or wants honest assessment of their idea's strengths and weaknesses. Produces a Validation Report that informs the Go/No-Go decision. Nonfiction only.

book-architect

56
from robertguss/claude-code-toolkit

Design the structural and emotional architecture for nonfiction books. Use when an author has a validated book concept and needs to create the blueprint before drafting. Triggers include requests to structure a book, create a chapter outline, design a table of contents, map the reader's journey, or plan book organization. Requires upstream documents from book-ideation (Book Concept Document) and optionally from idea-validator (Validation Report) and market-research (Market Research Report).

app-store-opportunity-research

56
from robertguss/claude-code-toolkit

Full-pipeline iOS App Store opportunity research. Discovers underserved niches, analyzes competitor gaps, estimates revenue, produces scored top-3 opportunity reports, and writes MVP PRDs — all through browser and web research. Use when the user wants to find profitable iOS app ideas, research App Store charts, analyze competitor apps (ratings, reviews, revenue, gaps), generate opportunity reports, or write MVP PRDs. Triggers on "find app opportunities", "app store research", "what app should I build", "research this app category", "find a gap in the app store", "ios app ideas".

app-growth-playbook

56
from robertguss/claude-code-toolkit

Generate platform-specific, actionable growth playbooks for mobile apps. Use when planning a Product Hunt launch, creating TikTok/Reels content strategies, setting up Apple Search Ads campaigns, preparing App Store featuring submissions, building referral loops, designing email/push re-engagement campaigns, writing Reddit launch posts, or creating content marketing plans for app growth. Provides templates, scripts, timing guides, and step-by-step processes — not generic advice.

ebook-discovery

56
from robertguss/claude-code-toolkit

Surface ebook ideas you didn't know you had. Use when ready to discover what ebooks might be hiding in your content, expertise, or thinking. Supports both content-rich creators (blog posts, videos, newsletters) and those with unpublished expertise. Produces a curated list of ebook candidates ready for Concept Development. Handles multi-session discovery with living documents.

ebook-concept-development

56
from robertguss/claude-code-toolkit

Develop ebook ideas into structured concepts ready for architecture. Use when the user has an ebook idea (from a brainstorm document, existing content to repurpose, a book section to extract, or a fresh concept) and wants to develop it into a clear, validated concept. Produces an Ebook Concept Document with reader, transformation, promise, content source, scope/format, and key topics. Handles multi-session development with living documents.

writing-dna-discovery

56
from robertguss/claude-code-toolkit

Capture a writer's voice DNA through collaborative interview and sample analysis. Use when someone wants to document their writing voice for use with a ghost writer skill. Produces a Voice DNA Document with patterns, anti-patterns, and actionable guidance. Handles one register/mode per session, supports refinement over time.

ghost-writer

56
from robertguss/claude-code-toolkit

Produce first drafts that match a writer's authentic voice using their Voice DNA Document. Consumes DNA documents from writing-dna-discovery skill. Generates 2 meaningfully different drafts with headlines, confidence assessment, decision notes, and DNA refinement suggestions. Collaborative partner that evaluates, pushes back, and advocates for quality. Handles blog posts, essays, newsletters, and more.

chapter-architect

56
from robertguss/claude-code-toolkit

Plan and architect a single chapter at beat-level granularity. Use when you have a chapter from the Architecture Document and need to create a detailed outline before drafting. Produces a Chapter Outline Document for use by draft-coach or ghostwriter.

paywall-pricing-optimizer

56
from robertguss/claude-code-toolkit

Design effective paywalls, structure subscription tiers, and optimize pricing for mobile apps. Covers monetization model selection, paywall screen design, pricing psychology, A/B testing strategy, and RevenueCat/StoreKit/Google Billing integration. Use when the user wants to monetize an app, design a paywall, choose between subscription vs one-time purchase, set pricing tiers, improve conversion rates, plan pricing experiments, or integrate in-app purchases. Triggers on "design my paywall", "how should I price my app", "subscription tiers", "monetization strategy", "paywall copy", "free trial length", "RevenueCat setup", "improve paywall conversion".