Update to Popety.io

{
  "description": "Asking rents by rooms and per m², rent trend and inventory mix for a Swiss commune. Use when the user asks about rents, asking rents, rental market, rent levels or rent trends in a commune.",
  "included_files": [
    {
      "relative_path": "references/popety-kit.html",
      "size_in_bytes": 17333
    }
  ],
  "name": "rental-market-overview",
  "skill_md_contents": "---\nname: rental-market-overview\ndescription: \"Asking rents by rooms and per m², rent trend and inventory mix for a Swiss commune. Use when the user asks about rents, asking rents, rental market, rent levels or rent trends in a commune.\"\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# Rental market overview\n\nAsking rents by rooms and per m², rent trend and inventory mix for a Swiss commune.\n\n**Arguments to collect from the user:**\n\n- `municipality` — Municipality name, e.g. \"Lausanne\" or \"Zürich\". (required)\n\n## Workflow\n\nProduce the rental-market document for <municipality>, from live listings. entity_stats on listings is SECTION-based (0.50 credits per call; the 4 core calls = 2.00 credits). Listings section filters accept ONLY municipality / district / canton / postal_code / bbox + property_type (an ARRAY) + deal_type (\"sale\" | \"rent\", REQUIRED) + date_from / date_to (ISO with T+Z) + active (boolean) — no rooms/price filters. active: true = the CURRENT asking market; if a section returns too few listings for a small commune, retry without active but with date_from 12 months back. Follow these steps exactly:\n\n1. RENT BY ROOM COUNT (0.50 cr)\n   Call entity_stats with:\n   { entity_type: \"listings\", filters: { municipality: \"<municipality>\", deal_type: \"rent\", active: true },\n     section: \"price_per_room\" }\n   Extract: all-rooms median/average, median + p30–p70 per room band, and the property-type mix (apartments vs parking/commercial/rooms counts).\n\n2. RENT PER M² BY ROOM COUNT (0.50 cr)\n   Call entity_stats with:\n   { entity_type: \"listings\", filters: { municipality: \"<municipality>\", deal_type: \"rent\", active: true },\n     section: \"price_m2_per_room\" }\n   The per-m² view inverts the story — small flats pay the premium. Present BOTH units for the by-rooms figures (CHF/month and CHF/m²; in an artifact, a unit toggle).\n\n3. RENT TREND (0.50 cr)\n   Call entity_stats with:\n   { entity_type: \"listings\", filters: { municipality: \"<municipality>\", deal_type: \"rent\", property_type: [\"apartment\"] },\n     section: \"price_evolution\" }\n   Quarterly median asking rent for newly listed apartments. Read the last ~6 years; compute the 12-month change for the KPI row.\n\n4. TIME TO LET (0.50 cr)\n   Call entity_stats with:\n   { entity_type: \"listings\", filters: { municipality: \"<municipality>\", deal_type: \"rent\", date_from: \"<12 months ago, ISO with T+Z>\" },\n     section: \"distribution\" }\n   Read time_on_market: share let within 30/60/90 days and the average — the absorption-speed section.\n\n5. ROOMS × SURFACE MATRIX (recommended — per-object cost, preview first)\n   search_entities listings { area: { municipality: \"<municipality>\" }, transaction_type: \"rent\", property_type: \"apartment\", active: true } with preview: true FIRST (typically ~100–150 ads ≈ 5–8 credits; skip if the user is cost-sensitive); then compute the median rent per rooms × surface-band cell.\n\n6. THE DOCUMENT (blueprint — follow the kit)\n   - Verdict + 4 KPIs: median apartment rent · median CHF/m²·mo · average days to let · trend vs the series trough or 12 months back\n   - \"Rent by rooms\": band chart (p30–p70 + median tick) with a CHF/month ↔ CHF/m² unit toggle; the m² view inverts the story (small flats pay the premium) — say so\n   - \"Where rooms and surface meet\": the matrix as a heatmap (if step 5 ran), fading cells under 3 ads; name the volume cell — it is the reference product\n   - \"Rent trend\": quarterly line since ~2020, trough/peak annotated, last quarter emphasised; the analyst paragraph covers reversionary upside on older tenancies\n   - \"How fast homes let\": DOM bands with % labels; analyst paragraph on pricing power at this absorption speed\n   - One line on the non-apartment inventory mix (parking/commercial counts)\n   Notes-line: asking rents, not contract rents; sparse bands. Next step: /popety:listing-hunter for a client shortlist, or /popety:purchase-market-overview for the sale side — offer the more relevant one.\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"
}