Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
linkfox-ai avatar

Linkfox Wallysmarter Product Detail

  • 230 installs
  • 64 repo stars
  • Updated August 3, 2026
  • linkfox-ai/linkfox-skills

Helps with ai & agent building tasks.

About

linkfox-wallysmarter-product-detail is a Claude Code skill in the AI & Agent Building category.

  • linkfox-wallysmarter-product-detail
  • AI & Agent Building
  • AI-coding skill

Linkfox Wallysmarter Product Detail by the numbers

  • 230 all-time installs (skills.sh)
  • +35 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #2,670 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/linkfox-ai/linkfox-skills --skill linkfox-wallysmarter-product-detail

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs230
repo stars64
Last updatedAugust 3, 2026
Repositorylinkfox-ai/linkfox-skills

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

WallySmarter Product Detail

This skill retrieves detailed product information from Walmart via WallySmarter, including pricing history and sales volume trends.

Core Concepts

WallySmarter 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 linkfox-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 @智能数据查询.

Parameter Guide

ParameterTypeRequiredDefaultDescription
productIdintegerYesWalmart Item ID. Found in product URLs: https://www.walmart.com/ip/<productId>
includeStatsbooleanNotrueWhether to include historical price and sales data

Product Data Fields

FieldDescription
titleProduct title
descriptionProduct description
priceCurrent selling price (USD)
wasPriceStrikethrough price (USD)
minPriceLowest price (USD)
brandBrand name
ratingAverage rating (0.0–5.0)
reviewsTotal review count
salesEstimateEstimated sales volume (units)
revenueEstimated revenue (USD)
sellerNameSeller name
fulfillmentTypeFulfillment: MARKETPLACE or WFS
productPageUrlProduct page URL
imageUrlProduct image URL
departmentNameDepartment category name
departmentIdDepartment ID
listingScoreListing quality score
contentScoreContent quality score
outOfStockStock status: 0=in stock, 1=out of stock
sponsoredAd flag: 0=organic, 1=sponsored
isBrandedBrand flag: 0=no, 1=yes
multipleOptionsAvailableVariant flag: 0=no, 1=yes
usItemIdInternal US Item ID
createdAtProduct creation timestamp
updatedAtLast update timestamp
statsHistorical 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

1. Present data clearly: Show product details in a structured format. Do not add subjective business recommendations unless asked. 2. Price formatting: Display current price alongside wasPrice when available to highlight discounts. Always show USD symbol. 3. Trend summary: When stats data is available, summarize price and sales trends (e.g., "Price dropped 15% over the last 30 days"). 4. Score context: Explain listingScore and contentScore in context (higher = better quality listing). 5. Stock and fulfillment: Clearly flag out-of-stock items and fulfillment type (WFS vs Marketplace). 6. 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 @智能数据查询 for secondary analysis
  • Single ItemId per call; batch queries require multiple invocations
  • Historical data availability depends on WallySmarter's tracking coverage

User Expression & Scenario Quick Reference

Applicable — Walmart single-product deep-dive:

User SaysScenario
"查一下这个Walmart商品的详情"Basic product lookup
"这个沃尔玛产品最近价格走势如何"Price trend analysis
"WallySmarter查Walmart商品5177343351"Direct ID lookup
"沃尔玛这个产品销量怎么样"Sales estimate check
"Walmart product detail for item XX"English variant
"这个Walmart产品最近有没有降价"Price change detection

Not applicable — Needs beyond single product detail:

  • Walmart product search by keyword (use linkfox-walmart-search)
  • 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 linkfox-walmart-search instead.

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply: 1. The functionality or purpose described in this skill does not match actual behavior 2. The skill's results do not match the user's intent 3. The user expresses dissatisfaction or praise about this skill 4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.

<!-- LF_LARGE_RESPONSE_BLOCK -->

Handling Large Responses

To avoid overflowing the agent context, persist the response to disk and extract only the fields you need:

python scripts/response_io.py run --script scripts/wallysmarter_product_detail.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>"   # or --path "<JMESPath>"
Pick --out-dir outside any git working tree (e.g. /tmp/... on Unix, %TEMP%/... on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done.

run writes the full response to a file and emits only a schema preview + file path. read projects specific fields, with --limit/--offset for slicing and --format json|jsonl|csv|table for output.

When to prefer this pattern — apply your judgment based on the response characteristics, e.g.:

  • High field count per record, or fields you don't need
  • Batch/paginated results (multiple items per call)
  • Long-text fields (descriptions, reviews, HTML, time series)
  • Output reused across later steps rather than consumed immediately

For small, single-use responses, calling the main script directly is fine.

⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via read. <!-- /LF_LARGE_RESPONSE_BLOCK -->

--- For more high-quality, professional cross-border e-commerce skills, visit [LinkFox Skills](https://skill.linkfox.com/).

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.