Skip to content
amazon-competitor-intelligence-monitor logo

ZooData β€” Competitor Intelligence Monitor

amazon-competitor-intelligence-monitor

Amazon competitor intelligence engine. Produces analytical output focused on a defined set of competitors: either a one-shot deep teardown (Full Scan: 28-35 credits, 11 endpoints, battle card, side-by-side comparison, pricing/review/inventory breakdown) OR sustained per-competitor monitoring with...

SKILL.md

Full skill instructions

ZooData β€” Competitor Intelligence Monitor

Know your enemy. Two modes: Full Scan + Quick Check. Respond in user's language.

Files

FilePurpose
{skill_base_dir}/​scripts/​zoodata.pyExecute for all API calls (run --help for params)
{skill_base_dir}/​references/​reference.mdLoad for exact field names or response structure
{skill_base_dir}/​monitor-data/Runtime storage (auto-created): config.json, baseline.json, history/, alerts.json

Credential

Required: ZOODATA_API_KEY. Get free key at zoodata.ai/​api-keys.

Capabilities & Data Flow

  • Network: only https://api.zoodata.ai (Bearer ZOODATA_API_KEY). Setting ZOODATA_BASE_URL to any other host triggers a CLI warning β€” do not point it at hosts you don't trust.
  • Execution: bundled shared ZooData CLI {skill_base_dir}/​scripts/​zoodata.py (Python 3, stdlib-only). The shared CLI exposes ALL ZooData endpoints as subcommands; this skill's workflows use: categories, market, competitors, products, product, history, analyze, competitor-analysis, check, plus the review fallback toolkit (reviews-raw / review-tag-prompt / review-reduce-prompt / review-aggregate). Do not invoke unrelated subcommands for this skill's tasks.
  • Local files: a temporary /​tmp/​review_<ASIN>_<timestamp>/ working dir during the review fallback; reads the optional credential store ~/​.zoodata/​config.json.
  • Sent to the API: keywords, category paths, ASINs, marketplace/​date and numeric filter values only. Never sent: budget, experience level, risk tolerance, or any other user-profile text β€” profile inputs map client-side to numeric filters.
  • Credits: every API call consumes account credits. For broad or ambiguous requests, state the estimated credit cost and confirm with the user before running multi-call scans. The composite competitor-analysis command executes ~17+ API calls (Full Scan, ~28-35 credits documented) in ONE invocation and has NO skip/​trim flags β€” under a credit cap, use the granular commands instead.

Input

Required: keyword or ASIN(s). Optional: my_asin, competitor_asins, brand. If only ASIN given β†’ derive keyword via product --asin then ask user to confirm. Brand queries MUST also include confirmed --category.

API Pitfalls (CRITICAL)

  1. Category auto-detection: categoryPath is auto-detected from keyword, ASIN, or top search result. If category_source in output is inferred_from_search, MUST confirm with user before trusting results
  2. All keyword-based endpoints MUST include --category; ASIN-specific endpoints do NOT need it
  3. Brand + category: a brand sells across categories β€” only analyze within locked subcategory
  4. Use API fields directly: revenue=sampleAvgMonthlyRevenue (NEVER priceΓ—sales), sales=monthlySalesFloor, concentration=sampleTop10BrandSalesRate
  5. reviews/​analysis: needs 50+ reviews. Fallback chain when sample is insufficient:
    1. Lightweight: realtime/​product ratingBreakdown β€” only star distribution, no themes
    2. Full 11-dim insights β€” bypass /​reviews/​analysis entirely: a. zoodata.py reviews-raw --asin X β†’ fetch up to 100 raw reviews (10 credits, ~60s) b. For each review: render Map prompt via zoodata.py review-tag-prompt --review '<json>' and have your own LLM produce JSON tags (sentiment + 11 dimensions) c. Collect candidate phrases per dimension; for each dimension render Reduce prompt via zoodata.py review-reduce-prompt --label-type X --candidates '[...]' and have your LLM produce semantic clusters d. zoodata.py review-aggregate --reviews R --tagged T --clusters C β†’ consumerInsights output compatible with /​reviews/​analysis
    3. Fallback caveats (apply to the 4-step chain above β€” lessons from end-to-end validation):
      • Working dir: WORK=/​tmp/​review_<ASIN>_$(date +%s) && mkdir -p $WORK
      • Step b CLI behavior: review-tag-prompt RENDERS the prompt only; YOUR LLM produces the JSON. Render once to learn the schema, then produce tags for all N reviews in one in-context pass (don't call the CLI N times).
      • Step c candidate extraction (Python one-liner): candidates = {d: sorted({el.strip().lower() for t in tagged for el in (t.get(d) or [])}) for d in DIMS}
      • Small-sample rule (reviewCount<50): demote single-mention items πŸ“Šβ†’πŸ”; NEVER attach table-level or section-header πŸ“Š when any row inside is πŸ”; suppress "πŸ”΄ Critical" verdicts on count=1
      • Scope: fallback replaces ONLY the /​reviews/​analysis aggregation. This skill's primary workflow outputs (competitor metrics, brand ranking, pricing, etc.) remain valid β€” do not re-run them.

On Missing Key

When ZOODATA_API_KEY is not set (verify via python {skill_base_dir}/​scripts/​zoodata.py check β€” exits 2 if no key in env or ~/​.zoodata/​config.json): follow the "On Missing Key" protocol in zoodata/​SKILL.md β€” STOP before any call, link the user to https://zoodata.ai/en/api-keys, and DO NOT produce a "partial analysis from public knowledge" / "for reference only" fallback as a substitute.

On 401 Invalid Key

When zoodata.py returns code 401: follow the "On 401 Invalid Key" protocol in zoodata/​SKILL.md β€” STOP further calls, tell the user the key was rejected and direct them to api-keys, do not fabricate missing data.

On 402 Credit Exhausted

When zoodata.py returns code 402: follow the "On 402 Credit Exhausted" protocol in zoodata/​SKILL.md β€” STOP further calls, report partial findings already gathered, do not fabricate missing data.

Mode Selection

  • Full Scan (~28-35 credits): First run, no baseline.json, explicit request, or weekly refresh
  • Quick Check (~5-10 credits): Cron trigger, baseline exists, "check competitors"

Full Scan Flow

  1. competitor-analysis --keyword X [--category Y] [--my-asin Z] (composite, auto-detects category)
  2. If category_source is inferred_from_search, confirm with user before presenting results
  3. Analyze & score β†’ save baseline to {skill_base_dir}/​monitor-data/ β†’ offer Auto-Monitor

Quick Check Flow

  1. Load config.json + baseline.json from {skill_base_dir}/​monitor-data/ (missing β†’ fall back to Full Scan)
  2. Poll product --asin {asin} for each tracked ASIN
  3. Diff against baseline with tiered alerts β†’ update baseline β†’ offer Auto-Monitor

Alert Tiers

πŸ”΄ Critical🟑 Watch🟒 Opportunity
Price change > thresholdFBA↔FBM switchCompetitor stock-out
BSR crash > thresholdRating changeBullet/​image changes
Buy Box owner changedAbnormal review growthVariant added/​removed
Title modified

Competitive Score (per competitor, 1-100)

DimensionWeight80-100 (Strong)50-79 (Moderate)0-49 (Weak)
Sales Dominance25%Top 3 in category, >5K units/​mo πŸ“ŠTop 20, 1K-5K units/​mo πŸ“ŠBelow Top 20, <1K units/​mo πŸ“Š
Brand Strength20%Brand in CR10, 5+ SKUs, wide price range πŸ“ŠKnown brand, 2-4 SKUs πŸ“ŠUnknown brand, single SKU πŸ“Š
Listing Quality20%7+ images, 5 bullets, A+, optimized title πŸ“Š5-6 images, basic bullets πŸ“Š<5 images, weak bullets, no A+ πŸ“Š
Customer Satisfaction20%Rating β‰₯4.5, <3% 1-star, positive sentiment πŸ“Š4.0-4.4, 3-8% 1-star πŸ“Š<4.0 or >8% 1-star πŸ“Š
Trend Momentum15%BSR improving 30d, sales growth >10% πŸ”BSR stable, flat sales πŸ”BSR declining, sales drop πŸ”

Competitive Threat Level

Total ScoreThreatInterpretation
80-100πŸ”΄ DominantHard to compete head-on; find differentiation or avoid price band πŸ’‘
50-79🟑 CompetitiveBeatable with better listing, pricing, or reviews πŸ’‘
0-49🟒 VulnerableWeak competitor; opportunity to capture share πŸ’‘

Market Structure Analysis

  • CR10 > 70%: Concentrated market β€” new entrants need strong differentiation or niche positioning πŸ”
  • CR10 40-70%: Moderately competitive β€” room for well-positioned products πŸ”
  • CR10 < 40%: Fragmented β€” opportunity for brand building πŸ”
  • Top brand share > 25%: Category leader dominance β€” avoid direct competition in their price band πŸ’‘
  • New SKU rate > 15%: Active market with frequent new entrants πŸ“Š
  • New SKU rate < 5%: Mature/​stagnant market, high barriers πŸ”

Auto-Monitor Prompt

After EVERY run, offer: "Set up automatic monitoring? I can generate a scheduled Quick Check." Provide platform-specific setup (OpenClaw /​cron, ChatGPT Scheduled Tasks, Claude Projects).

Output Spec

Full Scan sections: Battlefield Overview β†’ Competitor Matrix β†’ Brand Power Ranking β†’ Price Map β†’ 30-Day Trends β†’ Review Battle β†’ Listing Audit β†’ Competitive Scores β†’ Battle Strategy β†’ Data Provenance β†’ API Usage.

Language (required)

Output language MUST match the user's input language. If the user asks in Chinese, the entire report is in Chinese. If in English, output in English. Exception: API field names (e.g. monthlySalesFloor, categoryPath), endpoint names, technical terms (e.g. ASIN, BSR, CR10, FBA, credits) remain in English.

Disclaimer (required, at the top of every report)

Data is based on ZooData API sampling as of [date]. Monthly sales (monthlySalesFloor) are lower-bound estimates. This analysis is for reference only and should not be the sole basis for business decisions. Validate with additional sources before acting.

Confidence Labels (required, tag EVERY conclusion)

  • πŸ“Š Data-backed β€” direct API data (e.g. "CR10 = 54.8% πŸ“Š")
  • πŸ” Inferred β€” logical reasoning from data (e.g. "brand concentration is moderate πŸ”")
  • πŸ’‘ Directional β€” suggestions, predictions, strategy (e.g. "consider entering $10-15 band πŸ’‘")

Rules: Strategy recommendations are NEVER πŸ“Š. Anomalies (>200% growth) are always πŸ’‘. User criteria override AI judgment.

Aggregate-label rule (applies to ALL report output, not just fallback): NEVER attach πŸ“Š to ANY element that aggregates or groups underlying content when ANY piece of that content is πŸ” or πŸ’‘. "Aggregate/​grouping elements" include:

  • Section headers at EVERY level (#, ##, ###, ####) β€” including top-level summary sections like "Overall Score", "Verdict", "Executive Summary"
  • Summary/​score lines anywhere in the report (e.g. ## Overall Score β€” 27/​100 Β· Grade F πŸ“Š is WRONG if any Basis row inside is πŸ”)
  • Table column headers in comparison tables (e.g. **Target ASIN** πŸ“Š as a column label is WRONG if any cell in that column contains πŸ”)
  • Table row headers or row-aggregation labels (when the row aggregates multiple cells of mixed confidence)
  • Any other visual grouping label β€” bullet-list group titles, callout box titles, etc.

A group-level πŸ“Š implies the whole block/​column/​row is data-backed, which smuggles inferred/​directional content into the πŸ“Š tier via visual grouping. Either (a) omit the group-level label entirely (preferred when content mixes tiers), or (b) use the LOWEST confidence present inside (πŸ” if any underlying content is πŸ”; πŸ’‘ if any is πŸ’‘). This is a universal output-quality rule β€” it applies regardless of which fallback path (if any) was triggered.

Emoji reservation rule (closely related): The three confidence symbols πŸ“Š πŸ” πŸ’‘ are RESERVED for confidence labeling. NEVER use them as decorative prefixes on section headers, table headers, or any aggregate element β€” even when you also include a correct confidence suffix on the same line. Example:

  • ❌ WRONG: ## πŸ“Š Overall Score β€” 27/​100 Β· Grade F πŸ” (the leading πŸ“Š reads as a data-backed claim even though the trailing πŸ” is correct)
  • βœ… RIGHT: ## Overall Score β€” 27/​100 Β· Grade F πŸ” (no decorative emoji, just the proper confidence suffix)
  • βœ… RIGHT: ## 🎯 Overall Score β€” 27/​100 Β· Grade F πŸ” (use non-reserved decorative icons like 🎯 🧭 πŸ“‹ πŸ“ πŸ“‚ 🏁 🚨 πŸ† πŸ”” when a visual prefix is desired)

Decorative emoji β‰  confidence label β€” but from a reader's perspective, a leading πŸ“Š/πŸ”/πŸ’‘ is indistinguishable from a confidence claim. Reserve these three symbols EXCLUSIVELY for confidence annotation to avoid ambiguity.

Data Provenance (required)

Include a table at the end of every report:

DataEndpointKey ParamsNotes
(e.g. Market Overview)markets/​searchcategoryPath, topN=10πŸ“Š Top N sampling, sales are lower-bound
............

Extract endpoint and params from _query in JSON output. Add notes: sampling method, T+1 delay, realtime vs DB, minimum review threshold, etc.

API Usage (required)

EndpointCallsCredits
(each endpoint used)NN
TotalNN

Extract from meta.creditsConsumed per response. End with Credits remaining: N.

API Budget

Full Scan: ~28-35 credits (all 11 endpoints via composite). Quick Check: ~5-10 credits (realtime/​product Γ— N ASINs).

More skills from SerendipityOneInc

amazon-market-entry-analyzer logo
SerendipityOneInc/APIClaw-Skills

amazon-market-entry-analyzer

One-click market viability assessment for Amazon sellers. Analyzes market size, competition intensity, brand landscape, pricing structure, and consumer pain points to deliver a GO/CAUTION/AVOID recommendation. Uses all 11 ZooData API endpoints with cross-validation for data-backed decisions. Use ...

75 0
View
amazon-analysis logo
SerendipityOneInc/APIClaw-Skills

amazon-analysis

Full-Spectrum Research & Seller Intelligence. Amazon seller data analysis tool. Features: market research, product selection, competitor analysis, ASIN evaluation, pricing reference, category research. Use when user asks about: Amazon market research, product selection, ASIN analysis, category re...

75 0
View
amazon-review-intelligence-extractor logo
SerendipityOneInc/APIClaw-Skills

amazon-review-intelligence-extractor

Deep consumer insights from 1B+ pre-analyzed Amazon reviews. Extracts pain points, buying factors, user profiles, usage patterns, and differentiation opportunities across 11 analysis dimensions. Compares review sentiment across competitors and generates listing copy suggestions. Uses all 11 ZooDa...

75 0
View
amazon-listing-audit-pro logo
SerendipityOneInc/APIClaw-Skills

amazon-listing-audit-pro

Comprehensive listing health check and optimization engine for Amazon sellers. Scores listings across 8 dimensions, benchmarks against category leaders, identifies keyword gaps, and generates data-backed improvement recommendations. Supports single ASIN or bulk audit (10-100+ ASINs for agencies)....

75 0
View
amazon-daily-market-radar logo
SerendipityOneInc/APIClaw-Skills

amazon-daily-market-radar

Automated daily Amazon market digest. Given the user's own ASINs (1-10) and any competitor ASINs they want included (up to 20), produces a daily change-detection briefing on Amazon: price moves, BSR shifts, new entrants in the surrounding category, review wave detection, stockout signals. Output ...

75 0
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgΓ€nger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View