# Growth Measurement

> Use when work needs to design or audit growth metrics, tracking, data quality, attribution, forecasts, and causal experiments as one evidence-backed measurement system.

- **Type:** Skill
- **Install:** `agentstack add skill-krillinai-growee-skills-growth-measurement`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [krillinai](https://agentstack.voostack.com/s/krillinai)
- **Installs:** 0
- **Category:** [Data & Analytics](https://agentstack.voostack.com/c/data-and-analytics)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [krillinai](https://github.com/krillinai)
- **Source:** https://github.com/krillinai/growee-skills/tree/main/skills/growth-measurement
- **Website:** www.clawee.ai/

## Install

```sh
agentstack add skill-krillinai-growee-skills-growth-measurement
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Growth Measurement & Experimentation

## Reuse Growee Context

At the start, read `.agents/growee-context.md` when it exists. Reuse only product, customer, market, outcome, constraint, evidence, and routing fields whose scope, definition, source, and date remain compatible; state what is reused and surface conflicts or staleness before asking for decision-changing gaps. The file grants no system access or execution authority, and this Skill must not silently rewrite the primary diagnosis.

## Integrated Capabilities

This Skill consolidates adjacent workflows behind one trigger. Use the main workflow for core requests. When a request matches a module below, read that module before executing it:

- [Growth Target Setting](references/modules/growth-target-setting/SKILL.md)
- [Growth Benchmark Analysis](references/modules/growth-benchmark-analysis/SKILL.md)
- [Tracking Plan](references/modules/tracking-plan/SKILL.md)
- [Growth Data Quality Audit](references/modules/growth-data-quality-audit/SKILL.md)
- [Attribution Analysis](references/modules/attribution-analysis/SKILL.md)
- [Marketing Mix Modeling](references/modules/marketing-mix-modeling/SKILL.md)
- [Growth Forecasting](references/modules/growth-forecasting/SKILL.md)
- [Experiment Design](references/modules/experiment-design/SKILL.md)

Audit, design, or specify a growth metric system that connects delivered customer value to sustainable business outcomes. Keep activity, attribution, prediction, association, and causality distinct. Missing evidence produces a bounded specification, never invented values.

Read [metric-contract.md](references/metric-contract.md) before accepting, comparing, or calculating a metric. Read [metric-system-design.md](references/metric-system-design.md) before selecting roles, a North Star candidate, or tree relationships. Read [measurement-and-governance.md](references/measurement-and-governance.md) before proposing instrumentation, reconciliation, targets, or operating cadence. Read [core-read-only-tools.md](references/core-read-only-tools.md) before using GA4, PostHog, Search Console, HubSpot, Google Ads, or Meta Ads. Use [playbook-sources.md](references/playbook-sources.md) for the pinned Growth Playbook basis.

## Select One Mode

| Mode | Use |
| --- | --- |
| `audit` | Review existing KPIs, definitions, dashboards, targets, trees, and reporting practices |
| `design` | Define a bounded outcome, metric constellation, tree, guardrails, and decision rules |
| `measurement` | Freeze reproducible contracts, sources, identity, windows, lineage, quality, and governance |

Name one primary mode. Preserve useful secondary work without blending an audit finding, design hypothesis, measured result, and operating decision.

## Return One Verdict

| Verdict | Gate |
| --- | --- |
| `decision-ready` | Core contracts are compatible, evidence is attributable, limitations are visible, and the declared decision rule can be applied |
| `partially specified` | Useful definitions or evidence exist, but material contract, comparability, quality, or governance fields remain unresolved |
| `hypothesis` | Customer value, metric role, relationship, target, or operating mechanism is plausible but not supported for the declared scope |
| `not decision-useful` | The proposed measure cannot support the decision because it represents the wrong value, entity, population, denominator, horizon, or evidence type |

Choose exactly one verdict for the metric system in scope. A dashboard, familiar KPI, target, executive preference, or large sample does not make a system decision-ready.

## Freeze The Decision And Contracts

Record the decision, owner, decision date and window, product and business context, customer value, qualified customer outcome, durable business outcome, entity and level, population, events, formula, identity, windows, maturity, cohorts, segments, sources, lineage, quality, guardrails, target basis, limitations, and external-action boundary.

Use exactly `verified`, `reported signal`, `inferred`, `unavailable`, or `not applicable` for evidence-bearing fields. Do not calculate or compare incompatible definitions. When private data is unavailable, create a metric and instrumentation specification with unknowns made explicit.

## Build From Value, Not Availability

Assign each core metric one primary role for the declared objective:

- `outcome`
- `north-star-candidate`
- `input`
- `guardrail`
- `diagnostic`
- `business-health`

A North Star Metric is optional. Reject every candidate when none represents delivered customer value, connects credibly to sustainable business value, decomposes into controllable inputs, and resists low-quality optimization. Revenue, GMV, DAU, MAU, traffic, signups, messages, seats, prompts, tokens, generated outputs, and transactions are not automatically customer value.

Label every metric-tree edge as exactly one of:

- `arithmetic identity`
- `hypothesized driver`
- `observed association`
- `causal evidence`
- `tradeoff`

Arithmetic decomposition does not establish causality. Correlation does not become a driver because it is actionable. A target is a strategic choice, not evidence; an external benchmark is context, not an operating rule.

## Execute In Dependency Order

1. Freeze the decision, owner, customer value, business outcome, and measurement boundary.
2. Validate entities, eligibility, events, formulas, identity, sources, windows, maturity, cohorts, and versions.
3. Assign metric roles and reject vanity or role-confused metrics without discarding useful diagnostics.
4. Build the smallest decision-useful constellation and label every tree edge with its evidence relationship.
5. Separate observed outcomes, predictions, attribution credit, associations, causal effects, targets, and benchmarks.
6. Audit quality, reconciliation, lineage, segment behavior, guardrails, business health, and counterevidence.
7. Specify the next measurement, validation, governance, and specialist handoffs.

## Transfer Across Markets

Treat every market as a new metric evidence boundary. Revalidate customer and payer value, entities, eligibility, events, formulas, identity, windows, cohorts, maturity, segments, sources, lineage, quality, targets, benchmarks, guardrails, business health, owners, and decision rules. Translation, a copied dashboard, or a familiar metric name does not validate transfer.

For China, distinguish market, legal entity, language, locale, product, channel, platform, app distribution, identity, payment, invoice, data source, consent, storage and transfer, content, advertising, support, and locally accountable review. When Simplified Chinese is requested, respond in native Simplified Chinese. Use current direct sources and local expertise; do not infer provider availability or make legal, tax, regulatory, accounting, causal, or performance conclusions. Keep the system `partially specified` or `hypothesis` until compatible local contracts and evidence support another verdict.

## Route Specialist Work

This Skill owns metric roles, contracts, constellation and tree design, relationship labels, guardrails, and measurement governance. Route adjacent artifacts without recreating them:

| Need | Route |
| --- | --- |
| Primary-constraint selection | `growth-diagnosis` |
| Value-state transitions or equal-maturity comparisons | `growth-diagnosis`, `retention` |
| Identity, data quality, attribution, target, forecast, or causal experiment work | Use the matching `growth-measurement` module |
| Recurring review or cross-team experiment operations | `growth-operations` |
| First value, recurring value, monetization, or returned-input mechanisms | `activation`, `retention`, `monetization`, `growth-loop-design` |

## Deliver In Order

Return:

1. mode, decision, owner, context, and measurement boundary;
2. one metric-system verdict and its limiting gate;
3. customer value, qualified outcome, and North Star recommendation or rejection;
4. metric constellation with one primary role per core metric;
5. metric tree with labeled relationships and evidence states;
6. versioned Metric Contracts;
7. evidence, compatibility, quality, lineage, target, benchmark, and limitation ledger;
8. instrumentation, reconciliation, governance, and 30-day validation plan;
9. Playbook sources, capability handoffs, and external-action boundary.

## External-Action Boundary

This Skill produces local analysis and specifications by default. It may perform bounded aggregate reads from the core sources in [core-read-only-tools.md](references/core-read-only-tools.md) only when explicit task-level authorization and a capable minimum-permission path already exist. Otherwise do not access authenticated systems or query production data.

Never export unrestricted customer data; join identities across systems without separate privacy-reviewed authorization; or alter events, identity, records, definitions, targets, dashboards, alerts, reports, flags, experiments, campaigns, budgets, bids, audiences, sitemaps, permissions, or customer state. Do not publish results or claim an action occurred when the capable path did not return verifiable evidence.

## Keep One Output Language

Use the requested output language consistently across headings, prose, tables, labels, and actions. When no language is explicit, match the user's dominant language; market, locale, platform, and source language do not override it.

For Simplified Chinese, write natural Simplified Chinese and translate ordinary business or analytical jargon instead of embedding English words such as `owner`, `brief`, `listing`, `cohort`, `baseline`, `benchmark`, `guardrail`, `gate`, `finding`, `roadmap`, `workflow`, and `handoff`. In B2B contexts, translate `account` as `企业客户` by default, or `客户账户层级` when the data level must be explicit; reserve `用户账号` for a person's login identity, and avoid the ambiguous standalone term `账户`. Keep only proper names, standard acronyms after a Chinese first-use definition, machine tokens or IDs, code, formulas, filenames, URLs, and exact quotations where necessary.

For English, use idiomatic English and do not add Chinese glosses except for proper nouns or quoted source text. Use multiple languages only when explicitly requested, and keep each version in a separate labeled section rather than mixing languages within sentences or tables. Do not alternate languages for emphasis or perceived expertise.

## Completion Gate

Confirm that the decision and owner are explicit; every core metric has one role and a reproducible or visibly incomplete contract; entities, denominators, windows, maturity, cohorts, sources, and versions are compatible; North Star candidacy is tested rather than assumed; every tree edge names its relationship and evidence; quality, trust, risk, cost, and business guardrails remain visible; targets and benchmarks have attributable bases or stay unavailable; predictions, attribution, association, and causality remain separate; missing evidence yields useful next work; specialist handoffs do not duplicate adjacent Skills; sources are pinned; and no external action occurred.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [krillinai](https://github.com/krillinai)
- **Source:** [krillinai/growee-skills](https://github.com/krillinai/growee-skills)
- **License:** MIT
- **Homepage:** www.clawee.ai/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-krillinai-growee-skills-growth-measurement
- Seller: https://agentstack.voostack.com/s/krillinai
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.