niche-scout
Evaluate Amazon KDP niche profitability using BSR analysis, keyword volume, and competition scoring. Use when researching book niches, validating publishing ideas, or comparing market opportunities.
Best use case
niche-scout is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Evaluate Amazon KDP niche profitability using BSR analysis, keyword volume, and competition scoring. Use when researching book niches, validating publishing ideas, or comparing market opportunities.
Teams using niche-scout 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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/niche-scout/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How niche-scout Compares
| Feature / Agent | niche-scout | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Evaluate Amazon KDP niche profitability using BSR analysis, keyword volume, and competition scoring. Use when researching book niches, validating publishing ideas, or comparing market opportunities.
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
AI Agent for Product Research
Browse AI agent skills for product research, competitive analysis, customer discovery, and structured product decision support.
AI Agent for SaaS Idea Validation
Use AI agent skills for SaaS idea validation, market research, customer discovery, competitor analysis, and documenting startup hypotheses.
SKILL.md Source
# Niche Scout Evaluate whether a keyword/topic is a profitable KDP publishing niche. Based on the 3-step validation framework from Sean Dollwet, Dale Roberts, and Dave Chesson (175 episodes distilled in Kings of Kindle). ## Usage ``` /niche-scout beekeeping for beginners /niche-scout "anxiety management" /niche-scout claude code AI coding assistant ``` ## Workflow ### Step 1: Amazon Keyword Volume (DataForSEO) Run the keyword volume script to get Amazon search volume and related keywords: ```bash python3 ~/.claude/skills/niche-scout/scripts/keyword-volume.py "$ARGUMENTS" ``` This returns: - Amazon search volume for the seed keyword + 9 variations - Related keywords with volume (up to 20) - Use these to assess **demand** and identify series potential (10-keyword strategy) **Demand threshold:** Seed keyword should have 200+ monthly Amazon searches. Related keywords reveal series opportunities. ### Step 2: BSR Analysis (Apify Amazon Scraper) Run the BSR scraper to get Best Seller Rank for top books: ```bash python3 ~/.claude/skills/niche-scout/scripts/bsr-scraper.py "$ARGUMENTS" ``` This runs two Apify calls: 1. **Search results** — gets titles, prices, ratings, ASINs for top 20 books 2. **Product details** — gets BSR, publisher, categories for top 10 Wait for both to complete (typically 30-90 seconds each). ### Step 3: Score the Niche Apply Sean Dollwet's BSR benchmarks to the scraped data: | Metric | Target | Scoring | |--------|--------|---------| | Books under 5,000 BSR | No more than 5 of top 20 | >5 = too competitive | | Books under 30,000 BSR | Most or all of top 20 | Sweet spot for new publishers | | Books under 100,000 BSR | At least 7 of 10 | Minimum viable demand | | Self-published on page 1 | At least 2-3 | Proves indie can compete | | Search results count | Under 3,000 | Lower = easier to rank | **Self-published detection signals:** - Publisher = "Independently published" or "Independently Published" - Price $2.99-$4.99 range - Keyword-heavy title (exact match of search term) - Stock/template cover design ### Step 4: Check All Three Platforms A keyword that's weak on Kindle might be strong on paperback or audiobook: | Platform | Good BSR | Notes | |----------|----------|-------| | Kindle eBooks | Under 50,000 | Most competitive; most publishers start here | | Paperback | Under 100,000 | Higher royalties; reference/cookbooks do better | | Audiobook (Audible) | Under 100 search results | Least competitive; under-served in most niches | ### Step 5: Generate the Report Output a structured niche report with: 1. **Keyword volume table** — seed + related keywords with Amazon search volume 2. **BSR table** — top 10 books sorted by BSR with publisher, self-pub flag 3. **Benchmark scorecard** — pass/fail on each Dollwet criterion 4. **Estimated daily sales** — using BSR-to-sales conversion (see reference/bsr-sales-table.md) 5. **Competition signals** — weak covers, bad titles, low reviews = beatable 6. **Series potential** — can you find 5-10 related keywords for a book series? 7. **Verdict** — VIABLE / BORDERLINE / TOO COMPETITIVE / DEAD ### Step 6: Hot vs Evergreen Assessment Classify the niche: - **Hot topic**: Trending, short window, fast cash if you move quickly - **Evergreen**: Steady demand year-round, compounds over time - **Seasonal**: Predictable spikes (gardening in spring, etc.) The ideal portfolio mixes both. Check Google Trends for seasonality patterns. --- ## Niche Selection Checklist (from Ch 2) Before committing to a niche, ALL boxes must check: - [ ] **Demand confirmed:** Multiple books in top results have BSR under 100,000 - [ ] **BSR sweet spot:** Most of the top 20 books fall between 10,000 and 30,000 - [ ] **Competition beatable:** No more than 5 books under 5,000 BSR in top 20 - [ ] **Self-published proof:** At least 2-3 self-published books selling well on page 1 - [ ] **Weak spots visible:** You can identify covers, titles, or descriptions you can beat - [ ] **Multi-platform potential:** Checked Kindle, paperback, and audiobook - [ ] **Search results count:** Under 3,000 (lower = better) - [ ] **Series potential:** Can identify 5-10 related keyword variations - [ ] **No trademark issues:** Keywords don't include trademarked terms --- ## Reference Files - For BSR-to-sales conversion: see [reference/bsr-sales-table.md](reference/bsr-sales-table.md) - For tool comparison: see [reference/tools.md](reference/tools.md) - For the full keyword workflow: use `/keyword-fill` after niche is validated ## Tool Dependencies - **DataForSEO** — Amazon keyword volume + related keywords (credentials in ~/.zshrc or hardcoded) - **Apify** — Amazon product scraping for BSR, publisher, categories (APIFY_TOKEN in env) - **Python 3** with `requests` library ## Related Skills - **keyword-fill** — Fill the 7 Amazon keyword boxes (run AFTER niche is validated) - **book-architect** — Generate outline + title/subtitle (run AFTER niche + keywords) - **listing-optimizer** — Write description + select categories - **deep-research** — For deeper market analysis on borderline niches - **seomachine** — For Google keyword data (complements Amazon data)
Related Skills
x-viral-template-miner
When the user wants to find proven-to-travel post templates in their niche and adapt them to their own product. Also use when the user mentions "what's going viral in my space", "what are competitors posting", "copy a viral post", "trending on X", "post ideas", "template mining", or "what to post this week". This is trend hunting, not plagiarism — the output is a template the user fills with their own assets.
x-linkedin-content-relay
When the user has X (Twitter) content that performed well and wants to relay it to LinkedIn 1-2 weeks later with reframing. Also use when the user mentions "repost to LinkedIn", "LinkedIn version of my tweet", "X to LinkedIn", "delayed repost", "LinkedIn for non-tech audience", or "LinkedIn relay". Also use when the user's ICP is non-tech and X is secondary — LinkedIn is the primary channel and this skill produces the content.
x-launch-video-structure
When the user is planning, scripting, or editing a product launch video for X (Twitter) and needs the structure. Also use when the user mentions "launch video", "demo video", "product launch on X", "60 second demo", "how to structure a launch", or "my launch video isn't working". Produces a beat-by-beat timing sheet, not copy.
x-account-warmup
When a user wants to grow an X (Twitter) account from zero before a product launch, or asks how to get first followers, warm up the algorithm, hit ~500-1,000 followers, or prepare an account to make a launch video land. Also use when the user mentions "new X account", "warm up my Twitter", "first 1000 followers", "building in public strategy", "X growth", or "engagement before launch".
skill-stack-thumbnails
Generate blog post thumbnails for Skill Stack using the brand aesthetic. Follows an iterative workflow - brainstorm concepts, get approval, generate with Gemini API.
youtube-ingest
Transcribe YouTube videos and playlists using Gemini Flash
web-scrape
Scrape web pages to clean markdown with optional AI summaries
voice-tyler-cowen
Write in Tyler Cowen's style - matter-of-fact, understated, treats enormous ideas as obvious observations. Read the passages. Absorb the flatness. Channel the HOW, not the content.
voice-trung-phan
Generate tweets and threads in the style of Trung Phan. Not just voice — captures his humor mechanics, format taxonomy, topic selection filter, and structural patterns. Use for trend-reactive tweets, meme commentary, and business/culture threads.
voice-levine-berry
Write in a combined Matt Levine + Wendell Berry voice. Levine's dry logic-walking and parenthetical humor for the analytical sections. Berry's meditative patience for the human ones. Read the passages. Absorb the rhythm. Channel the HOW, not the content.
voice-dan-koe
Write long-form essays and newsletters in Dan Koe's voice — philosophical depth made accessible, staccato rhythm with expansive passages, confident authority, zero hedging. Structured as a teaching conversation with bad-AI/correction/good-version rounds reverse-engineered from his actual articles. Use for newsletters, X articles, blog essays, or any long-form content that needs to blend philosophy with practical frameworks.
skill-extractor
Extract actionable Claude Code skills from raw source material — transcripts, conversations, workflows, expertise dumps. This skill identifies repeatable, promptable workflows embedded in content and scores them by leverage. Use when processing a corpus (podcast transcripts, blog posts, course material) to discover what skills could be built from it.