Use when a European Economic Review (EER) result must be shown to survive specification, sample, measurement, and inference changes — the…
Use when an International Economic Review (IER) result may be sensitive to specification, sample, functional form, calibration, or…
Use when a Journal of Environmental Economics and Management (JEEM) manuscript's headline estimate — a damage, WTP, pass-through, or…
Use when results for a Journal of Economic Geography (JEG) manuscript may be sensitive to spatial scale, the weight matrix, spatial…
Use when a Journal of Health Economics (JHE) result must be shown stable to specification, sample, inference, and mechanism threats before…
Use when organizing robustness and sensitivity checks for a Journal of Law, Economics, and Organization (JLEO) manuscript — structuring…
Use when a Journal of Money, Credit and Banking (JMCB) result may be specification-, sample-, or inference-sensitive and you need to plan…
Use when results for a The World Bank Economic Review (WBER) manuscript may be sensitive to specification, sample, measurement, or…
Use when an IMF Economic Review (IMFER) manuscript's headline cross-country estimate must be shown to survive specification, sample…
Use when a The Journal of Law and Economics (JLE) manuscript's headline estimate must be shown to survive specification, sample…
Use when the headline estimate of a The Review of Economics and Statistics (REStat) manuscript needs to survive specification, sample…
Use when results may be sensitive — to specification, sample, measurement, or inference for quantitative work, or to interpretation and…
Monitoring and observability with OpenTelemetry, Prometheus, Grafana dashboards, and structured logging
Coverage summary — per-scope, per-system, or per-migration-state breakdown of article + capability + functionality counts.
Root-cause a production error from Google Cloud Logging by correlating it into a single request's log trail and locating the offending code.
5 Whys, Fishbone diagrams, Fault Tree Analysis, and systematic debugging approaches.
Systematic root cause analysis skill with multiple investigation methodologies.
Root cause analysis for bugs, failures, regressions, incidents, broken flows, failing tests/builds/CI, production errors, or odd behavior.
Use when designing or auditing the experimental campaign for an RSS (Robotics: Science and Systems) paper — hypothesis-shaped robot…
Read The Fucking Prompt — finds the strongest user reaction to an AI instruction-following failure in a chosen session, reconstructs what…
When to activate: Ruby performance, rack-mini-profiler, stackprof, fragment caching, Marshal serialization, GC tuning, memoization, Rails…