Analyze Account Health
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.
Install
/plugin marketplace add amplitude/mcp-marketplaceThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add amplitude/mcp-marketplace --skill analyze-account-healthgit clone --depth 1 https://github.com/amplitude/mcp-marketplace.git /tmp/mcp-marketplace
mkdir -p ~/.claude/skills
cp -r /tmp/mcp-marketplace/plugins/amplitude/skills/analyze-account-health ~/.claude/skills/analyze-account-healthPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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_amp_entities` to find existing dashboards, charts, or notebooks for this account. If found, ask user if they want fresh analysis or to review existing. **Resolve how accounts are modelled — do this before any query.** Every step below breaks down "by account", and there are three different ways a project represents one. Check in this order and reuse the answer throughout: 1. Use the connected catalog's group-type discovery capability. If the project has a group type (commonly `org id` or `company`), that is the account. Read its attributes from the active taxonomy reader's group-property surface, then reference them with `scope: 'group'` plus `group_type`. To count accounts rather than users, set `count_unique_by` to the group type. 2. If there is no group type, the account is usually a **user property** (`company`, `org_name`) — `scope: 'user'`. 3. Failing both, an **event property** carrying the org (`org id`, `org url`). If a group property comes back as `Invalid group property … for group type …`,
Details
- Skill name
analyze-account-health- Repository
- amplitude/mcp-marketplace
- Path
plugins/amplitude/skills/analyze-account-health/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Analyze Account Health skill do?
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.
How do I install the Analyze Account Health skill?
Claude Code plugin: /plugin marketplace add amplitude/mcp-marketplace. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Analyze Account Health popular?
It lives in amplitude/mcp-marketplace, which has 48 GitHub stars and 12 forks.
Related skills
Add Analytics Instrumentation
48amplitude/mcp-marketplace
End-to-end analytics instrumentation workflow for a PR, branch, file, directory, or feature. Reads the code, discovers what events should be tracked, and produces a concrete instrumentation plan — all in one shot. Use this skill whenever a user wants to add analytics to a PR, asks "instrument this PR", "add tracking to this branch", "what analytics does this file need", "instrument the checkout flow", "run the full instrumentation workflow", or any request that implies going from code changes to a tracking plan. Also trigger when the user gives you a PR link, branch name, file path, or feature
Analyze AI Topics
48amplitude/mcp-marketplace
Analyzes what users ask AI agents about and how well each topic is served. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when the user asks "what are people asking the AI", "top AI topics", "where is the AI struggling", "AI coverage gaps", "what should we improve in our AI", or wants product insights from AI conversation patterns.
Analyze Chart
48amplitude/mcp-marketplace
Performs deep analysis of a specific Amplitude chart to explain trends, anomalies, and likely drivers. Use when a metric looks unusual, investigating a spike or drop, or understanding the "why" behind numbers.
Analyze Feedback
48amplitude/mcp-marketplace
Synthesizes customer feedback into actionable themes including feature requests, bugs, pain points, and praise. Use when planning product roadmap, understanding user sentiment, investigating specific issues, or preparing voice-of-customer reports.
Sanity Check
62ElliotJLT/Claude-Skill-Potions
Before building on assumptions, validates them first. Activates when making claims about how code works, what exists, or why something happens. Prevents assumption cascades where one wrong guess leads to a completely wrong solution.
Compare User Journeys
48amplitude/mcp-marketplace
Compares how two user groups behave differently by analyzing Amplitude Session Replays and metrics side by side. Produces a behavioral diff showing what one group does that the other doesn't. Use when a PM or growth lead asks "what do converters do differently", "how do power users behave", "why do churned users leave", "compare these cohorts", "what separates segment A from B", or wants to understand the qualitative behavioral gap between two user populations.
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.