Del archivo al resultado útil
Cómo pedir trabajo con esta skill instalada
Instalar la skill da un método a tu IA. Tu petición todavía debe aportar los hechos del caso, las restricciones y el entregable esperado.
1Nombra la tarea real
Describe la decisión o el entregable, no solo el tema.
2Aporta la información
Añade materiales, público, límites y hechos conocidos.
3Define qué significa acabado
Fija formato, criterios de calidad y comprobaciones.
Ejemplo de origen
Sustituye los corchetes por tu caso
Cuándo usarla
- Setting up dashboards for a new CRM deployment
- Your current dashboards are full of vanity metrics that nobody acts on
- Different teams (sales, marketing, success) need different views of the same data
- Management is making decisions from spreadsheets instead of the CRM
- Forecasting accuracy is poor and managers can't see the problem until it's too late
- Board meeting is in 2 weeks and you need a credible KPI dashboard
Errores que conviene evitar
- Including metrics from multiple systems on one dashboard without explaining data source — if CRM data and billing data differ, everyone will argue about which is correct
- Building a dashboard once and never refreshing it as the business changes — a dashboard built for Q1 may not reflect the metrics the CEO cares about in Q4
- Showing too many metrics — the human brain can meaningfully process 5-7 numbers on a screen; beyond that it's just noise
- Ignoring the "drill-down" capability — build dashboards where clicking on a metric opens the underlying records so managers can investigate without a second tool
- Mixing lagging indicators (closed revenue) with leading indicators (pipeline, activity) on the same dashboard — they belong on separate views because they require different management responses