wheelhouse-skillsWheelhouse Revenue Management agent skills for the Wheelhouse MCP (mcp.usewheelhouse.com). STLY pacing, future-rate overpricing, price-change attribution, local data caches, live pickup priority lists, occupancy-vs-market charts, a portfolio map, and confirm-before-write changes to preferences, Even
COWORK-Data-SyncsPulls and caches Wheelhouse RM data (listings + KPIs, reservations, and future price calendars -- either replace-only or with dated history snapshots) to local files via a direct API key and plain scripts, no MCP/Claude in the loop for the actual HTTP calls, so other Wheelhouse skills can read from
MCP-Leaderboard-Fast-SellerBuilds a live, MCP-only Top 10 of listings selling much faster than the rest of the portfolio -- pickup in the last 14 days as a share of the next 60 days' bookable inventory -- with each listing's neighborhood-occupancy-ratio shown as context, not blended into the score. Trigger on 'which listings
MCP-Leaderboard-Poor-Occ-PickupBuilds a live, MCP-only Top 10 (or N) list of listings most worth attention today, ranked by low near-term occupancy and low recent pickup, gated to listings that are actionable (automated pricing on, enough available nights). No cache/sync skill required -- pulls straight from the connected Wheelho
MCP-Listing-Map-visualBuild an interactive, filterable HTML map of a Wheelhouse listing portfolio pulled live from the connected Wheelhouse MCP — fetching address, tags/amenities, unit name, nickname, and listing IDs directly from the tool rather than from an uploaded file — geocoding the addresses, and producing a self-
MCP-Occ-Heatmap-Segment-MarketBuilds a night-by-night occupancy heatmap for one Wheelhouse portfolio segment against the bedroom-matched market benchmark, live through the connected Wheelhouse MCP, in Wheelhouse brand colors. Use when the user wants an occupancy heatmap or calendar, a night-by-night 'occupancy vs market' view fo
MCP-custom-rate-attributionFast, single-listing check of whether Custom Rates set in the last 30 days actually got booked — the simple, custom-rates-only sibling to MCP-price-change-attribution. Trigger for "did that custom rate get booked," "check if my custom rate led to bookings," "did the rate I set on [listing] work," "d
MCP-future-rate-overpricingChecks whether a listing's future posted rates are too high (or too low) vs. what actually transacted the same calendar month last year, broken out by month and by weekend (Fri/Sat) vs. weekday (Sun-Thu). Trigger for "are my future rates too high," "check for overpricing next season," "is [listing]
MCP-price-change-attributionChecks whether recent pricing changes (custom rates, seasonal/event rules, monthly rules, base price, global minimums, day-of-week, etc.) actually correlate with subsequent bookings, over a configurable 7- or 30-day lookback. Trigger for "did that price change work," "did my rate change get bookings
MCP-segment-vs-market-occupancy-graphBuilds an interactive month-by-month occupancy line chart for one Wheelhouse portfolio segment against a market's high performers — current on-the-books position only, no last-year comparison — live through the connected Wheelhouse MCP, in Wheelhouse brand colors. Use for 'how are we pacing against
MCP-stly-pacing-calculationsRuns a Same-Time-Last-Year (STLY) pacing analysis — Nights Booked, Revenue, ADR, and Occupancy (adjusted and unadjusted) vs. the on-the-books position one year ago — for a listing or saved Wheelhouse segment, over any date range (months, a rolling day count, a named period, or explicit dates). Produ
Context-CustomRates-APIUse when a Wheelhouse client wants a script calling the RM API directly (X-Integration-Api-Key) to set, replace, combine, or remove a Custom Rate, outside a live chat turn. Covers the same fixed-vs-adjustment semantics, overlap/split behavior, and compounding math as Context-CustomRates but for unat
Context-CustomRatesUse when a Wheelhouse client wants to set, replace, combine, or remove a Custom Rate via the connected Wheelhouse MCP -- a date-range price override that overrides the pricing engine's recommendation rather than participating in the preference rule hierarchy. Covers fixed vs. adjustment rate types,
Context-Events&Seasons-APIUse when a Wheelhouse client wants a script calling the RM API directly (X-Integration-Api-Key) to create, rename, redate, or otherwise change a Season or Event (custom_date_ranges) or a rule referencing one, outside a live chat turn. Covers the same id-sharing model and blank-id protocol as Context
Context-Events&SeasonsUse when a Wheelhouse client wants to create, rename, redate, or otherwise change a Season or Event (the named date ranges under the Events & Seasons configuration group) via the connected Wheelhouse MCP, or wants to add/update a seasonal- or event-type pricing rule that references one. Covers the t
Context-Preferences-APIUse when a Wheelhouse client wants to change pricing-engine or rule-hierarchy settings via a script calling the RM API directly (X-Integration-Api-Key), outside a live chat turn -- e.g. a scheduled job, or their own backend. Covers the same settings as Context-Preferences (base price, seasonality, d
Context-PreferencesUse when a Wheelhouse client asks to change any pricing-engine or rule-hierarchy setting via the connected Wheelhouse MCP -- base price, seasonality, day-of-week, last-minute/far-future, min/max price, min stay, demand sensitivity, historical anchoring, check-in/check-out, long-term discounts, occup
Context-PriceLabsMigrationUse when a client's language or mental model comes from PriceLabs (or another pricing tool) rather than Wheelhouse -- migrating an account, building on the API with prior PriceLabs experience, or using PriceLabs terms ("Customization," "Pricing Profile," "Date-Specific Override") to describe what th