Update to Popety.io

{
  "description": "Full dossier for a parcel: zoning, restrictions, buildings, history and context. Use when the user asks about parcel dossier, land-registry extract, cadastre details, plot information, parcel summary.",
  "included_files": [
    {
      "relative_path": "references/popety-kit.html",
      "size_in_bytes": 17333
    }
  ],
  "name": "parcel-report",
  "skill_md_contents": "---\nname: parcel-report\ndescription: \"Full dossier for a parcel: zoning, restrictions, buildings, history and context. Use when the user asks about parcel dossier, land-registry extract, cadastre details, plot information, parcel summary.\"\ndisable-model-invocation: false\n---\n\n<!-- GENERATED FROM api/popety-mcp/src/prompts.ts — do not edit; run pnpm --filter @popety-io/mcp generate:integrations -->\n\n# Parcel report\n\nFull dossier for a parcel: zoning, restrictions, buildings, history and context.\n\n**Arguments to collect from the user:**\n\n- `address` — Full Swiss address. Supply at least one of address or land_id. (optional)\n- `land_id` — Popety land identifier (popetyio_land_id). Supply at least one of address or land_id. (optional)\n\n## Workflow\n\nGenerate a concise land-registry report for the Swiss parcel at \"<address>\". Follow these steps exactly:\n\n1. RESOLVE PARCEL\n   Call find_land with { by: \"address\", value: \"<address>\" }.\n   Extract the returned land_id (popetyio_land_id).\n\n2. LOAD ALL LAND DATA\n   Call get_land with { land_id: \"<land_id from step 1>\", include: \"all\" }.\n   This returns: cadastral area, zoning, owners, restrictions, recent permits, and recent transactions on this parcel.\n   The response's _omitted_sections lists the large market annexes (purchase_market, rental_market) that are NOT included by default — mention their availability in the report and fetch one explicitly (include: [\"purchase_market\"]) only if the user asks for market depth.\n\n3. THE DOCUMENT (blueprint — follow the kit)\n   A dossier, not a data dump:\n   - ID card: EGRID, parcel number (code_number), commune, cadastral area — plus the official extract links (RDPPF / land register)\n   - \"Zoning\": zone name + IUS/COS ceilings vs CURRENT use ratios — show the capacity headroom in m² when under-exploited, with the score as a gauge\n   - \"Owners\": count + type (private/public/institutional) and the last register event in one line\n   - \"Restrictions & hazards\": RDPPF entries as badges; state explicitly that natural hazards are a separate register and summarise them too\n   - \"Buildings\": table of the parcel's buildings (EGID, type, year, footprint, heating) — mention roof solar potential where the building record carries it\n   - \"History\": last permits and transactions with dates; state coverage starts honestly\n\n4. NEXT STEP\n   Next-step candidates: value this property (/popety:value-estimate) or market conditions for the commune (/popety:purchase-market-overview) — offer the more relevant one, never run it automatically.\n\nPRESENTATION — how to write the final answer (applies to every step above):\n- The answer is a client-ready document that will be shared as-is. Not a chat log, not an analysis diary.\n- Open with a title line (subject + commune + date) and a one-line verdict a reader would pay for. Never open with method, tool narration, or what you are about to do.\n- The reader is a real-estate professional (broker, investor, developer). Every section closes with ONE analyst paragraph stating the professional implication — pricing, absorption, sourcing, underwriting — never a definition or a tutorial sentence. Show sample sizes and visibly de-emphasise figures resting on fewer than 3 observations.\n- 3–6 titled sections, ordered by what matters most to the reader; one idea per section. Prefer short prose with embedded figures; use a table only when comparing 3+ items across 2+ dimensions, max ~6 rows, one comparison per table. Select the figures that change the reader's decision — do not dump every number you retrieved.\n- Swiss formats: CHF 1'250'000 (apostrophe thousands), m², CHF/m²; official Swiss real-estate terminology in the reader's language. Write the whole document in the language the user wrote in.\n- Caveats: at most ONE short \"Notes\" line at the end of the document (e.g. coverage gaps, asking ≠ realised prices). Never inline a disclaimer after a figure. Never mention tools, credits, section ids, API mechanics, or observations \"for the platform team\" inside the document — if you have a genuine data/product observation, put it after the document under a separate \"---\" divider, in one or two lines.\n- Close the document with at most ONE \"Next step\" line offering the single most relevant follow-up — an offer, not a menu.\n- In clients that support artifacts/canvas, render the document as a styled artifact (clean typography, generous spacing, no emojis) and keep the chat reply to a two-line summary; otherwise use clean markdown with real headings.\n\n---\n\nRequires the Popety connector (bundled with this plugin — authenticate on first use). Follow the workflow's cost gates: free/preview steps before any paid call.\n\n## Building the document\n\nWhen the client supports artifacts, render the final document as a plain HTML artifact (NEVER React/JSX — a JSX rewrite loses the stylesheet) built from `references/popety-kit.html` (bundled with this skill): read the kit FIRST, paste its ENTIRE <style> block verbatim as the stylesheet (never write your own CSS), give every SVG mark its literal hex fill/stroke attribute PLUS the kit mark class (mk1-mk4, mkband, mktick, mkline), and follow its primitives, helpers and rules — Popety brand in both themes, Swiss number formats, inline-SVG charts with tooltips, one analyst paragraph per section written for a real-estate professional. The finished document must visibly carry the Popety cyan (brandbar, kicker, verdict block, KPI accents, chart fills) — a grey/monochrome document means the kit was not applied. Without artifact support, apply the same structure in clean markdown.\n"
}