con un clic
data-analysis
Use to investigate data for surprising, actionable insights
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Menú
Use to investigate data for surprising, actionable insights
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
ALWAYS follow this style when writing Python / JavaScript code
To select, design, annotate, and verify a data visualization (chart, map, or table).
ALWAYS follow this design guide for any front-end work
Use this for non-trivial analysis, design, diagnosis, review, strategy, or judgment. Skip it for simple lookups, mechanical rewrites, and pure tone tasks.
For CloudFlare development, deployment, e.g. Python CloudFlare Workers
Use when creating demos or POCs
| name | data-analysis |
| description | Use to investigate data for surprising, actionable insights |
Hunt for stories that make smart readers lean forward and say "wait, really?" - findings that are high-impact, surprising, actionable, and defensible.
This is a DETAILED process. Create a PLAN and execute step by step.
Apply diverse analysis toolkits ranging from statistical tests to geospatial, network, NLP, time series, cohort, segmentation, survival analysis, etc. to expand the insights pool.
Look for stories that confirm something suspected but never proven, or overturn something everyone assumes is true:
Search internally / externally:
Find leverage points:
Cross-check externally: Is there outside evidence (benchmarks, research, industry data) that supports, refines, or contradicts the finding?
Test robustness: Does the finding hold under cross model checks, alternative model specs, thresholds, sub-samples, or time windows? Does a placebo test (shuffled labels, random baseline) reproduce it? If so, it's noise.
Check for errors & bias: Examine data provenance, definitions, collection methodology. Control for confounders, base rates, uncertainty. What's missing? Selection and survivorship bias are silent killers.
Check for logical fallacies:
Consider limitations: What cannot be concluded? What caveats must accompany the finding to avoid misuse?
Select insights that are
Lead with the most compelling finding → evidence → caveats → what to do with it.
Tone: Write like a journalist, not a statistician. Say "Sales reps in the Northeast close 2x faster, but only for deals under $10K", not "Closure varies by region." Findings should make a smart reader lean forward.