monte-carlo-asset-health

Aggregate freshness, alerts, monitors, and upstream lineage into a structured health report.

90|6|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/monte-carlo-data/mc-agent-toolkit --skill monte-carlo-asset-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monte-carlo-asset-health
Source: https://github.com/monte-carlo-data/mc-agent-toolkit/tree/main/skills/asset-health
Command: npx skills add https://github.com/monte-carlo-data/mc-agent-toolkit --skill monte-carlo-asset-health

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Check the health of a data asset by aggregating freshness, alerts, monitoring coverage, importance, and upstream dependency health into a single, structured report.

Core Features & Use Cases

  • Generates a comprehensive health report for a single asset, including last activity, active alerts, monitor status, and upstream health.
  • Highlights upstream issues and risk factors to support proactive triage and remediation planning.
  • Integrates with Monte Carlo MCP workflows to drive deterministic checks and consistent outputs.

Quick Start

Ask about a table's health to generate a structured health report.

Frequently Asked Questions about monte-carlo-asset-health

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the health of a data asset?

To check data asset health, resolve the specific asset and aggregate its freshness metrics, active alerts, and monitor status. This generates a structured health report highlighting last activity and upstream lineage dependencies for proactive triage.

What is included in a data asset health check?

A data asset health check includes last activity timestamps, active alerts, monitoring coverage, and upstream lineage health. By synthesizing these metrics, it provides a comprehensive risk assessment and identifies upstream issues affecting data warehouses and reports.

How do I assess upstream lineage issues for my data warehouse tables?

Assess upstream lineage issues by collecting dependency data via get_asset_lineage and aggregating it with freshness and alert metrics. This identifies risk factors in upstream dependencies, enabling proactive remediation planning for data warehouse assets.

Can I monitor data freshness and alerts for individual assets?

Yes, you can monitor data freshness and alerts for individual assets by collecting metrics through get_table and get_alerts. This resolves the specified asset and synthesizes the results into a structured health report for triage.

Does this data observability approach work for reports and upstream dependencies?

Yes, this data observability approach works for individual assets across data warehouses, reports, and upstream dependencies. It resolves the asset and collects metrics to generate deterministic health checks and consistent outputs.

Why monitor upstream dependency health during a data asset triage?

Monitoring upstream dependency health during triage highlights upstream issues and risk factors that impact the target asset. Aggregating lineage data with alerts and monitors supports proactive remediation planning and structured risk assessment.