nexscope-ai/nexscope-ecommerce-skills / ecommerce-amazon-product-discovery
ecommerce.amazon-product-discovery
VerifiedAmazon product discovery and potential bestseller mining via Nexscope data. Triggered when users mention product mining, potential bestsellers, high-conversion product selection, click growth analysis, market growth opportunities, keyword-based product selection, FBA profit screening, niche market product discovery, seller origin filtering, Nexscope data, FBA profitability screening, keyword-based product selection. Even if users do not explicitly mention "Nexscope", this skill should be triggered whenever the task involves keyword-driven Amazon product selection based on conversion rates, click volume, and profitability metrics.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.9 KB |
| manifest.json | config | 273 B |
| references/api.md | markdown | 8.9 KB |
| scripts/amazon_product_discovery.py | script | 6.6 KB |
references/api.md
View on GitHub# Jimore Amazon Product Discovery API Reference
## API Specification
- **Endpoint**: `${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/jiimore/productDiscovery`
- **HTTP Method**: POST, Content-Type: application/json
- **Authentication**: Header `Authorization: <api_key>`, read api_key from environment variable `NEXSCOPE_API_KEY` or `NEXSCOPE_API_KEY` (if not configured, follow **## Resolving Authentication and Credit Issues** in SKILL.md)
## Request Parameters
POST Body (JSON):
### Required Parameters
| Parameter | Type | Required | Description |
|------|------|------|------|
| keyword | string | Yes | Keyword (required; translate the keyword to the language of the selected country) |
### Filter Parameters
| Parameter | Type | Required | Description |
|------|------|------|------|
| countryCode | string | No | Country, use country abbreviation. Default `US`. Options: `US`, `JP`, `DE` |
| priceMin | number | No | Minimum product price |
| priceMax | number | No | Maximum product price |
| totalReviewsMin | integer | No | Minimum number of reviews |
| totalReviewsMax | integer | No | Maximum number of reviews |
| customerRatingMin | number | No | Minimum rating |
| customerRatingMax | number | No | Maximum rating |
| clickConversionRateMin | number | No | Minimum click-to-purchase conversion rate, value range 0-1, 0.1 means 10% |
| clickConversionRateMax | number | No | Maximum click-to-purchase conversion rate, value range 0-1, 0.1 means 10% |
| clickConversionRateCompositeMin | number | No | Minimum composite conversion rate, value range 0-1, 0.1 means 10% |
| clickConversionRateCompositeMax | number | No | Maximum composite conversion rate, value range 0-1, 0.1 means 10% |
| clickCountT7Min | integer | No | Minimum weekly click count |
| clickCountT7Max | integer | No | Maximum weekly click count |
| clickCountT30Min | integer | No | Minimum monthly click count |
| clickCountT30Max | integer | No | Maximum monthly click count |
| clickCountGrowthT7Min | number | No | Minimum weekly click growth rate, value range 0-1, 0.1 means 10% |
| clickCountGrowthT7Max | number | No | Maximum weekly click growth rate, value range 0-1, 0.1 means 10% |
| clickCountGrowthT30Min | number | No | Minimum monthly click growth rate, value range 0-1, 0.1 means 10% |
| clickCountGrowthT30Max | number | No | Maximum monthly click growth rate, value range 0-1, 0.1 means 10% |
| salesVolumeT360Min | integer | No | Minimum annual sales volume |
| salesVolumeT360Max | integer | No | Maximum annual sales volume |
| grossProfitMarginMin | number | No | Minimum gross profit margin |
| grossProfitMarginMax | number | No | Maximum gross profit margin |
| fbaFeeMin | number | No | Minimum FBA fee |
| fbaFeeMax | number | No | Maximum FBA fee |
| launchDateMin | string | No | Earliest listing time, format: `yyyyMMdd000000` |
| launchDateMax | string | No | Latest listing time, format: `yyyyMMdd000000` |
| nicheCountMin | integer | No | Minimum niche market count |
| nicheCountMax | integer | No | Maximum niche market count |
| sellerCountry | string | No | Seller country/region code, comma-separated for multiple selections, e.g.: `CN,US` |
### Sorting and Pagination
| Parameter | Type | Required | Description |
|------|------|------|------|
| sortField | string | No | Sort field. Default `purchasedClicksT360`. Options: `totalReviews` (total reviews), `price` (price), `launchDate` (listing time), `clickCountT7` (7-day click count), `clickCountT30` (30-day click count), `clickCountT90` (90-day click count), `clickConversionRate` (click-to-purchase conversion rate), `clickConversionRateComposite` (composite click-to-purchase conversion rate), `customerRating` (rating), `purchasedClicksT360` (360-day purchase clicks), `clickCountGrowthT7` (weekly click growth rate), `clickCountGrowthT30` (monthly click growth rate), `currentPrice` (current price), `fbaFee` (FBA fee), `shippingFee` (FBA shipping), `gpm` (gross profit margin) |
| sortType | string | No | Sort direction. Default `desc`. Options: `desc` (descending), `asc` (ascending) |
| page | integer | No | Page number. Default `1` |
| pageSize | integer | No | Items per page (10-100). Default `50` |
## Nexscope response envelope
These research endpoints return a platform object with numeric `code`, nullable `msg`, and business `data`. Only outer `code: 0` means success; `200`, string codes, missing codes, and HTTP 200 alone do not. A nonzero code is a platform error: show `msg` and do not interpret the payload as a successful result.
`msg` preserves the upstream message when available; Chinese messages are translated to English by Nexscope. A successful response without a message has `msg: null`. Do not infer success or retry behavior from the message text. On both success and failure, the direct fields `code`, `errcode`, `errorCode`, `msg`, `errmsg`, `message`, and `errorMsg` are removed from public `data`. Read the message only from outer `msg`; deeper business fields are preserved, including nested `code` and `status`.
Business field tables and abbreviated business examples below describe `data`, unless explicitly labeled as a complete platform response. For example, a business `products` field is at HTTP `data.products`, and a business `data` array is at HTTP `data.data`. The research endpoints already had this outer envelope; no additional wrapper is added.
```json
{"code":0,"msg":null,"data":{}}
```
Metadata includes string `ts` (epoch milliseconds), string `cost` (elapsed milliseconds, not credits), `time`, and nullable `traceId`. Handle network/HTTP failures before the platform code; gateway failures may not be platform JSON. Keep the existing billing-header guidance separate from elapsed time.
## Response Structure
| Field | Type | Description |
|------|------|------|
| total | integer | Total count |
| sourceTool | string | Tool type: `jiimore` |
| sourceType | string | Source type: `amazon` |
| type | string | Render style |
| title | string | Title |
| costToken | integer | Token consumption |
| columns | array | Rendered columns |
| products | array | Product list (see below) |
### Product Object Fields
| Field | Type | Description |
|------|------|------|
| asin | string | Amazon product ASIN |
| parentAsin | string | Amazon product parent ASIN |
| title | string | Product title |
| brand | string | Brand |
| price | number | Price |
| imageUrl | string | Product main image |
| productImageUrls | array | Product image URL list |
| asinUrl | string | ASIN link |
| ratings | integer | Number of reviews |
| availableDate | string | Listing time (timestamp) |
| availableDateString | string | Listing date (string) |
| categoryNames | array | Category information |
| marketplaceId | string | Site ID |
| clickCountT7 | integer | Weekly click count |
| clickCountT30 | integer | Monthly click count |
| clickCountT90 | integer | Quarterly click count |
| clickConversionRate | number | Click-to-purchase conversion rate |
| clickConversionRateComposite | number | Composite conversion rate |
| grossProfitMargin | number | Gross profit margin |
| fbaFee | number | Amazon fee |
| shippingFee | number | FBA shipping fee |
| sourceTool | string | Tool type: `jiimore` |
| sourceType | string | Source type: `amazon` |
## Error Codes
HTTP 200 does not prove business success. Read only the numeric outer platform `code`: `0` succeeds and any other value fails. Show outer `msg`; never test removed provider codes or nested business `code` as the platform status. Authentication, permissions, balance, and validation failures may be platform errors even with HTTP 200; also handle non-2xx HTTP and non-JSON responses.
### Recovery guidance
| Condition | Action |
|---|---|
| Authentication failed | HTTP 401 or authorized error: follow **## Resolving Authentication and Credit Issues** in SKILL.md. |
| Insufficient balance | HTTP 402: follow **## Resolving Authentication and Credit Issues** in SKILL.md. |
## curl Example
```bash
curl -X POST ${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/jiimore/productDiscovery \
-H "Authorization: Bearer ${NEXSCOPE_API_KEY}" \
-H "Content-Type: application/json" \
-d '{
"keyword": "wireless charger",
"countryCode": "US",
"clickConversionRateMin": 0.1,
"priceMin": 10,
"priceMax": 50,
"sortField": "clickConversionRate",
"sortType": "desc",
"page": 1,
"pageSize": 20
}'
```
---
## API Key request rate and retries
All API Keys of one Nexscope user share the public API execution request-rate allowance, measured in any rolling 1-second window. The allowed RPS depends on that user's entitlements; it is not a universal 1 RPS. One Skill operation may issue multiple public API requests, each of which uses the allowance.
HTTP 429 with Nexscope outer code `13012` means request-rate exhaustion: honor the response's `Retry-After`. Outer code `13013` means concurrent-request exhaustion, not rate exhaustion; honor `Retry-After` when supplied. Check the HTTP status and outer JSON code separately. Do not automatically replay writes or requests with uncertain outcomes; first reconcile the operation's state.
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: 472k | 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 |