nexscope-ai/nexscope-ecommerce-skills / ecommerce-amazon-market-research
ecommerce.amazon-market-research
VerifiedUse Nexscope market list capability to filter Amazon niche markets by category dimensions, supporting market size, competition, top concentration, seller structure, new product share, price/rating/margin ranges, and many other criteria for discovering viable markets and evaluating product selection directions. Trigger when the user mentions Amazon market research, niche category research, market opportunity screening, market concentration analysis, new product opportunities, market selection, Nexscope market research, category market research. Even if the user does not explicitly mention "Nexscope", if the need is to screen and evaluate Amazon markets by category dimensions, this skill should also be triggered.
Nexscope Market Research
This skill helps screen and rank Amazon category markets using Nexscope market-research data.
Core Concepts
- Category market-level analysis: Not a product-level list, but market profiles aggregated by category/node.
- Market size: Monthly average sales volume, monthly average revenue, product count, etc.
- Competition structure: Seller/brand concentration, top concentration, Amazon self-operated share, FBA/FBM share.
- Input scale: Filter parameters GoodsCrn / BrandCrn / SellerCrn / EbcProportion / FbaProportion / FbmProportion / AmazonSelfProportion (
min*/max*) must be 0~1 decimal values, see the parameter table below andreferences/api.md. - New product opportunities: New product count, new product share, new product average price/rating/sales, etc.
How to Invoke
- API Endpoint:
POST /sellersprite/market/research(complete params/response/error codes inreferences/api.md) - Python Script:
python scripts/amazon_market_research.py '<JSON params>' [--inline] - Cost constraint: This tool consumes credits; the same session and parameter combination is called only once by default, with a 24h local cache in the script. On failure or empty results, do not automatically retry with different keywords, pagination, or postal codes; inform the user about additional consumption before continuing to search.
Output strategy (script default behavior):
- Always write the full response to
<cwd>/nexscope/<YYYY-MM-DD>/<session>/data/nexscope-sellersprite-market-research-<timestamp>.json(<cwd>is the working directory at script execution time, i.e. the current project directory in Claude Code;<session>is taken from theSESSION_IDenv var, auto-grouped by user task; do not write to /tmp, error if current directory is not writable) - Response body <= 8 KB: print full JSON to stdout after saving
- Response body > 8 KB: print only summary to stdout after saving (top-level fields, common counts like
total/costToken, length of largest list field + first 3 samples) - Add
--inlineto force full output to stdout (still saves to disk)
Data reading tip: Check the summary first to decide if it's enough; when specific fields are needed, prefer using jq or ConvertFrom-Json to extract from the saved json file on demand, avoiding loading the entire JSON into context.
Key Parameters
The endpoint filter options are consistent with the
_sellersprite_market_researchtool (70+); below is a commonly used subset. For complete parameters and output fields, seereferences/api.md.
| Parameter | Type | Required | Description |
|---|---|---|---|
| marketplace | string | Yes | Marketplace code, default US |
| month | string | No | nearly or yyyyMM |
| nodeIdPath | string | No | Category node path |
| departmentKeyword | string | No | Category keyword path |
| page / size | integer | No | Pagination, default 1/50, size max 200 |
| orderField / orderDesc | string/boolean | No | Sort field and direction; orderDesc defaults to true (descending) |
| minAvgRevenue / maxAvgRevenue | number | No | Monthly average revenue range |
| minAvgUnits / maxAvgUnits | integer | No | Monthly average sales range |
| minGoodsCount / maxGoodsCount | integer | No | Product count range |
| minGoodsCrn / maxGoodsCrn | number | No | Product concentration (decimal 0~1, e.g. 0.4 means 40%, do not use integer 40) |
| minSellerCrn / maxSellerCrn | number | No | Seller concentration (decimal 0~1) |
| minBrandCrn / maxBrandCrn | number | No | Brand concentration (decimal 0~1) |
| minAmazonSelfProportion / maxAmazonSelfProportion | number | No | Amazon self-operated share (decimal 0~1) |
| minFbaProportion / maxFbaProportion | number | No | FBA share (decimal 0~1) |
| minFbmProportion / maxFbmProportion | number | No | FBM share (decimal 0~1) |
| minEbcProportion / maxEbcProportion | number | No | A+ content share (decimal 0~1) |
| minNewProportion / maxNewProportion | number | No | New product share (scale may differ from above; check references/api.md / schema) |
| minAvgPrice / maxAvgPrice | number | No | Average price range |
| minAvgRating / maxAvgRating | number | No | Average rating range |
| minAvgProfit / maxAvgProfit | number | No | Average gross margin (%) |
Usage Example
{
"marketplace": "US",
"month": "nearly",
"minAvgRevenue": 10000,
"maxGoodsCrn": 0.4,
"minNewProportion": 10,
"maxSellerCrn": 0.5,
"orderField": "total_amount",
"orderDesc": true,
"page": 1,
"size": 50
}
Display Rules
- First present the top N market candidates, then show core metrics (market size, concentration, new product share).
- Input parameter echo:
GoodsCrn/BrandCrn/SellerCrn/EbcProportion/FbaProportion/FbmProportion/AmazonSelfProportionfilters use 0~1 decimal values; when presenting to users, convert to percentage (e.g., passing0.4can be expressed as "product concentration cap of 40%"). If fields in the responsedata[]still carry "(%)" fields, their scale may differ from input scale, and the response values take precedence. - Other ratios, gross margins, and similar field units should reference
references/api.md. - Display filter criteria echo so users can reproduce results.
- If results are too few or too many, suggest users adjust key thresholds (e.g., concentration, scale thresholds).
Important Limitations
- Required parameter:
marketplace - Maximum 200 records per page
- Historical month range is limited by the third party (typically last 24 months)
Authentication
Set the NEXSCOPE_API_KEY environment variable. If credentials are missing or expire, visit https://www.nexscope.ai/help/skills-external-access?co-from=skillNS to top up credits.
API Key request rate
All Nexscope API Keys belonging to the same user share one request-rate allowance for public API execution. The allowance is measured over any rolling 1-second window. Your RPS depends on your account entitlements; do not assume every user has a fixed 1 RPS. A single Skill operation may make multiple public API requests, and each request uses this allowance.
If an execution request returns HTTP 429 with outer code 13012, the request-rate allowance was exceeded. Honor the returned Retry-After before considering another request. Outer code 13013 means the concurrent-request limit was exceeded, not the rate limit; honor its Retry-After when supplied. Inspect the response and reconcile state before retrying. Never automatically replay a write operation or a request whose outcome is unclear.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |