AgentStack
SKILL verified MIT Self-run

Analyze Account Health

skill-amplitude-mcp-marketplace-analyze-account-health · by amplitude

Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.

No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-amplitude-mcp-marketplace-analyze-account-health

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Analyze Account Health? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Analyze Account Health

Deep-dive into a B2B account's product usage to prepare for QBRs, assess renewal risk, identify expansion opportunities, or prioritize CS outreach.

Instructions

Step 0: Identify Account & Discover Context

Get the account identifier:

  • Company name, org ID, account ID, or group property value
  • Ask user if not provided

Search for existing work: Use Amplitude:search to find existing dashboards, charts, or notebooks for this account. If found, ask user if they want fresh analysis or to review existing.


Step 1: Quick Health Triage

Use Amplitude:query_dataset to run these queries in parallel:

Usage Trend:

  • Event: _active, Metric: uniques, Group by: account property
  • Time: Last 60 days, daily interval
  • Shows: Activity increasing or decreasing?

Engagement Quality:

  • Calculate DAU and MAU for account
  • Get DAU/MAU ratio (stickiness)
  • Shows: How engaged are active users?

User Momentum:

  • Active user count week-over-week
  • Shows: Team growing or shrinking?

Classify Health:

  • Healthy: Growing MAU, DAU/MAU >40%, positive WoW
  • At-Risk: Flat/declining MAU, DAU/MAU 20-40%, negative WoW
  • Critical: Steep decline, DAU/MAU 30 days)
  • [Count] users ([X]% of licenses)

💡 Top Pain Points & Requests

Pain Points

  1. [Theme] (X mentions)
  • [Concise description]
  • Evidence: [Behavioral data] + "[Quote]" - [Source, Date]
  • Action: [What to do]

Feature Requests

  1. [Theme] (X mentions)
  • [What they want]
  • Evidence: "[Quote]" - [Source, Date]
  • Roadmap status: [On roadmap/Not planned/Considering]

What They Love ❤️

  1. [Feature]: "[Quote]"

📊 Feature Adoption

High Usage: [Feature] - [X users] (↑Y%) Declining: [Feature] - [X users] (↓Y%) - Investigate Untapped (Upsell): [Premium feature] - Could solve [pain point]


🎯 Recommendations

🔥 This Week

  1. [Specific action with user/contact name]

📅 This Month

  1. [Strategic action with context]

💰 Expansion Opportunities

  1. [Upsell signal with evidence]

📎 Details

  • Analysis Date: [Date]
  • Timeframe: [Last X days]
  • Confidence: [High/Medium/Low based on data volume]

Best Practices

  • Always name users - CS needs who to contact, not aggregates
  • Connect feedback to behavior - Validate complaints with usage data
  • Be specific in recommendations - "Call Sarah about Feature X" not "improve engagement"
  • Show trends, not snapshots - Direction matters more than point-in-time
  • Flag data gaps - Note low volume, missing properties, or incomplete data
  • Prioritize by impact - Focus on issues affecting multiple users or champions

Common Patterns

Churn Risks:

  • Champion churned + declining overall usage
  • Multiple complaints about same issue + behavioral evidence of friction
  • License utilization declining + negative feedback

Expansion Signals:

  • Hitting plan limits (users, API, storage)
  • Requests for premium features + high engagement
  • New users being added + positive feedback

Source & license

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

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

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.