# scheduled-report-refresh

Re-pulls the charts in a saved Amplitude dashboard for recurring reports and summarizes the changes since the last baseline.

Skill by Amplitude. Category: Knowledge.

## Install

Project (for this project only):

```sh
npx skills add amplitude/mcp-marketplace --skill scheduled-report-refresh
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

Global (for every project on this machine):

```sh
npx skills add amplitude/mcp-marketplace --skill scheduled-report-refresh -g
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

## Tags

- Runs on your computer: It runs as a program on your machine, with your access.

## Security audits

- Gen Agent Trust Hub: Pass
- Socket: Pass
- Snyk: Pass

Installs: 4. Installs counted by skills.sh. [Open on skills.sh](https://www.skills.sh/amplitude/mcp-marketplace/scheduled-report-refresh)

## Source

[Open the source](https://github.com/amplitude/mcp-marketplace/tree/HEAD/plugins/amplitude/skills/scheduled-report-refresh). Checked 2026-10-10. This summary may contain AI-generated text, so it can be wrong. Check the source before you rely on it.

## SKILL.md

````markdown
---
name: scheduled-report-refresh
description: Refreshes recurring reports (daily briefings, WBRs, experiment briefs) from saved Amplitude content — fetch the dashboard, re-pull its charts, fill gaps with ad hoc queries, summarize deltas. Use for "run the daily/weekly report", "refresh this dashboard's numbers", or scheduled custom-agent report runs.
---

# Scheduled Report Refresh

The dominant *automated* job on this MCP server: custom agents and
scheduled runs re-pulling a known set of charts and summarizing changes.

## The arc

1. **Anchor on saved content.** `use_amp_dashboards` `action: 'get'`
   (batch ≤3) for the report's chart list, or `get_from_url` if the run
   input is a link. Saved charts are the contract — do not rebuild
   definitions from scratch.
2. **Re-pull data.** `get_amplitude_charts` `include: 'data'`, ≤3 chart IDs
   per call, at the report's granularity (daily for daily/weekly briefs).
   For each chart compare the current period against the trailing baseline
   the report uses.
3. **Fill gaps ad hoc.** `query_amplitude_data` (typed `chart`) only for
   numbers no saved chart covers (a new funnel step, a one-off slice).
4. **Context for movement.** `use_amp_flags` `action: 'list_deployments'` once — recent deploys are
   the first hypothesis for any metric movement.
5. **Report.** Delta table first (metric, current, baseline, % change),
   then notable movers with hypotheses. State explicitly when the current
   period is partial ("today is tracking at X vs Y full-day yesterday").

## Expectations to set

- `get_amplitude_charts` `include: 'data'` on a saved chart returns exactly
  what the UI shows — trust it; don't re-validate every number with
  `query_amplitude_data`.
- Keep definition reads (`include: 'definition'` / `'typed'`) minimal on
  refresh runs — the dashboard chart list plus data is enough unless a chart
  looks misconfigured.
- If a chart errors or returns empty, report it as a broken report item
  rather than silently dropping it — a missing tile in a recurring report
  is itself a finding.
````

- Previous: [live-data-forensics](https://syn4pse.dev/terminal/amplitude-live-data-forensics.md)
- Next: [use-amp-guides-surveys](https://syn4pse.dev/terminal/amplitude-use-amp-guides-surveys.md)
- [Terminal](https://syn4pse.dev/terminal.md)
- [Suggest a change](mailto:terminal@syn4pse.dev?subject=Terminal%20suggestion)
