nexscope-ai/nexscope-ecommerce-skills / ecommerce-temu-product-source-query
ecommerce.temu-product-source-query
VerifiedFilter Temu products by multiple dimensions (keyword/product ID/store ID, front/backend categories, price, rating, reviews, total/weekly/daily sales, listing date, fully-managed/semi-managed, semi-managed regions, tags, etc.). Triggered when users mention Temu products, Temu product selection, Pinduoduo cross-border, Temu bestsellers, Temu semi-managed, fully-managed products, Temu product query, or temu items. Even if the user does not mention the tool name, this skill should be triggered whenever searching for products, viewing sales/ratings/prices, or filtering products on Temu.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.7 KB |
| manifest.json | config | 239 B |
| references/api.md | markdown | 7.1 KB |
| scripts/temu_product_source_query.py | script | 6.6 KB |
SKILL.md
View on GitHub---
name: ecommerce.temu-product-source-query
description: Filter Temu products by multiple dimensions (keyword/product ID/store ID, front/backend categories, price, rating, reviews, total/weekly/daily sales, listing date, fully-managed/semi-managed, semi-managed regions, tags, etc.). Triggered when users mention Temu products, Temu product selection, Pinduoduo cross-border, Temu bestsellers, Temu semi-managed, fully-managed products, Temu product query, or temu items. Even if the user does not mention the tool name, this skill should be triggered whenever searching for products, viewing sales/ratings/prices, or filtering products on Temu.
---
# Temu Product Query
## Quick Reference
- **Pagination**: `page` starts at 1; `pageSize` defaults to 20, max 100 (recommended <= 50).
- **Range parameters**: `*Begin` / `*End` come in pairs (price, rating, reviews, total/weekly/daily sales, listing date), forming upstream ranges.
- **Categories**: `categoryHome` frontend category ID, `categoryBackend` backend category ID; use Temu Category Search first to get the ID.
- **Fulfillment mode**: `isLocal` (0=fully-managed, 1=semi-managed); for semi-managed, use `region` to specify regions (multiple separated by commas).
- **Listing status**: `soldOut` (0=active, 1=delisted).
- **Tags**: `tags` / `customTags` -- multiple separated by commas.
- **Sorting**: `sortBy` is a "field-direction" string, e.g., `order_week-0` (weekly sales descending, default), `price-0`, `order_total-0`, `rating-0`.
## Script (Optional)
Command-line debugging: `python scripts/temu_product_source_query.py '<JSON>'` (requires `NEXSCOPE_API_KEY`). See [references/api.md](references/api.md) for details.
## Reference
See [references/api.md](references/api.md) for input/output parameter tables.
## Authentication
Set `NEXSCOPE_API_KEY`. Visit https://www.nexscope.ai/help/skills-external-access?co-from=skillNS to manage 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: 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 |