Update to Propalt

{
  "name": "blog-post-writer",
  "description": "Use when an estate or letting agent asks for a UK property blog post, news article, local market update, website article, or topic ideas that should be grounded in Propalt property or market data. Match an existing brand voice when the user supplies examples or a website can be accessed; do not require web access or a Word-document runtime to complete the writing task.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 426
    }
  ],
  "skill_md_contents": "---\nname: blog-post-writer\ndescription: \"Use when an estate or letting agent asks for a UK property blog post, news article, local market update, website article, or topic ideas that should be grounded in Propalt property or market data. Match an existing brand voice when the user supplies examples or a website can be accessed; do not require web access or a Word-document runtime to complete the writing task.\"\n---\n\n# Blog Post Writer\n\nWrite useful local property content backed by real Propalt facts.\n\n## Workflow\n\n1. Establish the intended area, audience, topic, and approximate length. If the user has no topic, use relevant Propalt market data to suggest two or three angles.\n2. If the user supplies prior articles or accessible website content, mirror the useful parts of the tone and structure. If that content cannot be accessed, ask only for a short tone preference when it materially affects the result; otherwise use a warm, direct, knowledgeable estate-agent voice.\n3. Pull only the Propalt data needed for the article. Typical choices:\n   - `get_monthly_market` / `get_quarterly_market` for trends;\n   - `get_hpi` for HPI history from a full postcode;\n   - `selling_property_market_activity_properties_for_sale_post` or `letting_property_market_activity_properties_for_let_post` for current stock;\n   - `get_comparable_by_property_id` for a resolved property's evidence;\n   - `get_nearby_schools`, `get_nearby_transport`, or `get_nearby_amenities` for supported location content;\n   - `get_demographics`, `get_households`, `get_income`, or `get_crime` only with supported geographic inputs and only as aggregate area context.\n4. Write the article around 3–5 meaningful facts rather than dumping statistics.\n5. Attribute Propalt-derived figures clearly as Propalt data. If external current context is needed and available, attribute it separately rather than presenting it as Propalt data.\n\n## Writing rules\n\n- No fabricated local facts, streets, prices, catchments, or statistics.\n- Do not claim a school catchment from `get_nearby_schools`; it provides proximity, not catchment eligibility.\n- Avoid em dashes and stock AI phrasing. Use concrete local language and short paragraphs.\n- Do not make claims about a particular resident from aggregate demographic data.\n- If a requested statistic is unavailable, omit it or say it is unavailable instead of filling the gap from memory.\n\n## Delivery\n\nReturn a publish-ready article in chat by default. If the user explicitly requests a `.docx` and the host provides document-generation capability, create the file; otherwise provide clean copy that can be pasted into a CMS or Word. Do not make successful completion depend on installing packages.\n"
}