peajes-auditoria-tarifas-expert

Diagnoses toll tariff normalization algorithms and CSV upload pipelines on Supabase.

Updated Jan 31, 2023
One-click install
npx skills add https://github.com/Briian3306/Transporte --skill peajes-auditoria-tarifas-expert-briian3306
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: peajes-auditoria-tarifas-expert
Source: https://github.com/Briian3306/Transporte/tree/main/ibarra-app/.agents/skills/peajes-auditoria-tarifas-expert
Command: npx skills add https://github.com/Briian3306/Transporte --skill peajes-auditoria-tarifas-expert-briian3306

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Auditing toll tariffs requires understanding a two-layer diagnosis system (algorithmic diagnostico vs human status), Patrón A/B detection, and a CSV/Excel upload wizard, all split between a read-only remote DESARROLLO database and a local Supabase CLI environment. This Skill guides inspection, diagnosis, and safe implementation of tariff normalization changes without risking unauthorized writes to production data. ## Core Features & Use Cases - Algorithm advisory: Explains and troubleshoots the peajes_normalizar_tarifas and peajes_recalcular_tarifas RPCs, the full diagnosis tree (MUESTRA_INSUFICIENTE, TARIFA_UNICA, CATEGORIA, POSIBLE_HORARIO, REVISAR), and invariants like RN-05 and RN-15. - CSV/Excel upload guidance: Covers the wizard pipeline, text-based CSV parsing (avoiding SheetJS numeric coercion of Argentine formats like 19.985,09), delimiter detection, and Strategy/Builder transformation codes such as CONVERTIR_NUMERO_ARS. - Environment safety: Enforces read-only MCP inspection of DESARROLLO and restricts all SQL edits to local Supabase CLI migrations with pgTAP tests. - Use Case: A user asks why a toll station's tariffs are stuck in REVISAR status; the Skill inspects tarifas_normalizadas via read-only MCP queries, checks dispersion thresholds, and recommends a migration fix tested locally. ## Quick Start Ask the assistant to inspect why a specific toll station's tariffs show a given diagnostico in DESARROLLO and recommend whether to keep, fix, or implement a change.

Frequently Asked Questions about peajes-auditoria-tarifas-expert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose why a toll tariff is marked REVISAR or MUESTRA_INSUFICIENTE?▼

Query tarifas_normalizadas via read-only MCP on DESARROLLO, grouping by diagnostico, status, and patron. Compare case counts against the sample threshold (default 15) and dispersion threshold (default 4.100) from tarifas_parametros_peaje to see which branch of the diagnosis tree applied.

What is the difference between peajes_normalizar_tarifas and peajes_recalcular_tarifas?▼

peajes_normalizar_tarifas runs after load confirmation and only assigns MUESTRA_INSUFICIENTE or REVISAR to new groups. peajes_recalcular_tarifas runs the full diagnosis tree over all price-positive pasadas of a peaje and also deletes orphan levels.

Why does my CSV upload break Argentine number formats like 19.985,09?▼

SheetJS coerces numeric strings and corrupts Argentine decimal formats. The parser keeps CSV cells as text, strips the BOM, detects the delimiter, and lets CONVERTIR_NUMERO_ARS handle the conversion during the transform step.

Can I run SQL migrations directly against the DESARROLLO database?▼

No. DESARROLLO is inspected read-only through MCP SELECT queries. All SQL changes go through local Supabase CLI migrations with pgTAP tests, and remote writes require explicit user authorization.

What is the difference between Patrón A and Patrón B in tariff auditing?▼

Patrón A means pasadas.categoria is NULL, so the family is just the station. Patrón B means the provider supplied a CATEGORIA text mapped in wizard Paso 5, so the family is station plus category. Detection happens at mapping, not from file headers.