/onboarding
Set up your analyst profile — tickers, coverage universe, and benchmarking preferences
Purpose
/onboarding creates or updates the marketcheck-profile.md project memory file with your analyst configuration: ticker watchlist, coverage universe (OEM tickers, dealer group tickers), geographic focus, and preferences. All skills read this profile to pre-populate analyses.
Arguments
How It Works
Execution flow. MCP tool calls are shown inline on each step.
Prompts for OEM tickers (F, GM, TM, STLA, etc.) and dealer group tickers (AN, LAD, PAG, etc.) to track. Uses built-in ticker→makes mapping to validate.
Asks for primary states or national scope for market share and DOM analyses.
Writes or updates marketcheck-profile.md in the project root with all settings. Confirms profile summary and suggested first command.
Example Output
ANALYST PROFILE CONFIGURED ══════════════════════════ Profile saved to: marketcheck-profile.md OEM Tickers: F, GM, TM, STLA, HYMTF, TSLA Dealer Tickers: AN, LAD, KMX, CVNA Geographic Focus: National Benchmark Period: Monthly (MoM) SUGGESTED NEXT STEPS /watchlist-scan — Scan all tickers now /market-snapshot — Quick sector state check "Earnings preview for F" — Start with your highest conviction name
Cost Estimate
One-time setup
Limitations
- Profile is stored in marketcheck-profile.md in the project directory — update it directly or re-run /onboarding to change settings.
- Ticker mapping covers major publicly traded OEMs and dealer groups; niche tickers may require manual makes mapping.