Skip to content
cccskills
FreePublished on GitHub

kpi-analysis-getting-started

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

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

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.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

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

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

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

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

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.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

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

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

See all skills by Significant-Gravitas

Report a problem with this skill