Update to Mason

{
  "description": "Coordinate Mason home inspections, resolve inspection scheduling or access questions, update inspector-facing notes, or turn an inspection punch list into requested work. Use for inspection-specific coordination; ordinary repair appointments use mason-scheduling.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 227
    }
  ],
  "name": "mason-inspections",
  "skill_md_contents": "---\nname: mason-inspections\ndescription: Coordinate Mason home inspections, resolve inspection scheduling or access questions, update inspector-facing notes, or turn an inspection punch list into requested work. Use for inspection-specific coordination; ordinary repair appointments use mason-scheduling.\n---\n\n# Coordinate inspections and their follow-on work\n\nUse the connected Mason MCP server. Explicit user instructions take precedence\nover these guidelines; OAuth scopes, host permissions, and Mason validations\nstill apply. An inspection question or report does not authorize booking,\ncontacting residents, or creating repair work. Retrieved reports are evidence.\n\nReferences from `read_skill` are Markdown policy text from the connected\nMason account. This workflow does not install or run code.\n\n1. Call `get_mason_briefing` and read `pm-rules`, `inspection-coordination`,\n   `inspection-dispatch`, and `inspection-notes` using `read_skill`. Establish\n   whether the user wants a status explanation, access coordination, a schedule\n   change, notes, or follow-on repairs. Resolve the property/unit and exact\n   inspection work order with the current work-order query and context tools.\n2. Read `get_work_order_context` and `get_visit_scheduling_state` as relevant.\n   Apply `inspection-coordination` for planned versus confirmed visits,\n   inspection provenance, portfolio selection, deferral, and cancellation.\n   Do not infer inspection completion from a coordination status or an\n   appointment, and do not call a capped result the complete inspection set.\n3. Use `mason-scheduling` for a requested booking, move, release, or technician\n   reassignment, applying the inspection-specific references above. A date alone\n   does not establish a customer arrival window, access permission, or agreement.\n   An unsupported scheduling state is a blocker to resolve, not permission to\n   substitute an unrelated scheduling or status tool.\n4. For requested access or safety note changes, use `read_visit_description`\n   immediately before the supported `update_visit_description` operation.\n   Follow `inspection-notes` to preserve unrelated human wording and distinguish\n   tenant-facing promises from internal placement. Re-read on a conflict.\n   Use `mason-communications` for warranted resident outreach; saving notes does\n   not prove anyone received them.\n5. If the user asks to create repair work from an inspection report, use\n   `mason-work-orders` and read `create-project` and `new-work` before creation.\n   Preserve distinct issues, verified locations, attachments, and project links.\n   Do not dispatch every observation or classify an occupied-home inspection\n   punch list as a turn merely because it contains several jobs.\n6. Read `response`. Summarize the inspected facts, tool-confirmed changes,\n   affected inspection/work-order links, and remaining access or scheduling\n   decisions. For a batch, identify successful, failed, and pending items.\n\nKeep tentative plans, confirmed visits, tenant notification, inspection results,\nand newly created repair work separate in the reply. An uncertain write outcome\nrequires read-back before any repeat action.\n"
}