Closing the design feedback loop requires understanding why designs fail, not just that they fail. This skill compares the distribution of every continuous feature between PASS and FAIL designs using non-parametric statistics, ranks features by discriminating power, and translates the result into…
How to install by-failure-diagnosis?
001tmf/blatant-why/by-failure-diagnosis
$npx -y skills add 001tmf/blatant-why --skill by-failure-diagnosisInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/001tmf/blatant-why" --skill "001tmf/blatant-why/by-failure-diagnosis"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/001tmf/blatant-why" that are relevant to the current task. Run `npx skills add "https://github.com/001tmf/blatant-why"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage.Jul 2026
- appinsights-instrumentationGuidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references.Jul 2026
- diagnosing-bugsDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.Jul 2026
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesJul 2026
- safe-debugRigor Debug / Rigor Audit skill for deep learning research work.Jul 2026
- golang-error-handlingIdiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single…Jul 2026
