Token导航 LogoToken导航

Agent Skill · 研究检索

analytics-metrics-kpi(分析指标 kpi)

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

analytics-metrics-kpi 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为权限未标注;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 49,058。

总安装 665周安装 28GitHub Stars 175下载 233核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/nicepkg/ai-workflow --skill analytics-metrics-kpi

这个 Skill 是做什么的

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

analytics-metrics-kpi 辅助数据整理、表格处理和指标计算,适合清洗字段、汇总数据和生成统计说明。适用于 CSV/Excel 分析、异常发现、图表准备等数据分析场景。使用时需确认数据来源、字段含义和时间范围,避免将样本误作全量事实。涉及敏感数据或导出文件时,应先确认权限和脱敏边界。

建议结合具体项目需求验证分析结果的准确性和适用性。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

analytics-metrics-kpi 怎么安装?

在终端执行 npx skills add https://github.com/nicepkg/ai-workflow --skill analytics-metrics-kpi。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

analytics-metrics-kpi 支持哪些 AI 工具?

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

analytics-metrics-kpi 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

analytics-metrics-kpi 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

analytics-metrics-kpi 用的人多吗?

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

analytics-metrics-kpi 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 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调用外部服务未明确有提醒
analytics-metrics-kpi

分析指标 kpi · 本页

665175权限未标注MIT通过

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

SKILL.md 原文

Analytics & Metrics Skill

Become data-driven. Define meaningful metrics, build dashboards, run experiments, and make decisions based on data, not intuition.

Metrics Framework (Acquisition → Revenue)

North Star Metric

Definition: One metric that best captures the value your product delivers.

Characteristics:

  • Directly tied to business success
  • Driven by product improvements
  • Leading indicator of revenue
  • Understandable to whole company

Examples:

  • Slack: Daily Active Users (DAU)
  • Airbnb: Booked Nights
  • YouTube: Watch Time
  • Uber: Rides Completed
  • Stripe: Payment Volume Processed

Funnel Metrics (Acquisition)

Total Visitors: 100,000/month
↓ 20% conversion
Free Signups: 20,000
↓ 10% free-to-paid
Paid Customers: 2,000

CAC: $50 (marketing + sales spend / customers acquired)
LTCAC: $100 (all customer acquisition costs)

Metrics to Track:

  • Traffic - Total visitors to website/app
  • Signup Rate - % who sign up (target: 10-15%)
  • Free-to-Paid Conversion - % free users who pay (target: 2-5%)
  • CAC - Cost per acquired customer
  • CAC Payback - Months to recover CAC from revenue (target: < 12 months)

Activation Metrics

Goal: New users become active users

Free Signups: 2,000
↓ 30% onboard successfully
Activated: 600
↓ 60% remain active Day 7
Day 7 Active: 360

Metrics to Track:

  • Onboarding Completion Rate - % who complete setup (target: 50-80%)
  • Time to First Value - Hours to first successful use
  • Feature Adoption - % who try key features
  • Day 1/7/30 Retention - % active those days (target: 40/25/15)

Engagement Metrics

Goal: Users regularly use product

Daily/Monthly Metrics:

  • DAU/MAU - Daily/Monthly Active Users
  • DAU/MAU Ratio - Stickiness (target: 20-30%)
  • Feature Usage - % using key features
  • Session Length - Minutes per session
  • Session Frequency - Times per week

Cohort Analysis Example:

Jan Cohort (1,000 signups):
- Day 1: 600 active (60%)
- Day 7: 360 active (36%)
- Day 30: 180 active (18%)
- Month 3: 90 active (9%)

Feb Cohort (1,500 signups):
- Day 1: 1050 active (70%) ← Improving!
- Day 7: 630 active (42%)
- Day 30: 300 active (20%)

Retention Metrics

Goal: Users stay and continue paying

Month 1: 1,000 customers
Month 2: 900 active (90% retained)
Month 3: 810 active (90% of month 2)
Month 12: 314 active (31% annual retention)

Churn Rate: % lost each period

  • Monthly churn: (Customers Lost / Month Start) × 100
  • Annual churn: 1 - (Ending / Starting)
  • Target for SaaS: < 5% monthly churn

NPS (Net Promoter Score)

  • Question: "How likely to recommend (0-10)?"
  • Score = % Promoters (9-10) - % Detractors (0-6)
  • Range: -100 to +100
  • Target: 50+ (world-class)

Revenue Metrics

Monthly Recurring Revenue (MRR)

MRR = (Total paid customers) × (average subscription price)
Growth MRR = New MRR + Expansion MRR - Churn MRR

Annual Run Rate (ARR)

ARR = MRR × 12

Average Revenue Per User (ARPU)

ARPU = MRR / Total Users

Customer Lifetime Value (LTV)

LTV = (ARPU × Gross Margin %) / Monthly Churn %

Example:
ARPU: $100
Gross Margin: 80%
Monthly Churn: 5%
LTV = ($100 × 80%) / 5% = $1,600

If CAC = $400: LTV/CAC = 4x ✓ (target: 3x+)

Dashboard Architecture

Executive Dashboard (C-Level)

Weekly Updates:

  • MRR / ARR (vs target, vs month ago)
  • New customers (weekly, monthly)
  • Churn rate (%)
  • NPS score
  • Engagement (DAU, MAU)
  • Key initiatives status

Frequency: Weekly

Product Dashboard (Product Team)

Daily/Weekly:

  • Funnel metrics (signup → paid)
  • Feature adoption
  • Engagement metrics
  • User feedback score
  • A/B test results
  • Support ticket volume

Frequency: Daily updates

Financial Dashboard (Finance/Operations)

Monthly:

  • MRR / ARR
  • Customer acquisition cost
  • Customer lifetime value
  • Gross margin
  • CAC payback period
  • Revenue by segment
  • Churn by cohort

Frequency: Monthly

Health Dashboard (Operations)

Realtime:

  • System uptime (%)
  • Error rate (%)
  • Response time (p95)
  • Database performance
  • Support ticket response time
  • Support backlog

Frequency: Realtime/hourly

A/B Testing (Experimentation)

Test Planning

Hypothesis: "If we change X, then Y will improve, because Z"

Example: "If we move signup button above the fold, then conversion will improve 15%, because users won't scroll."

Test Structure

Experiment Design:

  • Control: Keep current version
  • Treatment: New version
  • Sample size: Enough users to be statistical
  • Duration: 2-4 weeks minimum
  • Metric: Clear success metric

Statistical Significance

Confidence Level: 95% (industry standard)

  • Means 5% chance of false positive
  • Need enough samples (typically 1000-10K per variant)
  • Use calculator for exact sample size

P-Value: Probability result is random chance

  • P < 0.05: Statistically significant
  • P > 0.05: Not significant, inconclusive

Example A/B Test

Hypothesis: Moving signup button above fold increases conversion 15%

Setup:

  • Control: Current design
  • Treatment: Button moved above fold
  • Success metric: Conversion rate (signup / visit)
  • Sample size: 10,000 users per variant
  • Duration: 2 weeks
  • Confidence: 95%

Results:

  • Control: 2.0% conversion (200 signups from 10K visitors)
  • Treatment: 2.8% conversion (280 signups from 10K visitors)
  • Improvement: 40% increase (0.8% / 2% = 40%)
  • P-value: 0.02 (statistically significant!)
  • Decision: SHIP IT - Roll out to 100%

Test Ideas by Priority

High Priority (Start Here):

  • Signup flow optimization (biggest funnel)
  • Onboarding experience
  • Pricing page clarity
  • Feature discoverability

Medium Priority:

  • UI copy optimization
  • CTA button colors
  • Email subject lines
  • Notification triggers

Low Priority:

  • Micro-copy tweaks
  • Animation effects
  • Color scheme changes

Metric Pitfalls to Avoid

Vanity Metrics

❌ "We have 1M page views!" ✓ "We have 50K daily active users, growing 10% monthly"

Actionable vs Non-Actionable

❌ "User satisfaction increased" (what changed?) ✓ "Onboarding completion rate 65% → 78% (↑20%)" (clear action)

Correlation vs Causation

❌ "Ice cream sales correlate with drownings" ✓ Understand actual causation, not just correlation

Look-Alike Metrics

❌ Track MRR but not Customer LTV (can grow MRR by spending more on acquisition) ✓ Track both acquisition efficiency AND retention

Metrics Review Cadence

Daily:

  • System uptime
  • Error rates
  • Support response time

Weekly:

  • Funnel metrics
  • Feature adoption
  • Key engagement metrics
  • Test results

Monthly:

  • Revenue metrics
  • Cohort analysis
  • Churn breakdown
  • LTV/CAC trends

Quarterly:

  • Strategic metric review
  • Long-term trend analysis
  • Metric changes needed

Troubleshooting

Yaygın Hatalar & Çözümler

HataOlası SebepÇözüm
Vanity metrics focusWrong KPI selectionNorth Star alignment
Inconclusive A/B testLow sample sizeExtend duration
Data inconsistencyMultiple sourcesSingle source of truth
Dashboard unusedToo complexSimplify to 5-7 KPIs

Debug Checklist

[ ] North Star metric defined mi?
[ ] Metrics business goals'a aligned mi?
[ ] Data collection accurate mi?
[ ] Dashboard refreshed mi?
[ ] A/B test sample sufficient mi?
[ ] Statistical significance achieved mi?

Recovery Procedures

  1. Data Quality Issues → Flag affected metrics, exclude
  2. Inconclusive A/B → Extend test duration
  3. Misleading Metrics → Add context/segmentation

Master data-driven decision making and grow faster!

平台分布

OpenCode

26.95%
按下载量换算63

Cursor

23.39%
按下载量换算54

Claude Code

17.17%
按下载量换算40

github-copilot

13.02%
按下载量换算30

Gemini CLI

7.98%
按下载量换算19

cline

3.74%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限未标注

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills