Token导航 LogoToken导航

Agent Skill · 研究检索

product-analytics(产品分析)

用于辅助数据整理、表格处理、CSV/Excel 分析、指标计算和图表准备。它适合让 Agent 清洗字段、汇总数据、发现异常、生成统计口径或把分析结果转成可读说明。使用时需要确认数据来源、字段含义和时间范围,避免把样本数据当全量事实;涉及敏感数据、导出文件或批量写回时,应先确认权限和脱敏边界。

product-analytics 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 51,212。

总安装 588周安装 25GitHub Stars 19下载 206核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:product-analytics(产品分析)
来源仓库:https://github.com/finsilabs/awesome-ecommerce-skills
仓库路径:skills/product-analytics
安装命令:
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill product-analytics
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill product-analytics

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

product-analytics 用于辅助数据整理、表格处理、CSV/Excel 分析、指标计算和图表准备。适合清洗字段、汇总数据、发现异常、生成统计口径或把分析结果转成可读说明。使用时需要确认数据来源、字段含义和时间范围,避免把样本数据当全量事实。涉及敏感数据、导出文件或批量写回时,应先确认权限和脱敏边界。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/product-analytics

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill pro…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

product-analytics 怎么安装?

在终端执行 npx skills add https://github.com/finsilabs/awesome-ecommerce-skills --skill product-analy…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

product-analytics 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

product-analytics 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

product-analytics 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

product-analytics 用的人多吗?

公开数据是累计安装 588 次,近一周安装 25 次,下载 206 次,GitHub 19 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

product-analytics 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
product-analytics

产品分析 · 本页

58819需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Product Analytics

Overview

Product analytics reveals which products drive revenue, which are overstocked, and which product pages are losing shoppers before they add to cart. The core analyses — sell-through rate, dead stock identification, PDP conversion funnel, and category performance — give your buying and merchandising team the data they need to make confident reorder, markdown, and catalog decisions.

This skill guides you through running these analyses using your platform's built-in tools and dedicated apps, without building custom data pipelines.

When to Use This Skill

  • When the buying team needs a weekly sell-through report to decide on reorders and markdowns
  • When building a product performance dashboard for merchandisers
  • When identifying dead stock that ties up capital
  • When measuring which products have high views but low add-to-cart rates
  • When ranking products for collection page sorting based on performance data
  • When generating a catalog health report before a seasonal reset

Core Instructions

Step 1: Choose your product analytics tool by platform

PlatformToolWhat It Provides
ShopifyShopify Analytics (built-in)Product-level revenue, units sold, sell-through (if cost entered); free
ShopifyInventory Planner (App Store)Sell-through rates, days of supply, reorder recommendations, dead stock alerts
ShopifyGoogle Analytics 4 (via Shopify's GA4 integration)PDP views, add-to-cart rate, checkout funnel by product
WooCommerceWooCommerce Analytics (built-in)Product revenue, units sold, orders by product; free
WooCommerceMetorikAdvanced product analytics including sell-through, cohort analysis by product, and dead stock reports
BigCommerceBigCommerce Analytics → Merchandising (built-in)Product revenue, units sold, and conversion rate by product
BigCommerceGlew.io (App Marketplace)Advanced sell-through, dead stock, and product lifecycle analytics
All platformsGoogle Analytics 4 + enhanced ecommerceViews-to-cart-to-purchase funnel by product; requires GA4 setup with ecommerce tracking

Step 2: Analyze sell-through rate

Sell-through rate measures how much of received inventory has been sold:

Sell-through % = Units Sold / (Units Sold + Units On Hand) × 100

A product at 80%+ sell-through is performing well. Below 30% after 60+ days suggests slow movement.


Shopify

Using Shopify Analytics:

  1. Go to Analytics → Reports → Inventory sold and remaining (this is the sell-through report)
  2. Set the date range to the product's launch date or the beginning of the season
  3. The report shows: Units received, Units sold, Units remaining, and % sold for each variant
  4. Export to CSV for detailed analysis

Using Inventory Planner:

  1. Install Inventory Planner from the Shopify App Store
  2. Go to Inventory Planner → Reports → Sell-Through — shows sell-through rate by product and variant
  3. Go to Inventory Planner → Reports → Days of Supply — shows how many days of stock remain at current sales velocity
  4. Go to Inventory Planner → Replenishment — automatically recommends reorder quantities and timing

Key sell-through benchmarks by category:

  • Fashion/seasonal items: Target 70%+ sell-through by end of season; anything below 40% at season end needs markdown
  • Evergreen/perennial basics: 50–70% sell-through is normal (higher in-stock availability is intentional)
  • Perishables/consumables: 85%+ (low days of supply is the goal)

WooCommerce

Using WooCommerce Analytics:

  1. Go to WooCommerce → Analytics → Products
  2. Set date range to the period you want to analyze
  3. View: Revenue, Quantity, Average price, Orders by product
  4. Export to CSV; calculate sell-through manually by dividing quantity sold by (quantity sold + current stock)

Using Metorik:

  1. Go to Metorik → Products — view all products with revenue, units sold, and refund data
  2. Apply the Slow Moving filter to identify products with low recent sales relative to their stock levels
  3. Create a Segment in Metorik for "products with 0 sales in the last 60 days" and monitor regularly

BigCommerce
  1. Go to Analytics → Merchandising → Products — shows revenue, units sold, and conversion rate per product
  2. Go to Analytics → Merchandising → Inventory — shows current stock levels alongside recent sales velocity
  3. Install Glew.io for sell-through rate calculations and dead stock alerts with automated weekly digest emails

Step 3: Identify dead stock

Dead stock is inventory that has been on hand for a long time with minimal or no sales. It ties up working capital, occupies warehouse space, and often requires markdowns to liquidate.

Dead stock criteria (adjust by category):

  • Fashion/seasonal: On hand 60+ days + sell-through < 20%
  • Evergreen basics: On hand 120+ days + sell-through < 15%
  • High-value items: On hand 90+ days + inventory value > $500

Finding dead stock by platform:

Shopify:

  1. Go to Analytics → Reports → Inventory sold and remaining — filter for products with > 90 days since first available AND sell-through < 20%
  2. Alternatively, install Inventory Planner → go to Reports → Excess Inventory for automated dead stock identification with capital-at-risk calculation

WooCommerce:

  1. Go to WooCommerce → Analytics → Products — sort by "units sold ascending" to find products with minimal recent sales
  2. Cross-reference with WooCommerce → Products → Inventory for current stock levels
  3. Metorik makes this easier: go to Metorik → Products → Filter by: 0 sales in last 90 days AND stock > 0

Dead stock action guide:

Days on HandSell-ThroughRecommended Action
60–90 days< 20%10–15% markdown; add to promotional emails
91–120 days< 15%20–25% markdown; feature in collections and homepage
120–180 days< 10%30–40% markdown; run dedicated clearance campaign
180+ days< 5%40–50% markdown or bundle with fast-movers; consider liquidation if markup still negative

Step 4: Measure product page conversion (Views → ATC → Purchase)

A product with high traffic but low add-to-cart rate signals a page problem: pricing, description, images, or reviews.

Setting up product-level funnel tracking:

All platforms require Google Analytics 4 with Enhanced Ecommerce for PDP conversion tracking.

Shopify:

  1. Go to Shopify → Online Store → Preferences → Google Analytics and add your GA4 Measurement ID
  2. Or install Google & YouTube from the Shopify App Store (recommended — includes server-side events)
  3. In GA4, go to Reports → Monetization → Ecommerce purchases → filter by item to see views, add-to-carts, and purchases per product
  4. For a funnel view: go to GA4 → Explore → Funnel exploration and build a funnel: view_item → add_to_cart → begin_checkout → purchase; dimension by item_name

WooCommerce:

  1. Install Google Analytics for WooCommerce by MonsterInsights or Site Kit by Google — both send WooCommerce product events to GA4 automatically
  2. View product funnel the same way as Shopify in GA4

BigCommerce:

  1. Go to BigCommerce → Analytics → Marketing → Connected Channels → Google Analytics and enable Enhanced Ecommerce
  2. View product funnel in GA4

Key PDP conversion benchmarks:

  • PDP view → Add to cart: 5–15% is typical; below 3% warrants investigation
  • Add to cart → Purchase: 40–60% is typical

What low add-to-cart rate usually means:

  • Price is too high relative to perceived value → A/B test price or add value (bundle, guarantee)
  • Product images are poor quality or show the product unclearly → Improve photography
  • Description does not address customer objections → Add FAQ section, size guide, or material details
  • Reviews are low or absent → Activate review request automation

Step 5: Build a weekly catalog health report

Combine sell-through, dead stock, and conversion data into a weekly report for the buying team.

Report structure (can be a recurring Metorik digest, Inventory Planner export, or manual Shopify CSV export):

WEEKLY CATALOG HEALTH REPORT — Week of [Date]

HEADLINE METRICS
  Active SKUs: 284
  Dead stock count (>90 days, <15% ST): 23 SKUs ($41,200 at cost)
  Low stock / reorder needed (<14 days supply): 12 SKUs
  New arrivals launched this week: 8 SKUs

TOP PERFORMERS (Revenue, last 7 days)
  [Product A] — $12,400 — 78% sell-through — 14 days supply remaining
  [Product B] — $9,800 — 65% sell-through — 32 days supply remaining

PRODUCTS NEEDING ATTENTION
  Slow movers (on hand >90 days, <20% ST):
    [SKU X] — 180 days on hand — 8% ST — $4,200 inventory value — ACTION: 30% markdown
    [SKU Y] — 120 days on hand — 12% ST — $2,800 inventory value — ACTION: 20% markdown

  High views, low ATC (>200 views last 7 days, <3% ATC):
    [Product Z] — 340 views — 1.8% ATC — Review product description and pricing

Best Practices

  • Report sell-through weekly, not monthly — a weekly cadence lets buyers intervene before products age into dead stock
  • Always include inventory value (units × cost) in dead stock reports — a merchant cares more about $5,000 tied up in slow movers than 100 units of a $3 product
  • Set different dead-stock thresholds by category — fashion items become dead stock faster (60 days) than perennial basics (180 days); configure category-specific thresholds in Inventory Planner or your reporting tool
  • Use days of supply, not just inventory count — 500 units of a product selling 5/day (100 days of supply) is very different from 500 units selling 1/day (500 days); days of supply is the actionable metric
  • Pair low-ATC-rate alerts with session recording — tools like Hotjar or Lucky Orange (Shopify App Store) let you watch real visitor sessions on high-traffic/low-converting product pages; often reveals issues invisible in metrics alone
  • Include return rate in product health scoring — high-return products look good on revenue but erode margin; investigate and possibly discontinue before reordering

Common Pitfalls

ProblemSolution
Dead stock report includes recently launched productsExclude products launched in the last 30 days from dead stock analysis; they need time to ramp up before being flagged
Sell-through over 100%Inventory received was understated — check if inventory received captures all purchase orders including transfers and returns
Days of supply calculation shows zero for products that are not sellingHandle zero-sales denominator as "effectively infinite stock" rather than division by zero; display as "No recent sales" in reports
PDP conversion data does not match expectationsVerify GA4 Enhanced Ecommerce events are firing correctly on product pages; use GA4's DebugView to confirm view_item and add_to_cart events
Product analytics slow on large catalogsMaterialize a weekly product performance summary table in your data warehouse or use Inventory Planner's pre-computed metrics instead of querying raw order data

Related Skills

  • @sales-reporting-dashboard
  • @customer-analytics
  • @ab-testing-ecommerce
  • @profit-margin-analysis

平台分布

Codex

33.6%
按下载量换算69

Claude

33.68%
按下载量换算69

Cursor

17.98%
按下载量换算37

Gemini CLI

8.87%
按下载量换算18

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills