Update to 33CRM

{
  "description": "Analyze 33CRM booking volume, attendance, no-shows, cancellations, status mix, branches, owners, and upcoming booking records. Use for appointment operations, attendance reviews, no-show analysis, and branch booking workload.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 461
    }
  ],
  "name": "booking-attendance-review",
  "skill_md_contents": "    ---\n    name: booking-attendance-review\n    description: Analyze 33CRM booking volume, attendance, no-shows, cancellations, status mix, branches, owners, and upcoming booking records. Use for appointment operations, attendance reviews, no-show analysis, and branch booking workload.\n    ---\n\n    Use this skill for booking and attendance operations.\n\nWorkflow:\n1. Resolve the requested date range.\n2. Call `get_booking_report` for total bookings, attended count/share, status breakdown, and branch breakdown.\n3. Call `list_bookings` when the user requests the actual booking records, upcoming appointments, a status filter, branch, sales rep, or lead.\n4. Call `get_booking` only for one identified booking.\n5. Call `list_branches` or `list_sales_reps` when IDs/names are needed for filters.\n\nOutput:\n- Booking volume\n- Attendance and status mix\n- Branch distribution\n- Upcoming / filtered booking list when requested\n- Operational attention items\n- Data caveats\n\nRules:\n- `attended_share_of_all_bookings` uses all bookings in the period as the denominator; it is not necessarily a completed-appointment show-up rate.\n- Do not infer treatment type, diagnosis, clinical status, or patient outcome.\n- Appointment notes and clinical fields are not available and must not be invented.\n- Reply in the user's language.\n- Read-only only.\n"
}