nexscope-ai/nexscope-ecommerce-skills / ecommerce-shopify-store-query
ecommerce.shopify-store-query
VerifiedFilter Shopify standalone stores by multiple dimensions (store name/domain, country, years since creation, product count, ad count, monthly visits, monthly orders, social media followers, etc.). Triggered when users mention Shopify stores, Shopify store analysis, standalone stores, Shopify sellers, competitor standalone stores, Shopify monthly visits, standalone store ad library, shopify stores, or Shopify store query. Even if the user does not mention the tool name, this skill should be triggered whenever searching for stores, filtering store data, or analyzing store performance on Shopify standalone stores.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.5 KB |
| manifest.json | config | 281 B |
| references/api.md | markdown | 6.5 KB |
| scripts/shopify_store_query.py | script | 6.5 KB |
references/api.md
View on GitHub# Shopify Store Query API Reference
## Usage Notes
- **Gateway route**: `POST ehunt/shopify/storeQuery` (full: `${NEXSCOPE_PROXY_BASE}Query`).
- **MCP display name**: Shopify Store Query (the exact tool name is subject to the tool metadata deployed in the current environment).
- **Authentication**: Request header `Authorization: <api_key>`, api_key read from environment variable `NEXSCOPE_API_KEY` or `NEXSCOPE_API_KEY` (if not configured, follow the **## Resolving Authentication and Credits Issues** section in SKILL.md).
- **Note**: Business fields depend on the operation. Only the outer numeric platform `code: 0` indicates success; a nested business `code` does not replace it.
## Request Parameters (JSON)
| Parameter | Type | Required | Description |
|------|------|------|------|
| searchKey | string, maxLen=500 | No | Store name or domain keyword |
| country | string | No | Country code (e.g., US, CN) |
| year | integer | No | Store creation year: 1=Last 1 year, 2=1~2 years, 3=2~3 years, 4=3+ years |
| productNumMin | integer, >=0 | No | Product count range start |
| productNumMax | integer, >=0 | No | Product count range end |
| advertiseCountMin | integer, >=0 | No | Ad count range start |
| advertiseCountMax | integer, >=0 | No | Ad count range end |
| monthlyVisitMin | integer, >=0 | No | Monthly visits range start |
| monthlyVisitMax | integer, >=0 | No | Monthly visits range end |
| monthOrderMin | integer, >=0 | No | Monthly orders range start |
| monthOrderMax | integer, >=0 | No | Monthly orders range end |
| sortBy | integer | No | Sort field: 0=Product count, 1=Category count, 2=Monthly visits, 3=FB followers, 4=Ins followers, 5=Ad count, 6=Relevance, 7=Monthly orders (default) |
| orderBy | string | No | Sort direction: `desc` (default) / `asc` |
| page | integer, >=1, default 1 | No | Page number (starting from 1) |
| pageSize | integer, 1~100, default 20 | No | Results per page, max 100 |
## 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.
## Main Response Fields
| Field | Type | Description |
|------|------|------|
| total | integer | Number of results returned on this page |
| storeNum | integer | Total number of matching stores (upstream `store_num`) |
| stores | array | Shopify store list |
| columns | array | Columns for rendering |
| title | string | Title (`Shopify Store Query`) |
| sourceType | string | Source type: shopify |
| sourceTool | string | Tool type: ehunt |
| type | string | Render style: tableListWorkbenches |
### `stores[]` Elements
| Field | Upstream Alias | Description |
|------|----------|------|
| storeId | `store_id` | Store ID |
| shopId | `shop_id` | Shopify shop ID |
| storeName | `store_name` | Store name |
| storeDomain | `store_domain` | Store domain |
| storeLink | `store_link` | Store link |
| country | - | Country |
| createdTime | `created_time` | Creation time |
| productNum | `product_num` | Product count |
| categoryNum | `category_num` | Category count |
| categories | - | Category list (elements contain `id`, `name`) |
| monthlyVisit | `monthly_visit` | Monthly visits (formatted) |
| monthOrderNum | `month_order_num` | Monthly orders (formatted) |
| fbFollowers | `fb_followers` | Facebook followers |
| insFollowers | `ins_followers` | Instagram followers |
| advertiseCount | `advertise_count` | Ad count |
| adLink | `ad_link` | Ad library link |
| email | - | Contact email |
| facebookUrl | `facebook_url` | Facebook page |
| instagramUrl | `instagram_url` | Instagram page |
| socialLinks | `social_links` | Social media links (Map) |
| globalRank | `global_rank` | Global rank |
| logo | - | Store logo URL |
| availableStatus | `available_status` | Whether active: 1=Active |
## Script Debugging (Optional)
The repository provides **`scripts/shopify_store_query.py`** (Python 3, standard library only), which POSTs JSON matching the MCP input parameters to the Nexscope tool gateway.
- **Gateway**: `${NEXSCOPE_PROXY_BASE}/api/v1/tools/research/ehunt/shopify/storeQuery` (can override root URL with `NEXSCOPE_PROXY_BASE_BASE`)
- **Authentication**: Environment variable `NEXSCOPE_API_KEY` (same as other `nexscope-*` skills; if not configured, follow the **## Resolving Authentication and Credits Issues** section in SKILL.md)
```bash
export NEXSCOPE_API_KEY="<your-key>"
python scripts/shopify_store_query.py '{"searchKey": "fashion", "country": "US", "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 |