nexscope-ai/nexscope-ecommerce-skills / ecommerce-walmart-product-detail
ecommerce.walmart-product-detail
VerifiedQuery Walmart product details via Nexscope, including pricing history and sales trends. Trigger when users mention Walmart product detail, Walmart product data, Nexscope, Walmart price trends, Walmart sales trends, Walmart product detail, Walmart price history, Walmart sales trend, Nexscope product. Even if the user does not explicitly mention "Nexscope", trigger this skill whenever their need involves viewing detailed information, historical price changes, or sales trends for a single Walmart product.
Nexscope Product Detail
This skill retrieves detailed product information from Walmart via Nexscope, including pricing history and sales volume trends.
Core Concepts
Nexscope Product Detail looks up a single Walmart product by its ItemId and returns comprehensive product attributes along with historical pricing and sales data. This is a product-level deep-dive tool, complementing the broader Walmart search skill that operates at the search/listing level.
Data scope: Returns current product attributes (title, price, brand, ratings, fulfillment type, etc.) plus historical stats when includeStats is enabled (default).
Non-structured output: The tool returns mixed structured and non-structured data. It does NOT support secondary analysis via data query.
Parameter Guide
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| productId | integer | Yes | -- | Walmart Item ID. Found in product URLs: https://www.walmart.com/ip/<productId> |
| includeStats | boolean | No | true | Whether to include historical price and sales data |
Product Data Fields
| Field | Description |
|---|---|
| title | Product title |
| description | Product description |
| price | Current selling price (USD) |
| wasPrice | Strikethrough price (USD) |
| minPrice | Lowest price (USD) |
| brand | Brand name |
| rating | Average rating (0.0--5.0) |
| reviews | Total review count |
| salesEstimate | Estimated sales volume (units) |
| revenue | Estimated revenue (USD) |
| sellerName | Seller name |
| fulfillmentType | Fulfillment: MARKETPLACE or WFS |
| productPageUrl | Product page URL |
| imageUrl | Product image URL |
| departmentName | Department category name |
| departmentId | Department ID |
| listingScore | Listing quality score |
| contentScore | Content quality score |
| outOfStock | Stock status: 0=in stock, 1=out of stock |
| sponsored | Ad flag: 0=organic, 1=sponsored |
| isBranded | Brand flag: 0=no, 1=yes |
| multipleOptionsAvailable | Variant flag: 0=no, 1=yes |
| usItemId | Internal US Item ID |
| createdAt | Product creation timestamp |
| updatedAt | Last update timestamp |
| stats | Historical price and sales trend data object |
Usage Examples
1. Basic product lookup (with history) Get full details for a Walmart product including price and sales trends:
{"productId": 5177343351}
2. Product detail only (no history) Get product attributes without historical data for faster response:
{"productId": 5169493923, "includeStats": false}
Display Rules
- Present data clearly: Show product details in a structured format. Do not add subjective business recommendations unless asked.
- Price formatting: Display current price alongside wasPrice when available to highlight discounts. Always show USD symbol.
- Trend summary: When stats data is available, summarize price and sales trends (e.g., "Price dropped 15% over the last 30 days").
- Score context: Explain listingScore and contentScore in context (higher = better quality listing).
- Stock and fulfillment: Clearly flag out-of-stock items and fulfillment type (WFS vs Marketplace).
- Single product: This tool queries one product at a time. If the user needs multiple products, call the tool separately for each ItemId.
Important Limitations
- Only supports lookup by Walmart ItemId (the numeric ID in the product URL)
- Returns non-structured data -- NOT compatible with secondary data analysis tools
- Single ItemId per call; batch queries require multiple invocations
- Historical data availability depends on Nexscope's tracking coverage
User Expression & Scenario Quick Reference
Applicable -- Walmart single-product deep-dive:
| User Says | Scenario |
|---|---|
| "Look up this Walmart product detail" | Basic product lookup |
| "What's the recent price trend for this Walmart product" | Price trend analysis |
| "Nexscope look up Walmart product 5177343351" | Direct ID lookup |
| "How are sales for this Walmart product" | Sales estimate check |
| "Walmart product detail for item XX" | English variant |
| "Has this Walmart product dropped in price recently" | Price change detection |
Not applicable -- Needs beyond single product detail:
- Walmart product search by keyword (use the Walmart search skill)
- Bulk product comparison across multiple items simultaneously
- Walmart seller account or advertising metrics
- Real-time inventory or delivery estimates
- Category-level market analysis
Boundary judgment: If the user has a specific Walmart product ID or URL and wants detailed attributes, pricing history, or sales trends, this skill applies. If they want to search/browse products by keyword or category, use the Walmart search skill instead.
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 |