Growth metrics diagnosis
Skill duandigi/duandigi-growth-marketing-skill/skills/growth-metrics-diagnosis
Use this skill when investigating growth metric changes, anomalies, attribution conflicts, reporting discrepancies, or unclear performance across analytics, search, ads, CRM, product, or revenue systems.From its SKILL.md
npx -y skills add duandigi/duandigi-growth-marketing-skill --skill growth-metrics-diagnosisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.7 KB, 446 tokens by cl100k_base, as published. Nobody here has run it
Growth Metrics Diagnosis
Purpose
Diagnose what changed, why it may have changed, and what evidence is still missing.
Inputs
- Metric definition and data source
- Comparison windows
- Segments and related metrics
- Tracking, release, campaign, and operational changes
If critical input is unavailable, label it unknown and create a research or instrumentation task. Do not invent values.
Workflow
- Restate the exact metric formula, entity, timezone, attribution model, and reporting window.
- Validate data freshness, sampling, filters, consent changes, event definitions, and pipeline failures.
- Decompose the metric into volume, rate, mix, and value components.
- Compare leading, coincident, and lagging indicators.
- Build competing explanations and list evidence for and against each one.
- Separate confirmed causes, likely causes, and unknowns.
- Recommend the minimum next checks that would materially reduce uncertainty.
Required output
Return a concise, decision-oriented response containing:
- Metric definition
- Observed change
- Data-quality checks
- Driver decomposition
- Hypotheses
- Confidence
- Next checks
Label important statements as confirmed, inferred, assumed, or unknown when the distinction affects the decision.
Guardrails
Do not:
-
Attributing every change to marketing
-
Comparing partial current periods with complete prior periods
-
Confusing platform-reported conversions with incremental impact
-
Claim guaranteed growth or present an estimate as observed fact.
-
Recommend spam, fake reviews, impersonation, deceptive urgency, dark patterns, policy evasion, or unauthorized production changes.
-
Hide material uncertainty, tracking limitations, or possible harm.
When an action can spend money, publish content, contact people, change production systems, delete data, or alter access, produce a plan and request explicit authorization rather than executing automatically.
Completion check
Before finishing, verify that the output:
- answers a specific growth decision;
- uses the supplied business context;
- separates evidence from assumptions;
- defines a measurable next step;
- includes risks, constraints, and missing data;
- is no longer than necessary for the decision.
What ships with it: 1 file
1.3 KB alongside SKILL.md
evals/
- evals.json1.3 KB