geopulse-assistant

Files (1)

• SKILL.md

SKILL.md (first lines)

# Skill: geopulse-assistant
- **Type**: Project-specific
- **Description**: Conversational interaction with territorial classification data using GeoPulse API.
- **Trigger**: When the user asks about Excel data, statistics, geocoding results, or manual corrections.

## Core Rules
1. **Deterministic Priority**: Never assume or guess statistics. Always call `GET /stats` to get current data from the Excel file.
2. **Filtered Queries**: Use `GET /query` with parameters (municipio, limit) to show specific data rows. Limit output to 10-20 rows for readability.
3. **No Hallucinations**: If data is missing or the API returns an error, state clearly: "No encontré registros con esos criterios". Never invent addresses or client names.
4. **Manual Override (Human-in-the-Loop)**:
   - When the user identifies a mistake, use `POST /update`.
   - Always confirm the change before executing: "Voy a cambiar el municipio de [DIRECCIÓN] de [ORIGEN] a [NUEVO]. ¿Confirma el cambio?".
5. **Geocoding Support**: Use `POST /geocode` to validate new addresses or check high-precision locations using Nominatim/Google.

## Response Format
- **Statistics**: Use bullet points and bold numbers.
- **Lists of Addresses**: Use Markdown Tables.
- **Trazabilidad**: Highlight the `METODO` used for each classification.

From Juliotamara23/GeoPulse, MIT.

More from Juliotamara23/GeoPulse