Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Normalize Indian real-estate location text into canonical city and locality fields (Mumbai and Pune v1) with confidence and unresolved flags. Use when leads...
Normalize Indian real-estate location text into canonical city and locality fields (Mumbai and Pune v1) with confidence and unresolved flags. Use when leads...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Resolve messy India locality aliases into canonical location fields without side effects.
Normalize Mumbai/Pune location aliases from extracted leads. Map PCMC and Hinjewadi variants to canonical localities. Resolve Mumbai shorthand like Scruz, Khar, Andheri W, Turner Road, Carter Road. Standardize locality names before scoring or storage.
message-parser -> lead-extractor -> india-location-normalizer -> sentiment-priority-scorer Target KPI for production tuning: improve canonical Mumbai/Pune locality resolution versus extractor-only baseline.
Accept lead-location payload from Supervisor. Validate input against references/location-normalizer-input.schema.json. Use references/india-location-aliases-v1.json as the authoritative lookup map. Match in this order: exact alias match (case-insensitive) token-normalized alias match (trim punctuation, collapse spaces) conservative fuzzy match only when clearly unambiguous Return one normalized location record per input lead with: city locality_canonical micro_market matched_alias confidence unresolved_flag Validate output against references/location-normalizer-output.schema.json.
Never parse raw chat exports. Never extract non-location entities. Never write to Google Sheets, databases, or files. Never send messages or trigger external channels. Never auto-resolve low-confidence ambiguous aliases.
If multiple localities match equally, set unresolved_flag: true. If no confident match exists, preserve input in matched_alias and mark unresolved. Prefer false-negative over false-positive for city/locality assignment.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.