---
name: operationalize-approved-metrics-dashboards-reports
description: 'Carry an owner-approved metric contract through an internal dashboard and disabled recurring report, then reconcile both outputs and prepare evidence for controlled release. Use when when approved metrics must be implemented in both an internal dashboard and a repeatable report; when existing reporting needs a governed implementation/reconciliation cycle; when release owners need observable evidence before enabling use.'
compatibility: 'Instruction-only Agent Skill. Requires an Agent Skills-compatible client and access to the tools or systems named in the instructions. No executable scripts are bundled.'
metadata:
  publisher: RichlyAI
  product: Amo.ng
  amo_id: AMO-S-000037
  canonical_url: 'https://amo.ng/skills/operationalize-approved-metrics-dashboards-reports'
  package_version: 1.0.0
  source_type: workflow
  source_amo_id: AMO-W-000032
  source_content_sha256: efb0ba2d9d15dd52485c94feb1965a7de0da835994918100bb7480fbebddf578
---

# Operationalize Approved Metrics Across Dashboards and Reports

## When to use this Skill

- When approved metrics must be implemented in both an internal dashboard and a repeatable report; when existing reporting needs a governed implementation/reconciliation cycle; when release owners need observable evidence before enabling use.

## When not to use this Skill

- To resolve disputed metric meaning; to obtain production credentials; to mutate source records; to activate schedules or delivery; or to make management decisions.

## Required inputs

- Owner-approved metric contracts with stable IDs, formulas, grain, dimensions, time rules, units, tolerances, and owners
- Approved dashboard requirements and disabled report/schedule contract
- Authorized repository, schemas or read-only interfaces, and synthetic or sanitized fixtures
- Roles, access boundaries, authoritative reconciliation totals, and data-freshness rules
- Allowed files and commands, performance expectations, release owners, and rollback constraints

Use [INPUT-TEMPLATE.md](assets/INPUT-TEMPLATE.md) to organize the supplied information.

## Required tools or access

Published source tool designations: Claude, ChatGPT, Codex. These are source designations, not portable-client compatibility claims. Use only authorized access described in the inputs and source instructions. Do not claim access or inspection without evidence.

## Procedure

Before starting, read [SOURCE.md](references/SOURCE.md), including the exact Prompt instructions and any ordered Workflow steps, review notes and carry-forward requirements.

Use W32 in order. Carry the owner-approved metric contract into the dashboard specification and implementations. Keep unresolved definitions blocked. Implement only within authorized repository/data boundaries. Reconcile representative dashboard and report values to authoritative supplied totals. Test access, dates/timezones, stale/partial/error states, reruns, idempotency, and recovery. Keep delivery disabled and route the evidence pack to metric, data, security, and release owners.

Published expected output:

A metric-to-dashboard-to-report traceability register, change manifests, access and state tests, reconciliation matrix, failure/rerun evidence, disabled schedule/delivery proof, recovery instructions, and release-owner handoff.

## Review gates

Read and apply the source review instructions in [SOURCE.md](references/SOURCE.md) before acting. Keep proposed, unrun and executed actions distinct; preserve missing evidence and obtain the human approvals required by the source.

- Step 1: Stop if an accountable metric owner will not resolve a material definition conflict, and do not continue until the applicable metric contracts are owner-approved.
- Step 2: Hold if decision use, source feasibility, access rules, or KPI intent remains contradictory.
- Step 3: Stop if data access is unauthorized, metrics conflict, confidential data is exposed, or publishing is requested.
- Step 4: Stop for unapproved data, disputed metrics, unavailable source contracts, or any request to enable delivery.
- Step 5: Hold decision use when material reconciliation, freshness, definition, or ownership evidence is missing.

## Completion criteria

Complete when every implemented output traces to an approved metric ID; dashboard and report calculations use the same governed contract; access, stale/error, date/timezone, and rerun paths have recorded results; authoritative totals reconcile within approved tolerances or differences remain explicitly blocked; delivery remains disabled; and accountable owners receive the release and recovery evidence.

Use the [completion checklist](references/COMPLETION-CHECKLIST.md) and record unresolved items.

## Limitations

Do not redefine metrics, infer missing owner decisions, request or expose credentials, use unapproved personal or confidential data, treat fixtures as production evidence, deploy or enable production refresh, scheduling, delivery, or external communication, or claim accuracy, readiness, or successful implementation without executed evidence and accountable approval.

This is an instruction-only package. Packaging does not execute work, grant access or independently verify the package. Existing public verification in amo.json describes only the identified published source resources.

## References

- [Published source instructions](references/SOURCE.md)
- [Completion checklist](references/COMPLETION-CHECKLIST.md)
- [Input template](assets/INPUT-TEMPLATE.md)
- [Rights](RIGHTS.md)
- [Canonical Amo.ng Skill](https://amo.ng/skills/operationalize-approved-metrics-dashboards-reports)