Agent skill · data analytics · adobe
aa-kpi-pulse
Produces a compact KPI digest showing how key metrics changed over a period and what's driving the movement. Use this skill when someone asks for a performance summary, a weekly recap, a morning briefing, a KPI update, or any variation of "how did we do this week/month." Also trigger for "give me a performance overview," "what moved in the last 7 days," "pull our AA KPI report," or "summarize our metrics.
Why this skill is useful
Adds specific commands and workflows for generating KPI reports from Adobe Analytics that the AI wouldn't reliably generate on its own.
What it needs
Requires adobe account access. About 7k tokens when loaded. Last updated 2026-08-06. 160 stars on the source repository.
What this skill does
KPI Pulse (Adobe Analytics) Produce a compact, digestible KPI digest showing how key metrics changed over a chosen period, which items drove the change, and what stood out. Batches all KPIs into two runReport calls (current period + comparison period) and assembles results into an HTML performance card deck. --- AA MCP Tools Used findReportSuites — select working report suite setSessionDefaults — set session context (reportSuiteId + globalCompanyId) describeAa(REPORTSUITECONTEXTGUIDE) — load org context, top metrics, calendar config, and timezone findMetrics — discover and validate metric IDs listComponentUsage — identify top-used metrics if user hasn't specified runReport — all KPIs batched in one call per period (current + comparison) searchDimensionItems — find top contributors for top-mover callouts --- Phase 0 — Setup 1. Confirm report suite with findReportSuites / setSessionDefaults. 2. Call describeAa(REPORTSUITECONTEXTGUIDE) to load organizational context: top metrics, calendar configuration, and timezone. Record the report suite's first-day-of-week as WEEKSTARTDOW and the report suite timezone as TIMEZONE — you will use both when computing reporting periods in Phase 2. If the context guide returns no WEEKSTARTDOW, default to Monday (ISO 8601). --- Phase 1 — Select KPIs 1.1 If the user specified metrics Resolve each to an AA metric ID: Cap at 8 metrics for a focused pulse. If more are requested, ask the user to prioritize or offer to split into multiple reports. 1.2 If the user has not specified metrics Use listComponentUsage to find the most-used metrics in the report suite: Select the top 5–7 by usage count. Confirm with the user: "Based on usage, I'll track: Visits, Page Views, Revenue, Orders, Conversion Rate, Bounce Rate. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills adobe/aa-kpi-pulse