Amazon Product Research

Amazon Product Research & Seller Intelligence

A skill for Amazon sellers who need market validation, category analysis, product selection, competitor research, ASIN reviews, pricing guidance, and complete research reports.

It uses APIClaw (apiclaw.io) as its data source, while keeping the focus on structured research workflows and actionable seller decisions.

What this skill is good at

This skill is best for:

• product discovery: finding promising product opportunities
• market validation: deciding whether a niche or category is worth entering
• category analysis: understanding concentration, pricing, brand density, and new-SKU activity
• competitor research: comparing leading products, brands, and listings
• ASIN diagnostics: breaking down a specific product in detail
• pricing and positioning: recommending a launch range and market angle
• report generation: combining multiple endpoints into a structured market report

Credentials

• Required credential: APICLAW_API_KEY
• Purpose: authenticate requests to the APIClaw API
• Scope: used only for https://api.apiclaw.io
• No other credentials are required by this skill

Quick start

This skill requires one credential: APICLAW_API_KEY. Create it at APIClaw and configure it before running research workflows.

You can ask questions like:

1. "Is the pet supplies market worth entering?"
2. "Analyze ASIN B09V3KXJPB"
3. "Find Amazon products with low review counts but strong sales"
4. "Compare the top competitors in this category"
5. "Generate a full market research report"

File map

Context discipline

• Start with this file
• Load only one additional module at a time when possible
• Use openapi-reference.md only when exact fields or filters matter
• Prefer fewer, larger, high-value calls over many tiny calls

Intent routing

Safety and scope

• This is an instruction-focused research skill
• It does not install software, request unrelated secrets, or require elevated privileges
• It uses network access only when the user invokes APIClaw-backed research workflows
• Its external data dependency is the APIClaw API

API configuration

Example request

curl -s -X POST "https://api.apiclaw.io/openapi/v2/{endpoint}" \
  -H "Authorization: Bearer $APICLAW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ ...params... }'

Endpoint overview

Core workflow patterns

1. Market validation

Use:

• categories → confirm category path
• markets/search → inspect demand, price, concentration, and new-SKU rate
• products/search → inspect top products for brand and price structure

Use this when the user asks:

• "Is this category worth entering?"
• "Which niche has room?"
• "Compare these categories"

2. Product discovery

Use:

• categories → confirm category path if needed
• products/search → filter for product opportunities
• realtime/product → validate a shortlist

Use this when the user asks:

• "Find products for me"
• "What should I sell?"
• "Show low-competition opportunities"

3. Competitor analysis

Use:

• products/competitor-lookup → pull the competitor set
• realtime/product → inspect leaders in detail

Use this when the user asks:

• "Analyze competitors"
• "Compare these listings"
• "Why is this product winning?"

4. ASIN evaluation

Use:

• realtime/product → inspect listing, specs, variants, review structure
• products/competitor-lookup → add market context

Use this when the user asks:

• "Analyze this ASIN"
• "Break down this product"
• "What is weak about this listing?"

5. Pricing and positioning

Use:

• markets/search → category-level price signals
• products/search → top product price bands
• realtime/product → inspect how top listings frame value

Use this when the user asks:

• "How should I price this?"
• "What price band makes sense?"
• "Should I position this as premium or value?"

High-value filters to remember

For markets/search

Most useful fields:

• sampleAvgMonthlySales
• sampleAvgMonthlyRevenue
• sampleAvgPrice
• sampleAvgReviewCount
• sampleBrandCount
• sampleSellerCount
• sampleFbaRate
• sampleAmzRate
• sampleNewSkuRate
• topSalesRate
• topBrandSalesRate
• topSellerSalesRate

For products/search

Most useful filters:

• monthlySalesMin/Max
• salesGrowthRateMin/Max
• priceMin/Max
• ratingMin/Max
• reviewCountMin/Max
• listingAge
• variantCountMin/Max
• sellerCountMin/Max
• includeBrands / excludeBrands
• fulfillment
• badges
• excludeKeywords

Common product-discovery pattern

High demand / low review barrier:

{
  "monthlySalesMin": 300,
  "reviewCountMax": 50,
  "listingAge": "180"
}

Fast-growing products:

{
  "monthlySalesMin": 300,
  "salesGrowthRateMin": 0.1
}

New-product watchlist:

{
  "listingAge": "180",
  "badges": ["New Release"]
}

Reporting guidance

When generating output, prefer a decision-oriented structure:

1. What the market or product is
2. What the data suggests
3. What the main risks are
4. What the recommendation is
5. What the next action should be

For reports, include tables such as:

• top products
• brand distribution
• price bands
• concentration metrics
• opportunity score breakdown

Recommended next-file loading rules

Load these files only when needed:

• 01-market-selection.md → category-first and market-entry questions
• 02-product-selection.md → product shortlisting and discovery
• 03-competitor-analysis.md → competitor-focused questions
• 04-product-evaluation.md → single-product or ASIN evaluation
• 05-pricing-listing.md → pricing and listing strategy
• 06-daily-operations.md → monitoring and recurring reviews
• 07-expansion.md → adjacent category or follow-on product ideas
• workflow-full-market-report.md → complete market report generation
• workflow-product-opportunity.md → product opportunity shortlisting workflow
• openapi-reference.md → exact API field and filter reference

Final guidance

This skill is strongest when used for research, evaluation, and decision support. It is not a seller ERP or execution engine. Use it to answer questions such as:

• What market should I enter?
• What products should I test?
• Who are the real competitors?
• What are the price bands and positioning gaps?
• What is weak about a specific ASIN?
• What report should I generate for a seller or team?