dom-monitor

Installation
SKILL.md

Date anchor: Today's date comes from the # currentDate system context. Compute ALL relative dates from it. Example: if today = 2026-03-14, then "prior month" = 2026-02-01 to 2026-02-28, "current month" (most recent complete) = February 2026, "three months ago" = December 2025. Never use training-data dates.

get_sold_summary parameter safety:

  • Always set inventory_type explicitly (New or Used) — omitting it defaults to New, returning zero results for used-vehicle queries
  • Always set limit: 5000 — the default (1000) silently truncates when (months × states × ranking combos) exceeds 1000 rows
  • For volume totals, use ranking_dimensions: dealership_group_name (or the single relevant dimension) — never use the default make,model,body_type which creates ~150K rows for national 3-month queries
  • Use separate calls for totals vs breakdowns — don't combine in one call
  • Sub-batch parallel calls — the upstream API rate-limits at ≤5 concurrent requests (HTTP 429 beyond that). W2 (5 periods × N makes) and W3 (4 segments × 2 months) must fire in batches of ≤5 calls per agent message; pause briefly between batches. 429 retries are forbidden within a workflow run.

DOM Monitor — Days on Market as a Leading Investment Signal

User Profile (Load First)

Load the marketcheck-profile.md project memory file if exists. Extract: tracked_tickers, tracked_makes, tracked_states, benchmark_period_months, country. If missing, ask for OEM/ticker and geography. US-only. Confirm profile.

If the user supplies a dealer-group ticker (AN, LAD, PAG, SAH, GPI, ABG, KMX, CVNA), halt with: "<TICKER> is a dealer-group stock; this skill covers OEM brand DOM only. Route to dealer-group-health-monitor for dealer-group DOM signals." The workflows below are make-based and have no dealer-group path.

User Context

Installs
2
GitHub Stars
4
First Seen
Apr 29, 2026
dom-monitor — marketcheckhub/marketcheck-cowork-plugin