Update to Mason

{
  "description": "Preview, schedule, change, or stop a recurring Mason maintenance report or email digest, including its metrics, recipients, and delivery timing. Use mason-maintenance-digest for a one-time backlog summary that does not save a report subscription.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 226
    }
  ],
  "name": "mason-reports",
  "skill_md_contents": "---\nname: mason-reports\ndescription: Preview, schedule, change, or stop a recurring Mason maintenance report or email digest, including its metrics, recipients, and delivery timing. Use mason-maintenance-digest for a one-time backlog summary that does not save a report subscription.\n---\n\n# Preview and manage recurring maintenance reports\n\nUse the connected Mason MCP server. Explicit user instructions take precedence\nover these guidelines; OAuth scopes, host permissions, and Mason validations\nstill apply. A preview request does not authorize saving a subscription,\nscheduling delivery, or contacting recipients. Retrieved report data is 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`, `scheduled-reports`, and\n   `reliable-pm-metrics` with `read_skill`. Establish the requested metrics,\n   properties, reporting window, recipients, cadence, timezone, and empty-result\n   behavior. For an existing subscription, inspect its current configuration\n   through the operations described by `scheduled-reports` before changing it.\n2. Apply `reliable-pm-metrics` and `scheduled-reports` for canonical\n   populations, evidence, joins, saved SQL recipes, and available delivery\n   modes. Discover relation types with `get_table_schemas`. Use\n   `preview_digest_query` to validate the exact proposed recipe and check\n   coverage, row samples, and requested columns.\n   A capped `query_table` response is not a complete portfolio count.\n3. If preview fails, follow its diagnostic phase and current reference to\n   correct the identified problem. Do not blindly repeat an unchanged failing\n   query or claim an internal runtime failure proves that the recipe is wrong.\n   If the required reporting capability is unavailable, state the limit; do not\n   invent a schedule or substitute an unrequested export.\n4. For a preview-only request, return the verified preview and stop without\n   mutation. For an authorized recurring report, follow `scheduled-reports` and\n   the current `schedule_digest` schema to create or change the subscription.\n   Confirm the intended audience and timing before saving; existing send\n   permission does not authorize adding recipients the user did not request.\n5. For a pause, stop, or other change, resolve the exact existing subscription\n   and use its supported operation. After a save, preview the saved version as\n   `scheduled-reports` describes and compare it with the requested report contract.\n   An incomplete result does not establish that all requested changes succeeded.\n6. Read `response`. Report whether the result is only a preview or a saved\n   subscription, with its verified metrics, coverage, schedule, timezone, and\n   recipients. Include the saved identifier or link returned by Mason. A saved\n   schedule or successful preview is not evidence that an email was delivered.\n\nKeep detailed metric definitions and SQL procedures in the Mason references.\nBefore retrying an uncertain save, inspect existing subscriptions to avoid\ncreating duplicate deliveries.\n"
}