Update to Nowistay

{
  "name": "nowistay-daily-brief",
  "description": "Prepare a concise cross-property operations brief from Nowistay bookings, missions, and conversations. Use for daily briefs, today's arrivals or departures, upcoming guests, urgent work, operational handovers, and questions such as \"what needs attention today?\".",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 473
    }
  ],
  "skill_md_contents": "---\nname: nowistay-daily-brief\ndescription: Prepare a concise cross-property operations brief from Nowistay bookings, missions, and conversations. Use for daily briefs, today's arrivals or departures, upcoming guests, urgent work, operational handovers, and questions such as \"what needs attention today?\".\n---\n\n# Nowistay Daily Brief\n\nBuild the brief with the fewest complete MCP calls.\n\n## Workflow\n\n1. Resolve property names and IDs once with `list_properties`. For all properties, omit `search`; paginate only when the response says more properties exist.\n2. Resolve relative dates in each property's timezone. Use `get_property` only when the timezone is needed and not already available.\n3. Fetch bookings in one portfolio-wide request whenever possible. For multi-property or broad date ranges, use `list_bookings` with `response_format=table`, `limit=500`, and `include_details=false`. Follow `resultMetadata.nextOffset` until `hasMore=false`.\n4. Fetch missions with `list_missions`. Use compact results for a small focused request; use `response_format=table` and `limit=500` for a portfolio-wide brief.\n5. Fetch conversations only when the user explicitly asks about messages or unresolved guest communication. Do not read conversations merely to enrich a general brief.\n6. Retrieve full booking, mission, report, or conversation details only for items that need explanation or action.\n\n## Brief format\n\nPresent only useful operating information, ordered by urgency:\n\n- urgent incidents or failed missions;\n- arrivals and departures with property, guest, time, and readiness risks;\n- unassigned, overdue, or blocked missions;\n- guest conversations that need a host decision;\n- a short next-actions list.\n\nUse property names in the response. Identify a guest only when the user requested guest-level information or when the identity is necessary to act on a specific arrival, departure, or conversation; otherwise identify the stay by property and dates. Never include guest email, phone, postal address, private notes, or message content in a general brief. Keep internal IDs out of the prose unless the user asks for them or they are needed to disambiguate records. If a broad query is paginated, finish every page before claiming the brief is complete.\n\n## Efficiency rules\n\n- Do not call `list_bookings` once per property when omitting `property_ids` returns the whole eligible portfolio.\n- Do not use full-detail list responses for broad requests.\n- Do not call `get_booking` or `get_mission` for every row.\n- Do not describe complete server results as truncated merely because the UI displays a shortened preview; trust `resultMetadata.hasMore` and pagination fields.\n"
}