Dealership Group PluginLightweightCommand
/onboarding
Set up your dealer group profile with all locations
$/onboarding
Lightweight
Complexity
0
API Calls
$0.00 – $0.00
MC API Cost
$0.01 – $0.03
Total Cost
Purpose
Creates or updates the marketcheck-profile.md project memory file for a dealer group — capturing all locations (name, ZIP, radius, franchise brands), group-level preferences, and the operator context needed to personalize every subsequent skill run.
Audience:Dealer group operatorsDealer principalsIT administrators
How It Works
Execution flow. MCP tool calls are shown inline on each step.
01
Group Identity
Collect dealer group name, total number of locations, and whether the group is publicly traded.
02
Location Details
For each location: collect store name, ZIP code, market radius, franchise brands (or independent), and default inventory type.
03
Profile Write
Write the complete marketcheck-profile.md to the project directory with all locations, group metadata, and preferences.
Example Output
ONBOARDING COMPLETE — Sunrise Auto Group ══════════════════════════════════════════ Profile written to: marketcheck-profile.md Group: Sunrise Auto Group | 3 Locations | Franchise 1. Orlando North | ZIP 32801 | 50-mile radius | Honda, Acura 2. Orlando South | ZIP 32809 | 40-mile radius | Honda 3. Tampa West | ZIP 33601 | 45-mile radius | Honda, Toyota Default inventory type: used Profile ready. Run /daily-briefing to start your first group briefing.
Cost Estimate
TierLightweight
API Calls0
MC API — best$0.00
MC API — worst$0.00
Claude — best$0.01
Claude — worst$0.03
Total range$0.01 – $0.03
Limitations
- Profile accuracy depends on user-provided location data — incorrect ZIPs or radii will affect all subsequent skill runs.
- Franchise brand names must match MarketCheck make nomenclature for accurate data pulls.
Dealership Group Plugin
View all skills & commands