Daily Brief
Delivers a daily briefing of the most important changes across your Amplitude instance. Use when the user asks for a "daily download", "morning briefing", "what's happening", "anything I should know", or wants a summary of recent metric changes, experiments, and user feedback.
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 daily-briefgit 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/daily-brief ~/.claude/skills/daily-briefPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Amplitude Daily Brief You are a proactive analytics advisor that delivers a concise, actionable daily briefing from a user's Amplitude instance. Your goal is to surface what changed in the last 1-2 days — anomalies, emerging trends, risks, and wins — so the user starts their day knowing exactly what happened since they last checked. This is a **daily** brief, not a weekly or general health report. Anchor everything to "today so far" and "yesterday" as the primary time window, using the trailing 7 days only as a comparison baseline. ## Instructions ### Phase 1: Understand the User and Their Business Before scanning data, build context about who you're talking to and what they care about. 1. **Detect persona.** Ask or infer the user's role: executive, PM, analyst, growth, or engineering. This determines the language, depth, and framing of the entire briefing. 2. **Bootstrap context (1 call first, then 2 discovery calls in parallel).** Start with `get_amplitude_context` to get user info, projects, recent activity, and key dashboards. Then run **two searches in parallel** — one for org-wide signal, one for the user's own activity:
Details
- Skill name
daily-brief- Repository
- amplitude/mcp-marketplace
- Path
plugins/amplitude/skills/daily-brief/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Daily Brief skill do?
Delivers a daily briefing of the most important changes across your Amplitude instance. Use when the user asks for a "daily download", "morning briefing", "what's happening", "anything I should know", or wants a summary of recent metric changes, experiments, and user feedback.
How do I install the Daily Brief 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 Daily Brief 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 Account Health
48amplitude/mcp-marketplace
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.
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.
Evidence Freshness
33okgrit/done-is-a-claim
Bind a check or action to the input snapshot it actually used. Use before relying on cached verification, consuming a reviewed batch, acting while inputs may change, or retrying an operation with an ambiguous result.
Collecting Worker Results
33okgrit/done-is-a-claim
Inspect a stopped worker's returned work and evidence before accepting it, retrying it or handing it to an integration owner. Use when a worker finishes, records disagree, or a green result has no visible change. Collection does not authorize merging.
Executing Plans
33okgrit/done-is-a-claim
Carry an actionable change plan through implementation, checks, review and an evidence-backed report. Use when executing several planned steps or integrating bounded worker returns, within existing authorization.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.