# Metric Impact Analyzer

> Use when a change may affect metrics, semantic models, dashboards, reporting, or stakeholder-facing KPIs and you need to know whether business meaning or downstream BI assets change.

- **Type:** Skill
- **Install:** `agentstack add skill-yeaight7-agent-powerups-metric-impact-analyzer`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [yeaight7](https://agentstack.voostack.com/s/yeaight7)
- **Installs:** 0
- **Category:** [Data & Analytics](https://agentstack.voostack.com/c/data-and-analytics)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [yeaight7](https://github.com/yeaight7)
- **Source:** https://github.com/yeaight7/agent-powerups/tree/main/plugins/data-engineering/skills/metric-impact-analyzer

## Install

```sh
agentstack add skill-yeaight7-agent-powerups-metric-impact-analyzer
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Metric Impact Analyzer

Use this skill when a change may affect metrics, semantic models, dashboards, reporting, or stakeholder-facing KPIs.

## Goals
- Detect whether a technical change also changes business meaning.
- Identify likely downstream breakage in BI tooling and dashboards.
- Separate harmless refactors from definition-level changes.

## What to Inspect
- Metric definitions and calculation logic.
- Semantic model changes (dimensions, measures, relationships).
- Renamed or removed fields referenced by saved queries or dashboards.
- Changed filters, time windows, or default values.
- Changed joins, granularity, or fanout.
- Contract-breaking field type changes (e.g., INT → FLOAT, nullable → NOT NULL).

## Change Classification

| Change type | Risk level | Action required |
|---|---|---|
| Column rename with alias preserved | Low | Validate alias propagation |
| Description or label change | Low | Confirm no tooling parses descriptions |
| New optional field added | Low | No action unless it changes defaults |
| Filter condition tightened | Medium | Validate that the new filter matches intent |
| Metric formula changed | High | Stakeholder review required |
| Grain changed (e.g., day → week) | High | All downstream rollups must be revalidated |
| Dimension removed | Breaking | Cannot ship without migration plan |
| Join path changed | Breaking | All dependent metrics may be affected |

## Analysis Steps

1. Summarize what changed technically (field names, types, logic, joins).
2. Classify each change using the table above.
3. Infer what may have changed semantically — ask: "will this metric return a different number for the same time period?"
4. Identify who or what downstream may break: dashboards, saved queries, alerts, exports, downstream dbt models, BI tool semantic layers.
5. Flag whether stakeholder sign-off is required before the change is promoted.

## Output Format

1. **Technical change summary** — what exactly changed, at the field/model level.
2. **Business meaning impact** — does this change what the number means to a business user?
3. **Likely reporting or dashboard breakage** — specific assets at risk.
4. **Required validation** — what must be confirmed before shipping.
5. **Stakeholder confirmation needed?** yes / no / depends — with reason.

## Validation / Done Criteria
- Technical change summary covers all modified fields, models, and logic.
- Every change is classified by risk level using the table above.
- Downstream breakage is identified or explicitly noted as "unknown — downstream consumers not traced."
- Stakeholder confirmation requirement is stated as yes / no / depends, with a reason.

## Rules
- Be explicit about uncertainty when you cannot trace all downstream consumers.
- Use plain business language in the final summary — avoid dbt/SQL jargon in the stakeholder section.
- Do not edit code or models unless explicitly asked.

## Source & license

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

- **Author:** [yeaight7](https://github.com/yeaight7)
- **Source:** [yeaight7/agent-powerups](https://github.com/yeaight7/agent-powerups)
- **License:** Apache-2.0

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

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-yeaight7-agent-powerups-metric-impact-analyzer
- Seller: https://agentstack.voostack.com/s/yeaight7
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.