Update to Nowistay

{
  "name": "nowistay-calendar-revenue",
  "description": "Review and safely update Nowistay calendar availability, nightly rates, minimum or maximum stays, stop-sell rules, and arrival or departure restrictions. Use for pricing changes, bulk date-range updates, weekday rules, availability checks, and revenue-management tasks.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 462
    }
  ],
  "skill_md_contents": "---\nname: nowistay-calendar-revenue\ndescription: Review and safely update Nowistay calendar availability, nightly rates, minimum or maximum stays, stop-sell rules, and arrival or departure restrictions. Use for pricing changes, bulk date-range updates, weekday rules, availability checks, and revenue-management tasks.\n---\n\n# Nowistay Calendar and Revenue\n\nRead the current state before changing it, and change only fields the user requested.\n\n## Review\n\n1. Resolve the target properties once with `list_properties`.\n2. Call `get_calendar_ari` for each target property and exact date range.\n3. Summarize current availability, rates, and stay rules. Keep property currencies separate and preserve local dates.\n\nDo not infer that a date is available from the absence of a booking alone. Use calendar availability as the source of truth.\n\n## Update\n\n1. Translate the request into an exact property, date range, optional weekdays, and only the fields to change.\n2. Do not send availability, price, stay rules, or restrictions that the user did not ask to modify.\n3. Use `update_calendar_ari_preview` once per property. For weekday updates, use 0=Monday through 6=Sunday and never send an empty `days_of_week` list.\n4. Summarize the staged changes by property, dates, weekdays, rate, and rules.\n5. If the user asked only for a proposal or preview, stop. If the user explicitly asked to apply the change, continue through the platform confirmation with the matching `update_calendar_ari_confirm` token.\n\nFor portfolio-wide updates, collect one approval token per property and confirm each token exactly once. Never rebuild the update payload during confirmation.\n\n## Guardrails\n\n- Do not silently convert currencies or copy one property's absolute rate to properties using another currency.\n- Do not close dates, set stop-sell, or change arrival/departure restrictions unless explicitly requested.\n- When the request is ambiguous between a percentage change and an absolute rate, ask one focused clarification before staging.\n- Report partial failures per property without repeating successful updates.\n"
}