imotesa.bg

View saved version →

---
name: imotesa-neighbourhood-comparison
description: Compare observed asking-price context across Bulgarian neighbourhoods or inspect one local market segment without giving forecasts or investment advice.
---

Use this skill when a user wants evidence-based asking-price context for one Bulgarian city or neighbourhood, or a comparison of two to five neighbourhoods in the same city. Do not use it for individual properties, forecasts, lifestyle comparisons, legal advice, mortgage guidance, or investment recommendations.

## Workflow

1. For one city or neighbourhood, call `get_market_stats`. For two to five neighbourhoods in the same city, call `compare_areas`.
2. Pass names directly when they are known. Call `list_locations` only when the user needs candidate places or a location needs disambiguation.
3. Use `search_properties` or `get_property` only if the user changes the request to a specific property or active offers.

## Reporting rules

- Describe every figure as an observed asking price in EUR, not a transaction price. Rent figures are monthly.
- Prefer median price per m² and include the sample size, availability, property type, sale or rent context, and any room-count filter.
- For comparisons, explain that rank 1 is the most expensive available area and that `pct_above_cheapest` is relative to the cheapest available area.
- `available=false` means the segment has too few listings for published statistics; it does not establish that demand, supply, or prices are absent.
- If the tool reports a matched location, name the matched city or neighbourhood. If history is unavailable, say so rather than extrapolating.
- Report facts and uncertainty without predicting price movements, asserting what buyers paid, or recommending where to buy.
- Link the returned `canonical_url` when it helps the user inspect the source context.

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: imotesa-property-record
description: Inspect Bulgarian property records, current offers, and observed asking-price history when a user needs evidence about a property or a filtered set of properties.
---

Use this skill for requests to find Bulgarian properties, inspect a property's record, or understand its observed asking-price history. Do not use it for legal advice, mortgage guidance, investment recommendations, forecasts, or properties outside Bulgaria.

## Workflow

1. For a property request without a slug, call `search_properties`. Use `list_locations` only when the user needs help choosing or confirming a city or neighbourhood.
2. For a specific property, call `get_property`. If the user asks about price reductions, relisting, or time observed on the market, also call `get_property_history` with the property's slug.
3. Call `get_market_stats` only when the user asks for local price context. Do not use it to make a prediction or recommendation.
4. Link the relevant `canonical_url` in the result. Call `resolve_search_url` only when the user explicitly asks for a reusable URL; it creates or updates an internal search-page record.

## Reporting rules

- Describe all prices as observed asking prices in EUR, not transaction prices. Rent figures are monthly.
- Treat each listing history as a separate observation series. Different agencies or sellers can advertise the same property at different prices.
- Say that an inactive listing was no longer observed; do not infer a completed transaction.
- Distinguish the property record from the local market context. Prefer median figures and include sample size when citing market statistics.
- If a requested segment is unavailable or a location was matched approximately, state that clearly and offer the wider segment or resolved location returned by the tool.
- Give factual context and leave the decision to the user. Do not present a property as a recommendation or a guaranteed opportunity.

Referenced files: 1 — file references are metadata, not package contents.