Skip to content

monte-carlo-data/mc-agent-toolkit / skills/asset-health

monte-carlo-asset-health

Verified

Check the health of a data table/asset using Monte Carlo. Activates on "how is table X", "check health of X", "is X healthy", "status of X", "check on X table", or any health/status question about a data asset.

FileKindSize
README.mdmarkdown1.5 KB
SKILL.mdskill md9.5 KB
references/parameters.mdmarkdown4.3 KB
references/workflows.mdmarkdown4.5 KB

references/workflows.md

View on GitHub
# Workflow Details

Detailed step-by-step instructions for the Monte Carlo Asset Health skill.
Referenced from the main SKILL.md — consult when executing the workflow.

---

## Asset Health Check

When the user asks about the health or status of a data asset, run this sequence.

### Phase 1 — Resolve the asset

Run both calls in parallel:

```
search(query="<table_name>")
→ Returns MCON, full_table_id, and properties (tags)

get_mc_webapp_url()
→ Returns the base Monte Carlo webapp URL (MC_WEBAPP_URL)
```

Save the webapp URL for constructing alert links later.

Save the MCON for subsequent calls. Save properties for the Tags line in the
report. If multiple results are returned, present them in a table with these
exact columns and ask which one they want to check. Do not pick one automatically
or make assumptions.

```
| # | Table (full_table_id) | Warehouse | Importance | Key Asset |
|---|----------------------|-----------|------------|-----------|
| 1 | db:schema.table      | my-wh     | 0.99       | Yes       |
```

Every row must include the Warehouse column.

### Phase 2 — Gather health metrics (ALL in parallel)

Run all 4 calls in a single turn:

```
get_asset(mcon="<mcon>")
→ last updated, row count, importance score, is_important (key asset flag)

get_alerts(created_after="<7 days ago>", created_before="<now>", table_mcons=["<mcon>"], statuses=["NOT_ACKNOWLEDGED", "ACKNOWLEDGED", "WORK_IN_PROGRESS"])
→ active alerts on this asset

get_monitors(mcons=["<mcon>"])
→ monitor configs — check status field for paused vs active

get_asset_lineage(mcons=["<mcon>"], direction="UPSTREAM", hops=1)
→ 1-hop upstream parent assets
```

For the `get_alerts` time range, compute ISO 8601 timestamps from the current
date — e.g. `created_before` = now (`2026-07-10T00:00:00Z`) and `created_after`
= 7 days earlier (`2026-07-03T00:00:00Z`), using the actual current date.

### Phase 3 — Check upstream health (ALL parents in parallel)

Check at most **10** upstream parents. If there are more than 10, check the first
10 and note: "N more upstream parents not checked — ask to see more."

For each upstream parent, run both calls in parallel:

```
get_asset(mcon="<parent_mcon>")
→ freshness, importance

get_alerts(created_after="<7 days ago>", created_before="<now>", table_mcons=["<parent_mcon>"], statuses=["NOT_ACKNOWLEDGED", "ACKNOWLEDGED", "WORK_IN_PROGRESS"])
→ active alerts on this parent
```

All parents are checked in parallel with each other. Each parent's `get_asset` and
`get_alerts` are also parallel (no dependency between them).

### Phase 4 — Synthesize the health report

Assemble findings into the report format defined in SKILL.md:

1. **Tags** — from `search` properties. Omit line if none.
2. **Status** — determine from alerts and monitoring:
   - 🔴 if any alerts returned (the statuses filter already limits to active alerts)
   - 🟡 if no alerts but 0 active monitors on a high-importance asset
   - 🟢 otherwise
4. **Metrics table** — freshness, volume, alerts, monitoring, importance, upstream
5. **Active Alerts** — list each with type and status
6. **Upstream Issues** — list each parent with health status
   - If any parent is unhealthy, ask: "Want me to check further upstream for **\<parent\>**?"
7. **Recommendations** — only facts derivable from data:
   - Upstream issues that may explain this asset's problems
   - Alerts needing attention

### Monitoring assessment

When evaluating monitors from `get_monitors`:

- Count only **active** (non-paused) monitors
- A paused monitor does NOT count as active coverage
- Report: "N active monitors" or "N monitors (M paused)"
- Signal: ≥1 active = 🟢, 0 active = 🔴

---

## Upstream Drill-Down

When the user requests deeper upstream investigation for a specific parent:

### Phase 1 — Get upstream of the specified parent

```
get_asset_lineage(mcons=["<parent_mcon>"], direction="UPSTREAM", hops=1)
→ 1-hop upstream of the parent (grandparents of the original asset)
```

### Phase 2 — Check grandparent health (ALL in parallel)

For each grandparent:

```
get_asset(mcon="<grandparent_mcon>")
get_alerts(created_after="<7 days ago>", created_before="<now>", table_mcons=["<grandparent_mcon>"], statuses=["NOT_ACKNOWLEDGED", "ACKNOWLEDGED", "WORK_IN_PROGRESS"])
```

### Phase 3 — Report

Present findings for this hop. If any grandparent has issues, again ask:
"Want me to check further upstream for **\<grandparent\>**?"

Each drill-down is exactly 1 hop. Never auto-cascade. Always wait for user request.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall