From cre-skills
Plans, budgets, and coordinates tenant appreciation events, seasonal programming, and community engagement for commercial real estate properties. Supports API-driven vendor booking.
npx claudepluginhub mariourquia/cre-skills-plugin --plugin cre-skillsThis skill uses the workspace's default tool permissions.
Plans, budgets, and coordinates tenant appreciation events, seasonal programming, and community engagement activities for commercial real estate properties. Operates in two modes: plan-only (current) and plan-and-book (future API-integrated via MCP servers).
Orchestrates property management workflows across commercial real estate asset types, triaging tenant relations, maintenance, financial ops, vendors, compliance, capital planning, and benchmarking.
Automates tenant management and lease operations via AppFolio APIs with error handling for auth/endpoint issues. For property management SaaS integrations.
Manages Wix Events via API: query/filter events by status/date, create/update events, handle tickets, RSVPs, guest lists, check-ins, orders, revenue analytics, CMS integration.
Share bugs, ideas, or general feedback.
Plans, budgets, and coordinates tenant appreciation events, seasonal programming, and community engagement activities for commercial real estate properties. Operates in two modes: plan-only (current) and plan-and-book (future API-integrated via MCP servers).
Trigger this skill when the user asks about:
Keywords: tenant event, appreciation event, holiday party, tenant engagement, community event, property event planning, seasonal programming, tenant retention events, vendor booking.
property:
name: string # Property name
type: enum [multifamily, office, mixed_use, retail, industrial]
units_or_tenants: integer # Number of units (MF) or tenant companies (office)
total_occupants: integer # Estimated headcount across all tenants
sf: integer # Total leasable SF
class: enum [A, B, C] # Property class
amenity_spaces: list[string] # Available on-site spaces (lobby, rooftop, courtyard, conference center, pool deck)
location_metro: string # Metro area for vendor search radius
event_request:
event_type: enum [appreciation, seasonal, wellness, networking, community, holiday, move_in_welcome, milestone, food_truck, pet_friendly, kids_family, outdoor_movie, charity, decoration_reveal]
budget:
total: float # Total budget in USD
# OR
per_unit: float # Budget per unit/tenant
currency: string # Default USD
target_date: date # Preferred event date
season: enum [spring, summer, fall, winter] # If no specific date
duration_hours: float # Expected event duration
indoor_outdoor: enum [indoor, outdoor, hybrid]
tenant_demographics: # Optional
type: enum [residential, commercial, mixed]
family_friendly: boolean
corporate_formality: enum [casual, business_casual, formal]
pet_friendly: boolean
dietary_considerations: list[string] # vegetarian, vegan, halal, kosher, gluten-free, nut-free
age_distribution: enum [young_professional, mixed_age, family_heavy, senior]
execution_mode: enum [plan_only, plan_and_book]
# plan_only: generate full event plan with vendor specs and RFP templates
# plan_and_book: (future) execute vendor search, quoting, and booking via MCP tools
vendor_preferences: # Optional
preferred_vendors: list[string] # Vendor names to prioritize
excluded_vendors: list[string] # Vendors to avoid
max_vendor_count: integer # Cap on number of vendors to engage
local_radius_miles: integer # Search radius for local vendors, default 25
This is the active mode. All output is advisory; no external API calls are made.
Step 1 -- Event Concept Generation
references/event-playbook.md for type-specific benchmarksStep 2 -- Budget Breakdown
Step 3 -- Timeline
Step 4 -- Vendor Requirements Specification
references/vendor-booking-schemas.yaml for structured specsStep 5 -- Tenant Communication Plan
Step 6 -- ROI Projection
references/event-roi-model.mdStep 7 -- Post-Event Debrief Template
Activates when execution_mode: plan_and_book and required MCP servers are connected. Includes all Mode A steps plus automated vendor engagement.
Step 8 -- Vendor Search via MCP
Step 9 -- Quote Comparison
Step 10 -- Approval Gate
Step 11 -- Booking Confirmation
Step 12 -- Vendor Coordination
Step 13 -- Day-of Logistics
Step 14 -- Post-Event Settlement
This section defines how the skill transitions from Mode A to Mode B when MCP servers become available for vendor services.
mcp_integrations:
catering:
providers: [ezCater, CaterCow, Fooda, local_vendors]
actions:
- search_menus:
input: {location, date, headcount, dietary_reqs, budget_range, cuisine_type}
output: {vendor_list: [{name, menu_options, price_per_head, rating, min_order}]}
- get_quotes:
input: {vendor_id, menu_selections, headcount, date, time, delivery_address}
output: {quote_id, line_items, total, tax, delivery_fee, cancellation_policy}
- place_order:
input: {quote_id, payment_method, contact_info, special_instructions}
output: {order_id, confirmation, estimated_delivery, vendor_contact}
approval_gate: true
- modify_order:
input: {order_id, changes}
output: {updated_order, price_delta, confirmation}
- cancel_order:
input: {order_id, reason}
output: {cancellation_confirmation, refund_amount, refund_timeline}
data_flow: event_spec -> menu_search -> quote_comparison -> approval -> booking -> confirmation
entertainment:
providers: [GigSalad, Thumbtack, local_agencies]
actions:
- search_performers:
input: {location, date, event_type, genre_or_category, duration, budget_range}
output: {performer_list: [{name, category, price, rating, availability, media_samples}]}
- check_availability:
input: {performer_id, date, time, duration}
output: {available, alternate_dates}
- get_quotes:
input: {performer_id, date, time, duration, venue_details, requirements}
output: {quote_id, price, includes, rider_requirements, cancellation_terms}
- book:
input: {quote_id, payment_method, contact_info, venue_access_details}
output: {booking_id, confirmation, performer_contact, setup_requirements}
approval_gate: true
data_flow: event_spec -> performer_search -> availability_check -> quote -> approval -> book
rentals:
providers: [CORT_Events, Party_Rental_Ltd, local_rental_companies]
actions:
- search_inventory:
input: {location, date, items_needed: [{category, quantity, style_preference}]}
output: {available_items: [{item, options, price_per_unit, delivery_fee}]}
- check_availability:
input: {item_ids, date_range}
output: {availability_status, alternatives_if_unavailable}
- get_quotes:
input: {item_selections, delivery_date, pickup_date, delivery_address}
output: {quote_id, line_items, delivery_fee, total, damage_waiver}
- reserve:
input: {quote_id, payment_method, contact_info, access_instructions}
output: {reservation_id, confirmation, delivery_window, pickup_window}
approval_gate: true
data_flow: event_spec -> inventory_search -> availability -> quote -> approval -> reserve
venue_services:
providers: [building_amenity_system, common_area_booking]
actions:
- check_availability:
input: {space_id, date, start_time, end_time, setup_buffer, teardown_buffer}
output: {available, conflicts, alternate_times}
- reserve_space:
input: {space_id, date, time_range, event_description, setup_requirements}
output: {reservation_id, confirmation, rules_and_restrictions}
- setup_requirements:
input: {reservation_id, furniture_config, av_needs, power_requirements}
output: {work_order_id, estimated_cost, scheduling_confirmation}
data_flow: event_spec -> space_search -> availability -> reserve -> setup_order
communications:
providers: [Mailchimp, building_app, AppFolio, Yardi]
actions:
- create_invite:
input: {event_details, template_style, recipient_list_or_segment, rsvp_enabled}
output: {draft_id, preview_url}
- send_blast:
input: {draft_id, send_time, channels: [email, app_push, sms]}
output: {send_confirmation, recipient_count, delivery_stats}
approval_gate: true
- track_rsvps:
input: {event_id}
output: {total_invited, rsvps_yes, rsvps_no, rsvps_pending, dietary_responses}
- send_reminders:
input: {event_id, reminder_type: [3_day, day_of, post_event_thanks]}
output: {send_confirmation, recipient_count}
data_flow: event_plan -> invite_draft -> approval -> send -> track_rsvps -> reminders
When an MCP integration is unavailable, the skill degrades gracefully:
| Integration | Available | Unavailable Fallback |
|---|---|---|
| Catering | Search menus, get quotes, book | Generate RFP with specs, suggest local vendors to contact manually |
| Entertainment | Search performers, book | Generate performer requirements brief, suggest booking platforms |
| Rentals | Search inventory, reserve | Generate rental list with quantities, suggest rental companies |
| Venue services | Check/reserve building spaces | Generate space reservation request for property management |
| Communications | Send invites, track RSVPs | Generate email/flyer copy, provide RSVP tracking spreadsheet template |
Every action involving financial commitment requires explicit human approval:
1. Plan generated -> user reviews plan
2. Vendors selected -> user approves vendor shortlist
3. Quotes received -> user approves specific quote
4. Booking initiated -> user confirms booking (BLOCKING)
5. Payment processed -> user authorizes payment (BLOCKING)
No autonomous spending. The skill recommends; the human decides.
The final deliverable is a structured event plan document:
# [Event Name] -- Event Plan
## Property: [name] | Date: [date] | Budget: [$total]
### 1. Event Concept
- Theme and description
- Target attendance and demographics
- Space and layout plan
- Weather contingency (if applicable)
### 2. Budget
| Line Item | Budgeted | % of Total | Notes |
|---|---|---|---|
| Catering | $X | X% | [details] |
| Entertainment | $X | X% | [details] |
| ... | ... | ... | ... |
| **Total** | **$X** | **100%** | |
### 3. Timeline
[Week-by-week countdown with milestones]
### 4. Vendor Specifications
[Per-vendor scope, RFP template or booking confirmation]
### 5. Communications Plan
[Message schedule with draft copy]
### 6. ROI Projection
[Attendance forecast, retention impact, cost-per-attendee, ROI calculation]
### 7. Post-Event Debrief Template
[Survey questions, metrics to capture, vendor evaluation form]
Flag and warn the user about:
This skill connects to other CRE skills in the ecosystem:
tenant-retention-engine: Event attendance and satisfaction data feed retention scoringproperty-operations-admin-toolkit: Event logistics coordinate with building operations (elevator holds, parking, security, cleaning)property-performance-dashboard: Event spending and tenant satisfaction metrics roll into property-level KPIsannual-budget-planner allocates the tenant events line item that this skill spends against