agentleFS
robertgussrobertguss/claude-code-toolkit/skills/non-fiction-book-factory/book-market-research/SKILL.md

book-market-research

Skill118 starsChanged 4 months agoMITView on GitHub

Determine if a book is worth writing from a business perspective, specifically for Amazon KDP self-publishing. 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,…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No manual data gathering required

    line 69
  2. Distinctive:

    Ask for Book Concept Document (and Validation Report if available)

    line 89
  3. Distinctive:

    Read carefully, note the core thesis and target reader

    line 90
  4. Very specific:

    Ask about author intent (Income/Authority/Passion/Lead Gen/Audience Service)

    line 91
  5. Distinctive:

    Search for competing books in the category

    line 98
  6. Distinctive:

    If mid-Deep-Dive: remind about CSV and field guide

    line 143
  7. Very specific:

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

    line 204

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

IntentDescriptionScore Interpretation
IncomeBook must generate meaningful revenueScore is decisive—low score means revise or kill
AuthorityPosition as expert, book is a credentialModerate score acceptable if positioning is strong
Passion/Legacy"This book needs to exist"Low score = proceed with eyes open, not a blocker
Lead GenerationFunnel for services/consultingScore less critical if book serves the funnel
Audience ServiceServing existing followersPlatform 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

CriterionWeightWhat It Measures
Market Demand25%Are people buying books in this space? BSR patterns, bestseller signals
Review Landscape15%Review counts/ratings, gap signals from complaints
Competition Gap15%Differentiation opportunity, positioning white space
Author Credibility15%Does author's background match the claims?
Pricing Viability10%Can price competitively and maintain margin?
Author Platform10%Existing audience for launch velocity
Timing5%Trend momentum vs. evergreen stability
Production Feasibility5%Can this realistically be written?

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

Score Interpretation

ScoreLabelMeaning
7.0+Strong GoMarket conditions favor success
5.5–6.9Conditional GoViable with strategic adjustments
4.0–5.4ReviseSignificant concerns—reposition or reconsider
<4.0KillMarket 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.