nexscope-ai/nexscope-ecommerce-skills / ecommerce-shopee-product-detail
ecommerce.shopee-product-detail
VerifiedRetrieve the current public details of one Shopee listing from a supported product URL, including price, discount, sales, stock, variants, media, brand, category, shop, and rating data. Use when a user provides a Shopee product URL and asks for listing details, SKU variants, inventory, pricing, or competitor-page analysis. Do not use for keyword search, historical trends, reviews, or seller-account operations.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.4 KB |
| manifest.json | config | 448 B |
| references/api.md | markdown | 5.7 KB |
| references/testing.md | markdown | 3.9 KB |
| scripts/shopee_product_detail.py | script | 9.9 KB |
references/testing.md
View on GitHub# Testing evidence for `ecommerce.shopee-product-detail`
## Required user information
- One direct public Shopee product URL on a supported marketplace.
- The URL must contain numeric shop and item IDs in the `-i.<shopId>.<itemId>` suffix.
- No seller-account authorization is required; the Nexscope API key and sufficient credits are required to call the gateway.
## English prompt coverage
1. Basic: `Look up this Shopee product and show its current price, stock, sold count, rating, and shop: https://shopee.sg/example-i.9641401.29691169956`
2. Filtered: `From this Shopee Malaysia listing, show only the current and original prices, discount, total stock, and official-store signals: https://shopee.com.my/example-i.123456.789012`
3. Advanced: `Analyze this Shopee listing as a competitor page. Summarize its identity and shop, then tabulate all returned SKU models and variant stock, and show up to three images: https://shopee.ph/example-i.123456.789012`
Expected routing: all three prompts select `ecommerce.shopee-product-detail`, make at most one call for the supplied URL, and present only fields returned by the service.
## Error tests
- `{}`: reject because `productUrl` is required.
- `{"productUrl":"not-a-url"}`: reject before network access.
- `{"productUrl":"http://shopee.sg/example-i.1.2"}`: reject because HTTPS is required.
- `{"productUrl":"https://example.com/example-i.1.2"}`: reject because the host is unsupported.
- `{"productUrl":"https://shopee.sg/product/1/2"}`: reject because the required suffix is missing.
- Extra top-level parameters: reject to preserve the one-parameter public contract.
## Evidence
- [x] Static package validation: frontmatter, manifest file list, endpoint prefix, JSON, Python syntax, and `git diff --check` verified locally on 2026-08-27 with `python -m unittest transfer/script/test_shopee_product_detail_staging.py` and focused shell checks. The bundled `quick_validate.py` could not run because PyYAML is absent from both available Python runtimes.
- [x] Offline mock request: request URL, method, authorization, tracing headers, JSON body, 150-second timeout, response parsing, ID matching, cache, and disk-output location verified locally on 2026-08-27 by `transfer/script/test_shopee_product_detail_staging.py`.
- [x] Sandbox or test-environment request: one paid `curl` call to the Nexscope test gateway succeeded on 2026-08-27 with HTTP 200, outer `code=0`, inner `data.errcode=200`, one product, and matching `shopId=9641401` / `itemId=29691169956`. Evidence: `transfer/test-results/shopee-product-detail-curl.json`. The test also found that the gateway wraps the documented business payload in an outer Nexscope `code/data` envelope; the migrated client currently expects top-level `errcode/data` and therefore requires a compatibility fix before final acceptance.
- [ ] Real-account request: not run; this is a paid call and no production call was authorized.
- [ ] ZIP import and installation: not run; the user requested staging migration and tests, not packaging/import.
- [x] English trigger and output review: the three prompts above and the display rules were reviewed locally on 2026-08-27.
Unchecked items are not failures; they remain unverified. Never mark connected-environment or paid-call evidence complete without durable output from that environment.
## NEX-198 validation evidence
- Static/frontmatter/manifest and offline Mock checks: passed.
- Previously saved test Curl: HTTP 200, outer `code=0`, inner `errcode=200`, requested entity matched.
- External Curl did not expose upstream billing headers; backend monitoring `response.headers` supplied array-valued evidence. `X-Cost-Token=105000`, calculated credits `109.305`, reported `X-Cost-Credit=53`, trace `b0b3a1605c608f1ce954a00dbc8670e9`. Do not substitute body `costToken`.
- ZIP/local install: passed in the isolated `transfer/test-results/public-ecommerce-migration/local-install/skills` root.
- Production publication: not performed.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |