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

Linkfox Sellersprite Market Statistics

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

Retrieve SellerSprite Amazon market statistics to size categories, estimate demand, and compare segment growth before picking a storefront focus.

About

Integrates SellerSprite market statistics for Amazon categories: volume, growth, competition, and revenue proxies. Gives agents data-backed niche sizing during ideation so ecommerce brands choose segments with adequate demand and manageable rivalry.

  • SellerSprite market stats
  • Amazon category sizing
  • segment growth trends
  • competitive concentration metrics
  • niche comparison tables

Linkfox Sellersprite Market Statistics by the numbers

  • 243 all-time installs (skills.sh)
  • +38 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #275 of 853 Sales & Marketing 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-sellersprite-market-statistics

Add your badge

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

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

What it does

Retrieve SellerSprite Amazon market statistics to size categories, estimate demand, and compare segment growth before picking a storefront focus.

Files

SKILL.mdMarkdownGitHub ↗

SellerSprite Market Statistics

This skill helps fetch node-level market statistics for Amazon categories via SellerSprite.

Core Concepts

  • 节点统计:对指定类目节点做聚合统计,不返回完整商品明细。
  • TopN 口径topN 决定头部商品统计样本数量(默认 10)。
  • 新品定义newProduct 指定“新品”按最近 N 个月定义(默认 6)。

API Usage

  • Endpoint: POST https://tool-gateway.linkfox.com/sellersprite/market/statistics
  • Auth: Header Authorization: <api_key> (LINKFOXAGENT_API_KEY)
  • 完整说明见 references/api.md:含 marketplace / month 规则,必填 nodeIdPathtopN/newProduct 默认值;响应含 data[] 中市场整体、hl* 头部、new* 新品与上架日期等全部字段(与 _sellersprite_market_statisticsoutputSchema 一致)。
  • Runnable script: scripts/sellersprite_market_statistics.py

Parameters

参数类型必填说明
marketplacestring站点编码,默认 US
nodeIdPathstring节点ID路径,如 1064954:1069242:...
monthstringnearlyyyyyMM
topNinteger头部样本数,默认 10
newProductinteger新品定义(月),默认 6

Usage Example

{
  "marketplace": "US",
  "nodeIdPath": "172282:281407",
  "month": "nearly",
  "topN": 10,
  "newProduct": 6
}

Display Rules

1. 明确展示统计口径:topNnewProduct、时间范围。 2. 先输出关键总览指标,再输出扩展字段。 3. 若用户未给 nodeIdPath,先引导用户提供节点路径或先做类目定位。

Important Limitations

  • 必填参数:marketplacenodeIdPath
  • nodeIdPath 必须为合法节点路径
  • 月份查询受第三方历史范围限制

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/sellersprite_market_statistics.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 -->

Related skills

Sales & Marketingecommercepricing

This week in AI coding

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

unsubscribe anytime.