skill-creator
This skill provides guidance for creating effective skills.
Determine if a book is worth writing from a business perspective, specifically for Amazon KDP self-publishing.
$ npx -y skills add robertguss/claude-code-toolkit --skill book-market-research --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/book-market-researchContext preview
The summary Claude sees to decide when to auto-load this skill.
Determine if a book is worth writing from a business perspective, specifically for Amazon KDP self-publishing.
name: book-market-research license: Proprietary metadata: author: robertguss version: "1.0" description: 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.
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, 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.
**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.
**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 |
**Quick Assessment (single session):**
experience
**Deep Dive (multi-session):**
authors
**Claude recommends mode** based on author intent, validation status, category competitiveness, and KDP experience.
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
1. Search for competing books in the category 2. Analyze search results for:
3. Identify market gaps from complaint patterns 4. Assess author credibility fit 5. Produce preliminary Market Research Report
**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:
4. Provide Amazon Field Guide (see `references/amazon-field-guide.md`) 5. Output CSV file for user
**Phase 2: Human Data Gathering**
**Phase 3: Quantitative Analysis**
1. Parse completed CSV 2. Calculate market indicators:
3. Score each criterion 4. Produce full Market Research Report with viability scorecard
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
| 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
Extend Claude Code with specialized workflows, automatic formatting, and better defaults. Skills give Claude domain expertise—brainstorming methods, documentation generation, book writing pipelines.
Repo: robertguss/claude-code-toolkit
This skill provides guidance for creating effective skills.
This skill should be used when writing in the distinctive style of David Heinemeier Hansson (DHH). It applies when creating blog posts, technical articles,…
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for…
This skill should be used when writing technical content in the style of Hunt/Thomas (The Pragmatic Programmer) and Joel Spolsky (Joel on Software). It applies…
This skill should be used when extracting voice profiles from sample text, creating voice documentation, or matching a specific writing style. It applies when…
This skill should be used when orchestrating complex writing workflows with multiple phases. It provides two-agent orchestration patterns, the two-gate content…