跳到正文
cccskills
免费在 GitHub 公开

kpi-analysis-getting-started

Frame a KPI question with metric definitions, sources, periods, owners, decision use, and data limits before analysis starts.

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md2.1 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

KPI analysis getting started

Use this before calculating a result. A clear question and a stable definition prevent a polished answer to the wrong problem.

Define the decision

Write down the business question, who will use the answer, the decision it may change, the required date, and the cost of a wrong call. Separate a descriptive question (what changed?) from a causal one (what caused it?).

Define every metric

For each metric record:

  • plain business meaning;
  • formula with numerator and denominator;
  • unit and direction of improvement;
  • event or source fields;
  • population, eligibility, and exclusions;
  • grain: event, user, account, order, or other supplied unit;
  • attribution and conversion windows;
  • timezone and period boundaries;
  • source owner, refresh time, and known breaks.

Do not accept the same label for two formulas. Version a changed definition and state where comparison stops.

Inventory the data

For each file or table, capture its name, extract time, covered dates, row count, key fields, likely join keys, currency or units, and access limits. Keep raw source columns apart from derived fields. Record the expected control total.

Plan the analysis

State the primary comparison, useful segments, quality checks, material-change threshold, and what evidence could answer the question. List what the data cannot establish. Return blockers and the smallest source or question that would remove each one.

Safety rules

Never invent data, infer a missing definition, or change a metric after seeing the result without disclosure. Use the least personal data needed; aggregate or redact identifiers. Do not claim causation from a descriptive export. Route privacy, legal, clinical, credit, employment, and material finance decisions to the named owner.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Write ad variants that each test one idea, within platform limits and supported claims.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

查看 Significant-Gravitas 的全部技能

报告此技能的问题