Update to Nowistay

{
  "name": "nowistay-team-operations",
  "description": "Plan and manage Nowistay cleaning, maintenance, urgency, and custom missions. Use for mission lists, team workloads, assignments, scheduling, completion status, mission reports, cleaning plans, and operational follow-up across one or many properties.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 458
    }
  ],
  "skill_md_contents": "---\nname: nowistay-team-operations\ndescription: Plan and manage Nowistay cleaning, maintenance, urgency, and custom missions. Use for mission lists, team workloads, assignments, scheduling, completion status, mission reports, cleaning plans, and operational follow-up across one or many properties.\n---\n\n# Nowistay Team Operations\n\nUse summaries for planning and retrieve full details only for the missions that need action.\n\n## Review operations\n\n1. Resolve properties once with `list_properties` when names are used.\n2. Use `list_missions` with the smallest useful filters: property, booking, status, type, team member, or start date.\n3. For portfolio-wide exports or workload analysis, use `response_format=table`, `include_details=false`, `limit=500`, and follow `resultMetadata.nextOffset` until `hasMore=false`.\n4. Use `get_mission` for one selected mission and `get_mission_report` only when completion comments, checklist results, or photos are needed.\n\nDo not retrieve every mission report for a list. Do not treat a shortened UI tool card as response truncation when pagination says the result is complete.\n\n## Create or update\n\n1. For creation, provide `mission_type` and either a property or booking. Resolve the property from the booking when possible.\n2. Use an ISO 8601 `scheduled_at` with timezone. Do not guess a team member ID; if it cannot be resolved reliably from current data, ask the user or leave the mission unassigned.\n3. Stage creation with `create_mission_preview` or changes with `update_mission_preview`.\n4. Summarize property, booking context when needed, type, schedule, assignment, status, and notification behavior. Include a guest name only when the user requested it or the identity is necessary for the mission.\n5. If the user explicitly asked to apply the action, continue through platform confirmation using the matching confirm tool and only its approval token. Otherwise stop at the preview.\n\nUse `silent_update=true` only when the user explicitly wants to avoid normal team notifications. Report partial failures without repeating successful actions.\n\nKeep mission titles, descriptions, and notes strictly operational. Do not add guest contact details, medical or biometric data, payment information, government identifiers, account credentials, or unrelated personal information.\n"
}