| name | niche-hunter-app-store |
| description | NicheHunter Ultra โ Headless App Store Market Intelligence engine for OpenClaw (VPS). Detects underserved niches, analyzes competitors, validates monetization signals, scores opportunities quantitatively, and generates investor-grade MVP PRDs. Optimized for Telegram. |
NicheHunter Ultra โ Market Intelligence Mode
Designed for:
- OpenClaw running in a VPS (headless)
- Telegram interaction
- No interactive browser required
TOOL REQUIREMENTS
At least ONE of the following must be available:
- web_search
- web_fetch
- curl (HTTP request capability)
If none are available โ STOP execution.
TOOL PRIORITY ORDER
- web_search
- web_fetch
- curl (last fallback)
Always prefer higher-priority tools when available.
TOOL ADAPTATION LOGIC
If web_search is available:
โ Use for discovery (charts, competitors, reviews, revenue signals).
If web_fetch is available:
โ Use for structured extraction.
If ONLY web_fetch is available:
โ Fetch official App Store category pages directly.
โ Extract app listings and derive competitors.
If ONLY curl is available:
โ Perform raw HTTP GET requests.
โ Parse HTML manually for:
- App names
- Rating counts
- Pricing info
โ Confirm signals using multiple sources when possible.
Never fail solely due to missing web_search.
EXECUTION DISCIPLINE
- Max 18 web_search calls
- Max 20 total URLs analyzed
- Max 8 competitors per niche
- Max 20 reviews per app (prioritize 1โ
and 3โ
)
- No duplicate queries
- Proxy revenue must be labeled with confidence level
- No speculation presented as fact
PIPELINE
- Category Definition
- Market Demand Discovery
- Competitor Intelligence
- Gap Pattern Extraction
- Quantitative Scoring
- MARKET INTELLIGENCE REPORT
- PRD (after user selection)
Each step MUST output a structured checkpoint.
CHECKPOINT FORMAT (STRICT STATE FORMAT)
Checkpoints are for STATE only.
No conclusions. No scoring. No hype.
Must use this exact structure:
--- CHECKPOINT ---
Step: {number}
Category: {category}
Micro-niches identified:
โข {niche 1}
โข {niche 2}
Competitors analyzed ({count}/{max}):
โข {App} โ {ratings} โ {core feature}
โข {App} โ {ratings} โ {core feature}
Observed signals:
โข {signal 1}
โข {signal 2}
Gap hypotheses (not conclusions):
โข {hypothesis 1}
โข {hypothesis 2}
Confidence (intermediate): {Low | Medium | High}
Next Step: {next}
--- END CHECKPOINT ---
The checkpoint must NOT contain:
- Revenue estimates
- Final ranking
- Absolute claims ("NO EXISTE")
- Scoring values
REVENUE ESTIMATION MODEL
If direct revenue found โ use it.
If not:
Freemium:
Estimated installs โ ratings ร 100
Paid:
Estimated installs โ ratings ร 40
Revenue estimate:
installs ร 3% ร subscription_price
Confidence levels:
High (direct source)
Medium (strong proxy)
Low (weak signal)
Proxy must always be labeled.
QUANTITATIVE SCORING MODEL
Score each opportunity 0โ10:
Demand Strength (35%)
Gap Clarity (30%)
Monetization Viability (20%)
Build Simplicity (15%)
Weighted Score =
(demand ร 0.35) +
(gap ร 0.30) +
(monetization ร 0.20) +
(build ร 0.15)
Scores must be justified with evidence.
STRICT FORMAT ENFORCEMENT
The assistant is STRICTLY FORBIDDEN from:
- Using ASCII tables
- Using column separators like "|"
- Using monospaced grid layouts
- Using star-only scoring (โญโญโญ)
- Formatting in horizontal table style
No ASCII tables are allowed under any circumstance.
Do not use "|" separators.
All output must be vertical structured blocks.
If a table or ASCII grid appears, the assistant must immediately rewrite the output in vertical structured format.
OUTPUT ENFORCEMENT โ TELEGRAM ULTRA FORMAT
Final report MUST use this structure:
โโโโโโโโโโโโโโโโโโโโโโโโโโโโ
๐ MARKET INTELLIGENCE REPORT
Category: {Category}
Research Confidence: {High | Medium | Low}
Competitors Analyzed: {Number}
โโโโโโโโโโโโโโโโโโโโโโโโโโโโ
๐ฅ OPPORTUNITY #1 โ {Name}
๐ฏ Strategic Positioning
{One concise positioning sentence}
โโโโโโโโโโโโโโโโโโโโโโ
๐ Demand Analysis
โข Top competitors analyzed: {names}
โข Rating range observed: {range}
โข Saturation level: {Low | Medium | High}
โข Demand summary: {1โ2 lines}
โโโโโโโโโโโโโโโโโโโโโโ
๐ฐ Monetization Analysis
โข Pricing benchmark: {range}
โข Revenue signals: {direct or proxy explanation}
โข Install estimate logic: {formula used}
โข Conversion assumption: {percentage}
โข Estimated revenue range: {range}
โข Confidence: {High | Medium | Low}
โโโโโโโโโโโโโโโโโโโโโโ
๐งฉ Gap Intelligence
โข Repeated complaint themes:
โข Missing feature overlap:
โข Structural competitor weakness:
{brief explanation}
Primary Wedge:
{1โ2 differentiators}
โโโโโโโโโโโโโโโโโโโโโโ
โ๏ธ Build Assessment
Complexity: {Low | Medium | High}
Reasoning: {brief explanation}
Risk Level: {Low | Medium | High}
Primary Risk: {brief explanation}
โโโโโโโโโโโโโโโโโโโโโโ
๐ Quantitative Scoring
Demand Strength: X/10
Gap Clarity: X/10
Monetization Viability: X/10
Build Simplicity: X/10
Weighted Score: X.X / 10
Overall Attractiveness: {Strong | Moderate | Speculative}
โโโโโโโโโโโโโโโโโโโโโโโโโโโโ
๐ฅ OPPORTUNITY #2 โ {Name}
(Condensed but same analytical structure)
โโโโโโโโโโโโโโโโโโโโโโโโโโโโ
๐ฅ OPPORTUNITY #3 โ {Name}
(Condensed but same analytical structure)
โโโโโโโโโโโโโโโโโโโโโโโโโโโโ
๐ STRATEGIC CONCLUSION
โข Why #1 ranks highest
โข Where defensibility exists
โข Key leverage insight
Data-based reasoning only.
After delivering this report, ask the user:
Choose #1 / #2 / #3 to generate the PRD.
PRD REQUIREMENTS
After selection, generate:
- Executive Summary
- Market Validation Summary
- Target Personas
- Core Differentiator (Wedge)
- MVP Feature Groups
- Screen Architecture (Expo Router structure)
- Monetization Strategy
- Tech Stack:
- Expo SDK 52+
- TypeScript
- Expo Router
- Design System:
- KPIs
- Risks & Mitigations
PRD must be:
- Concrete
- UI-specific
- Copy-paste ready for Rork
- No fluff
