Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Keepa Product History

v1.0.0

查询亚马逊商品的历史时序数据,包括价格走势、BSR(畅销排名)趋势、评分变化、卖家数量和月销量,支持多个亚马逊站点的任意ASIN。当用户提到价格历史、价格追踪、BSR历史、BSR趋势、历史定价、价格波动、Keepa数据、排名历史、降价提醒、秒杀历史价格、Buy Box价格趋势、优惠券价格、FBA/FBM价格对比、...

0· 82·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for linkfox-ai/linkfox-keepa-product-history.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Keepa Product History" (linkfox-ai/linkfox-keepa-product-history) from ClawHub.
Skill page: https://clawhub.ai/linkfox-ai/linkfox-keepa-product-history
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install linkfox-keepa-product-history

ClawHub CLI

Package manager switcher

npx clawhub@latest install linkfox-keepa-product-history
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
high confidence
Purpose & Capability
Name/description match the behavior: the skill queries time-series product data (Keepa-style) via a LinkFox tool gateway. Using an API key to call an external gateway is expected for this purpose. However, the skill metadata claims 'Required env vars: none' while both references/api.md and scripts/keepa_product_history.py require LINKFOXAGENT_API_KEY — an omission in declared requirements.
Instruction Scope
SKILL.md and the included script only instruct calling the documented LinkFox endpoint(s) and formatting/returning the response. There are no instructions to read unrelated local files, credentials, or system state. The trigger rules are broad (many keywords) but that is an invocation policy, not an instruction to access extra data.
Install Mechanism
This is instruction-only with a small helper script; there is no install spec that downloads or extracts code from arbitrary URLs. No installers or third-party packages are pulled in by the skill bundle itself.
!
Credentials
The runtime requires a secret API key (LINKFOXAGENT_API_KEY) to authenticate to https://tool-gateway.linkfox.com, but the skill metadata does not declare any required env vars or a primary credential. Asking for an API key to call the external service is proportionate to the stated purpose, but failing to declare it in the skill manifest is an inconsistency that could hide credential requirements or mislead users about what will be accessed.
Persistence & Privilege
The skill does not request always:true and has no install-time mechanisms that persist beyond the skill's own files. It doesn't modify other skills or system-wide configs. Autonomous invocation is allowed (platform default) but is not combined with elevated privileges.
What to consider before installing
This skill appears to genuinely call a LinkFox gateway to return Amazon/Keepa-style time-series data, but take these precautions before installing or enabling it: - The skill code and docs require an API key named LINKFOXAGENT_API_KEY, but the skill manifest claims no required env vars — ask the publisher to declare this in the manifest so you know what secrets are needed. - Only provide an API key you trust and that is scoped/minimized for this purpose. Do not reuse high-privilege keys (AWS, personal tokens, or keys used by other services). - Verify the endpoints and ownership: the tool gateway is https://tool-gateway.linkfox.com and feedback goes to https://skill-api.linkfox.com. Confirm these domains and the publisher are legitimate before sending sensitive data. - Because the skill calls an external service, avoid sending any personally identifiable or sensitive information in ASIN-related requests unless you trust the backend. - Prefer the author to add explicit manifest declarations (required env var and primary credential) and a homepage or publisher contact so you can verify provenance. Given the missing metadata and external API usage, treat the skill as suspicious until those inconsistencies are resolved.

Like a lobster shell, security has layers — review code before you run it.

latestvk97beqft1d2m9kw9z3y0mtzmxn841f4x
82downloads
0stars
1versions
Updated 3w ago
v1.0.0
MIT-0

Keepa Product Time-Series Data Explorer

This skill guides you on how to query and analyze Amazon product historical time-series data, helping Amazon sellers track price movements, BSR trends, rating changes, and other key product metrics over time.

Core Concepts

This tool provides historical time-series data for individual Amazon products (ASINs) powered by Keepa. It returns timestamped data points for various metrics, allowing trend analysis over a configurable time window (up to 365 days). Each query targets a single ASIN in a specific Amazon marketplace.

Time-series format: All data series are returned as arrays of {time, value} objects, where time is a timestamp and value is the metric at that point. BSR data includes a categoryName field along with a points array.

BSR logic: A smaller BSR value means a better sales rank. Rank 1 is the top-selling product in its category. When a user says "BSR improved", it means the numeric value decreased; "BSR dropped" means the value increased.

Available Data Series

SeriesParameterDescription
Buy Box Price(always returned)Buy Box price over time
Lowest New PriceshowPrice=1Lowest marketplace new item price
List PriceshowPriceList=1Strikethrough / list price
Deal PriceshowPriceDeal=1Lightning deal price
Prime Exclusive PriceshowPricePrime=1Prime-exclusive new item price
FBA PriceshowPriceFba=1Third-party FBA new item price
FBM PriceshowPriceFbm=1Third-party FBM new item price
Coupon PriceshowPriceCoupon=1Post-coupon Buy Box price
Main Category BSRshowBsrMain=1Best Sellers Rank in the main (root) category
Seller CountshowSellerCount=1Number of active sellers
Rating(always returned)Product star rating over time
Rating Count(always returned)Number of ratings over time
Monthly Sales(always returned)Monthly unit sales volume
Sub-category BSR(always returned)Best Sellers Rank in sub-categories

Supported Marketplaces

Domain IDMarketplace
1Amazon.com (US)
2Amazon.co.uk (UK)
3Amazon.de (Germany)
4Amazon.fr (France)
5Amazon.co.jp (Japan)
6Amazon.ca (Canada)
8Amazon.it (Italy)
9Amazon.es (Spain)
10Amazon.in (India)
11Amazon.com.mx (Mexico)
12Amazon.com.br (Brazil)

Default marketplace is 1 (US). Use domain=1 when the user does not specify a marketplace.

API Usage

This tool calls the LinkFox tool gateway API. See references/api.md for calling conventions, request parameters, and response structure. You can also execute scripts/keepa_product_history.py directly to run queries.

Parameter Guide

Required Parameters

  • asin: The Amazon Standard Identification Number to query. Only a single ASIN per request is supported.
  • domain: The Amazon marketplace domain ID (see table above). Always map the user's marketplace mention to the correct numeric ID.

Optional Parameters

  • days: Number of historical days to retrieve (1-365, default 90). Use 30 for short-term, 90 for medium-term, 365 for long-term analysis.
  • show* flags: Set any show* parameter to 1 to include that data series. By default, only the core series (Buy Box price, rating, rating count, monthly sales, sub-category BSR) are returned.

How to Choose Parameters

  1. Price analysis: Enable showPrice, showPriceList, showPriceDeal, showPriceCoupon as needed for the specific price comparison the user wants.
  2. FBA vs FBM comparison: Enable both showPriceFba and showPriceFbm.
  3. BSR deep-dive: Enable showBsrMain to get the root category BSR alongside the always-returned sub-category BSR.
  4. Competitive landscape: Enable showSellerCount to see how many sellers are competing.
  5. Full product overview: Enable all show flags for a comprehensive historical snapshot.

Usage Examples

1. Basic price history for a US product

asin: B0XXXXXXXX, domain: 1, days: 90

2. Long-term BSR trend (1 year) on the German marketplace

asin: B0XXXXXXXX, domain: 3, days: 365, showBsrMain: 1

3. Price comparison across fulfillment channels

asin: B0XXXXXXXX, domain: 1, days: 30, showPriceFba: 1, showPriceFbm: 1, showPrice: 1

4. Deal and coupon price tracking

asin: B0XXXXXXXX, domain: 1, days: 90, showPriceDeal: 1, showPriceCoupon: 1

5. Full product health check

asin: B0XXXXXXXX, domain: 1, days: 90, showPrice: 1, showPriceList: 1, showPriceDeal: 1, showPricePrime: 1, showPriceFba: 1, showPriceFbm: 1, showPriceCoupon: 1, showBsrMain: 1, showSellerCount: 1

Display Rules

  1. Present data clearly: Show time-series data in tables or describe trends; avoid subjective business advice unless the user explicitly asks for it.
  2. BSR clarification: When showing BSR data, remind users that lower values mean better (higher) sales ranks.
  3. Price formatting: Display prices with proper currency symbols matching the marketplace ($ for US, EUR for DE/FR/ES/IT, GBP for UK, JPY for JP, etc.).
  4. Time formatting: Present timestamps in a human-readable date format.
  5. Trend summarization: When data series are long, summarize the overall trend (e.g., "price decreased from $29.99 to $24.99 over 90 days") and highlight significant changes such as price drops, BSR spikes, or rating shifts.
  6. Error handling: When a query fails, explain the reason and suggest corrections (e.g., verify the ASIN is valid, check the marketplace domain ID).
  7. Single ASIN limitation: If the user asks about multiple ASINs, inform them that queries must be made one ASIN at a time, and run multiple sequential calls.

Important Limitations

  • Single ASIN per query: Only one ASIN can be queried at a time. For multi-ASIN comparisons, make separate requests.
  • Maximum 365 days: Historical data is limited to at most 365 days back.
  • Data granularity: Data points are at irregular intervals depending on when Keepa captured changes, not at fixed daily intervals.

User Expression & Scenario Quick Reference

Applicable -- Historical product-level data queries on Amazon:

User SaysScenario
"What's the price history for this ASIN"Price trend analysis
"Show me the BSR trend", "how is it ranking"BSR tracking
"Has the price dropped recently", "any deals"Price drop / deal detection
"How many sellers are on this listing"Seller count trend
"What's the rating trend", "review count over time"Rating / review tracking
"FBA vs FBM price", "who has the Buy Box"Fulfillment price comparison
"Monthly sales for this product"Sales volume trend
"Was there a price war on this ASIN"Competitive pricing analysis
"Show me the Keepa chart", "Keepa data"Explicit Keepa data requests

Not applicable -- Needs beyond product-level historical data:

  • Search term / keyword analysis (use ABA data instead)
  • Advertising / PPC campaign data
  • Listing copywriting or content optimization
  • Category-wide or market-level aggregate trends (this tool is per-ASIN only)
  • Real-time inventory or stock level checks
  • Product reviews text or sentiment analysis

Boundary judgment: When users say "product research" or "competitor analysis", if it boils down to examining a specific ASIN's historical price, BSR, or sales data, this skill applies. If they need keyword data, market-wide trends, or advertising metrics, it does not apply.

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.


For more high-quality, professional cross-border e-commerce skills, set LinkFox Skills.

Comments

Loading comments...