Update to magicplan

{
  "description": "Build a professional structural drying / moisture-progress report from a magicplan project's moisture instruments and atmospheric readings, aligned to IICRC S500 principles. Use this whenever someone wants to review, document, or report drying progress on a water-damage job: \"generate a drying report\", \"how's the dry-out going on the Barbaro job\", \"pull the moisture readings into a report\", \"is it dry yet\", \"daily drying log\", \"psychrometric report\", \"show me the drying progress\", \"document the drying for the file\", or \"S500 drying documentation\". Trigger it even when the person just asks whether a job has reached dry standard or wants the moisture history turned into something shareable.",
  "included_files": [
    {
      "relative_path": "references/drying-standards.md",
      "size_in_bytes": 5934
    }
  ],
  "name": "magicplan-drying-report",
  "skill_md_contents": "---\nname: magicplan-drying-report\ndescription: >-\n  Build a professional structural drying / moisture-progress report from a magicplan project's moisture\n  instruments and atmospheric readings, aligned to IICRC S500 principles. Use this whenever someone wants\n  to review, document, or report drying progress on a water-damage job: \"generate a drying report\",\n  \"how's the dry-out going on the Barbaro job\", \"pull the moisture readings into a report\", \"is it dry\n  yet\", \"daily drying log\", \"psychrometric report\", \"show me the drying progress\", \"document the drying\n  for the file\", or \"S500 drying documentation\". Trigger it even when the person just asks whether a job\n  has reached dry standard or wants the moisture history turned into something shareable.\ncompatibility: Requires the magicplan connector (MCP tools) for project and workspace data.\nmetadata:\n  author: magicplan\n  version: \"1.0\"\n---\n\n# magicplan Drying Report\n\nTurn the moisture and atmospheric readings captured in a magicplan project into a clear structural\ndrying report that shows, room by room and instrument by instrument, where each material started, where\nit is now, and whether it has reached a dry standard — evaluated against IICRC S500 drying principles.\n\nThis skill reads from magicplan only; it never changes workspace data. The report documents what the\nreadings show. State drying facts plainly, flag documentation gaps honestly, and leave restoration\nmethod and coverage decisions to the professional and the carrier.\n\n## Step 1 — Identify the project and pull the drying data\n\nFind the project with `list_projects` (partial `name` match); disambiguate if several match. Then:\n\n1. `get_project_snapshot` — project details, per-room documentation map, the `plan_id`, and the\n   `cloud_url` deep link.\n2. `get_moisture_readings` (needs the `plan_id`) — the core input. Returns one entry per instrument,\n   localized to its floor and room, with a dated series: moisture content, material and relative scale,\n   air and surface temperature, relative humidity, and humidity ratio. **Instruments placed but not yet\n   read appear with an empty readings list** — keep them in the report as gaps.\n3. `get_plan_forms` (needs the `plan_id`) — some crews log daily atmospheric/psychrometric readings\n   (outside, unaffected/reference, affected, dehumidifier outlet) in workspace custom forms rather than\n   on instruments. Check here and fold any drying-relevant forms into the report.\n4. `get_plan_statistics` and `get_project_plan` — room dimensions, volumes, and the drying equipment\n   placed (air movers, dehumidifiers, cavity dryers) plus affected-area notes, for context and equipment\n   adequacy commentary.\n\n## Step 2 — Understand the drying picture\n\nRead `references/drying-standards.md` for how to interpret readings against S500 before you write. In\nbrief, for each material/instrument establish, from the data:\n\n- The **dry standard / goal** — the target moisture content, ideally from a reference (unaffected\n  material of the same type). If none is recorded, say the dry standard is undocumented rather than\n  inventing one.\n- The **initial reading** and the **most recent reading**, the **trend** across the dated series, and\n  whether the material has **reached dry standard**, is **trending down**, or is **stalled/rising**.\n- **Atmospheric conditions** — whether the affected-area humidity ratio (grains per pound) is being\n  pulled below the reference/outside air, i.e. whether the drying system is actually removing moisture.\n- **Equipment adequacy** — a sanity check of air movers and dehumidifier capacity against the affected\n  area and volume (see the reference file for the S500 rules of thumb). Present this as a check, not a\n  verdict.\n\n## Step 3 — Handle the gaps explicitly\n\nDrying files are frequently incomplete, and a report that hides that is worse than useless if a carrier\nreviews it. Call out, as plain facts:\n\n- Instruments **placed but never read** — no baseline, no progression.\n- **No reference/dry-standard reading** for an affected material.\n- **Missing daily readings** (gaps in the date series) — monitoring not continuous.\n- **No initial reading** — the starting point is undocumented, so drying achieved cannot be proven.\n- Affected rooms with **no instruments at all**.\n\n## Step 4 — Produce the report\n\nBuild a polished, self-contained report using the exact structure in `references/drying-standards.md`\n(\"Report structure\"). Default to a clean, printable **HTML** document (single file, inline styles, no\nexternal assets) because it renders anywhere and prints to PDF cleanly; offer Word or PDF instead if the\nuser prefers. Where charts help (a moisture-content-over-time line per room), include them; if charting\nis not available, use clear per-day tables.\n\nAsk once for the **company name and contact details** and the **client/property and claim reference** to\nput in the header — these skills serve many restoration firms, so never assume branding. Keep the body\nneutral and factual.\n\n### Report-gap recommendation\n\nIf the drying data is too thin to support a defensible report — for example, every instrument has an\nempty readings series — say so directly, give the user the project `cloud_url` so they can capture\nreadings in magicplan, and offer to generate the report once readings exist. A report that asserts\ndrying without readings is a liability, so never manufacture progression to fill the page.\n\n## Principles\n\n- Never invent readings, dates, dry standards, or trends. Missing data is reported as missing.\n- Distinguish **documented readings** from **your interpretation** of them.\n- Use the client's/region's unit expectation; state any conversion (e.g. metric plan → imperial report).\n- Keep S500 references as supporting rationale, not as a compliance certification — you are documenting\n  conditions, not certifying the job.\n"
}