Update to Listint

{
  "description": "Compare several UAE property listings from Listint side by side on price, price per sqft, size, bedrooms, location, developer and completion status, and explain which suits a stated priority such as budget, space or move-in readiness. Use after a Listint search when someone asks to compare, rank, shortlist or choose between listings, or asks which is better value. Do not use to compare properties that did not come from Listint, or to give investment, mortgage or valuation advice.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 370
    }
  ],
  "name": "compare-listings",
  "skill_md_contents": "---\nname: compare-listings\ndescription: Compare several UAE property listings from Listint side by side on price, price per sqft, size, bedrooms, location, developer and completion status, and explain which suits a stated priority such as budget, space or move-in readiness. Use after a Listint search when someone asks to compare, rank, shortlist or choose between listings, or asks which is better value. Do not use to compare properties that did not come from Listint, or to give investment, mortgage or valuation advice.\n---\n\n# Comparing Listint listings\n\nUse this once `search_listings` has returned results the user wants weighed\nagainst each other. Compare only listings actually returned by Listint.\n\n## Build the comparison from real fields\n\nPut the listings in a table, one row each, with the columns that matter for the\nquestion asked. Useful columns, all straight from the result:\n\n`price_label` · `category` · `bedrooms` · `bathrooms` · `area` · `location` ·\n`property_type` · `agency` · `developer` · `completion_status` ·\n`completion_percentage`\n\nDerive **price per sqft** as `price / area`, rounded to the nearest dirham, and\nlabel it in AED/sqft. It is usually the single most useful column, because it\nseparates \"cheap\" from \"good value\".\n\nOnly compute it when both `price` and `area` are present. Where either is\nmissing, write \"n/a\" — never estimate a price or a size, and never carry a\nfigure over from a similar listing.\n\n## Say what the numbers mean\n\nAfter the table, give a short read of it against whatever the user actually\ncares about:\n\n- **Budget** — lowest total price, and separately the best price per sqft; these\n  are often different listings, which is worth pointing out.\n- **Space** — largest `area`, and bedrooms relative to size, since a large\n  bedroom count in a small area means small rooms.\n- **Move-in readiness** — `completion_status` of `Ready` beats `Off Plan`; for\n  off-plan, `completion_percentage` shows how far along it is.\n- **Location** — group by `location` so the comparison is like-for-like; a\n  cheaper listing in a different community is not really a cheaper equivalent.\n\nKeep it to a few sentences. State the trade-off rather than declaring a single\nwinner, unless the user gave one clear priority.\n\n## Boundaries\n\n- **Never put a sale price and a rent in the same comparison.** Check `category`\n  on every listing first: `Sale` is a purchase price and `Rent` is an annual\n  rent, so comparing them, or deriving one price-per-sqft column across both,\n  produces a meaningless answer. Compare within one category and say why if the\n  user's shortlist mixed them.\n- A missing price means it is not published. Say \"price on request\"; do not\n  treat it as the cheapest option or leave it out silently.\n- `completion_percentage` is construction progress. It is not a score, a\n  discount, or a measure of quality.\n- Comparing listings is not valuation. Do not project appreciation, rental\n  yield, or return on investment, and do not advise on financing.\n- Link each listing by its `url` so the user can open any of them.\n"
}