Skip to content

florianbonnet14/ThePowerOfAnalytics_ClaudeSkills / north-star-metric-agent

north-star-metric-advisor

Verified

Strategic framing and KPI setting specialist that helps identify and validate the single most important metric capturing customer value delivery and predicting business success. Use when starting a new team or product, when existing product lacks clear success metric, when team seeks to define what success means, or when metrics don't align with customer value and/or business goals.

FileKindSize
North Star Metric Tutorial.mdmarkdown4.4 KB
README.mdmarkdown2.3 KB
SKILL.mdskill md3.6 KB
references/advanced-faq.mdmarkdown12.1 KB
references/evaluation-framework.mdmarkdown6.5 KB
references/examples.mdmarkdown3.8 KB
references/output-template.mdmarkdown4.5 KB

references/output-template.md

View on GitHub
# North Star Metric Output Template

Use this template to document the final North Star Metric after validation.

```markdown
# North Star Metric: [METRIC NAME]

## Definition

**Metric:** [Clear, one-sentence definition with measurement specifics]

**Example:** "Number of nights booked per month" or "Weekly active users who send at least 3 messages"

---

## Customer Journey

**Point A (Unsatisfied Need):**
[Description of the customer's initial state, problem, or goal]

**Point B (Satisfied Need):**
[Description of the customer's desired end state after using your product]

**How This Metric Captures Value Delivery:**
[Explanation of how the metric directly measures movement from A to B]

---

## Why This Metric?

### 1. Reflects Customer Value
**Score:** [X/5]

[Explain how this metric correlates with customer success. Include:
- What customer outcome this represents
- Why improvement in this metric means customers are better off
- How this aligns with your product's core value proposition]

**Example behaviors measured:**
- [Specific action 1]
- [Specific action 2]
- [Specific action 3]

---

### 2. Measurable
**Score:** [X/5]

**Current State:** [Choose one: Already tracking | Need to build | Timeline for implementation]

**How We Measure:**
[Technical details on data collection:
- Event tracking approach
- Data sources
- Tracking infrastructure
- Update frequency (real-time, daily, weekly)]

**Data Quality:**
[Any known limitations or considerations]

---

### 3. Actionable
**Score:** [X/5]

**Our Control:** [Percentage]% of drivers under team influence

**Key Drivers We Influence:**
1. [Driver 1 - how we control it]
2. [Driver 2 - how we control it]
3. [Driver 3 - how we control it]
4. [Driver 4 - how we control it]

**Feedback Loop:** [Leading indicator: see results in days/weeks | Lagging indicator: see results in months]

**Dependencies:**
[List any external dependencies or factors outside team control]

---

### 4. Tied to Revenue/Cost
**Score:** [X/5]

**Connection Path:**
[Metric] → [Intermediate step(s)] → [Revenue/Cost Impact]

**Example:**
"# Messages sent per day → Higher engagement → Better retention → Increased paid conversions"

**Supporting Data:**
[Include any correlation data, conversion rates, or historical evidence linking this metric to business outcomes]

---

## Total Score: [SUM/20]

✓ **Interpretation:** [Excellent (18-20) | Good (15-17) | Needs Refinement (12-14) | Poor (<12)]

---

## Target & Benchmarks

**Current Baseline:** [Current value of metric]

**3-Month Target:** [Specific target]

**6-Month Target:** [Specific target]

**12-Month Target:** [Specific target]

**Industry Benchmarks:** [If available, include comparison to industry standards]

---

## Supporting Metrics (Level 1 KPIs)

While the North Star is our primary focus, these supporting metrics help us understand the drivers:

1. **[Input Metric 1]:** [Why it matters]
2. **[Input Metric 2]:** [Why it matters]
3. **[Input Metric 3]:** [Why it matters]

---

## Known Limitations

[List any known limitations or edge cases:
- What this metric might miss
- Potential gaming concerns
- Segments where this metric may not apply
- Conditions under which we'd reconsider this metric]

---

## Next Steps

1. **Data Infrastructure:** [What needs to be built/verified]
2. **Dashboard Setup:** [Where and how we'll track this]
3. **Team Alignment:** [Communication and education plan]
4. **Experiment Framework:** [How we'll test impact on North Star]

---

## Document History

**Defined:** [Date]
**Defined By:** [Team/person]
**Last Reviewed:** [Date]
**Next Review:** [Date]
```

## Completion Checklist

Before finalizing the document, ensure:

- [ ] Metric name is clear and specific
- [ ] Definition includes measurement specifics (timeframe, user segment)
- [ ] Point A and Point B are clearly articulated
- [ ] All 4 properties have scores and explanations
- [ ] Total score is ≥15/20
- [ ] Connection to revenue is explicit
- [ ] Current baseline and targets are set
- [ ] Supporting metrics are identified
- [ ] Known limitations are documented
- [ ] Next steps are actionable

## Tips for Strong Documentation

**Be Specific:**
- ✓ "# of nights booked per month"
- ✗ "Booking activity"

**Include Context:**
- ✓ "Weekly active users who send ≥3 messages"
- ✗ "Active users"

**Show the Path:**
- ✓ "Messages sent → Engagement → Retention → Paid conversions"
- ✗ "This metric relates to revenue"

**Quantify Control:**
- ✓ "We control 75% via features X, Y, Z"
- ✗ "We have good control over this"
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall