report-uncertainty-ranges
Use when stating any estimate or measurement. Attaches an interval and the source of the uncertainty instead of a single false-precision number.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 80
- Forks
- 17
01 前言 Front Matter
- name
- report-uncertainty-ranges
- description
- Use when stating any estimate or measurement. Attaches an interval and the source of the uncertainty instead of a single false-precision number.
02 资源文件 3
- 许可证LICENSE1.0 KB
- 参考文档SOURCE.md351 B
- 参考文档TRUST.auto.yaml2.1 KB
03 SKILL.md 正文
Report Uncertainty Ranges
A point estimate without an interval tells the reader the number is exact when it is not. Quantify the range or say plainly that you cannot.
Procedure
- Name the uncertainty type: sampling (finite n), measurement (instrument/annotation error), model (assumption), or scenario (future path). They compose differently.
- For sampling uncertainty, give 95% intervals. Bootstrap is the fallback for any statistic without a closed form:
import numpy as np rng = np.random.default_rng(0) boots = [np.median(rng.choice(x, x.size, replace=True)) for _ in range(10000)] lo, hi = np.percentile(boots, [2.5, 97.5]) - For a proportion, use a Wilson interval, not the textbook normal one, when p is near 0 or 1 or n is small.
- Propagate measurement error rather than ignoring it: for a product
f = a·b,σ_f/|f| = sqrt((σ_a/a)² + (σ_b/b)²). - Report intervals that describe the quantity you mean. A 95% CI is not "95% likely to contain the true value" under every interpretation — say which.
- Do not shrink an interval to look decisive; do not widen it to cover a claim it cannot support. If the interval spans the decision threshold, say the data is inconclusive.
- Round the interval to the precision of the estimate:
12.4% (95% CI 9.1–15.7), not12.4312 ± 0.4937.
python3 -c "from statsmodels.stats.proportion import proportion_confint; \
print(proportion_confint(37, 210, method='wilson'))"
Pitfalls
- A CI on a biased estimator is precisely wrong; uncertainty about bias is separate and usually larger.
- The interval says nothing about systematic error you did not model — name it.
- Error bars that are ±1 SEM look 3.9× narrower than a 95% interval and mislead by convention.
- Combining intervals by adding half-widths is wrong for independent errors; combine variances.
- Too many significant figures implies precision the interval contradicts.
Verification
grep -cE '95%|CI|interval|±|\[[0-9.]+, ?[0-9.]+\]' estimates.md
Every headline number carries an interval or an explicit "no interval available: reason". Report: "Estimate 12.4% (95% CI 9.1–15.7, Wilson, n=210); model bias not quantified."
04 同仓库更多 Skills
recipe-performance
Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold/warm/background-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout/paint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.
mexc-spot-websocket
MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.
mexc-spot-rest
MEXC Spot REST workflows for public data, signed account requests, orders, wallet/admin actions, and secure signing without exposing API keys.
mexc-futures-websocket
MEXC Futures WebSocket workflows for public streams, private account/order/position streams, ping/pong, subscriptions, and depth maintenance.
0xklen-version-and-refresh-sanctions-lists
暂无简介
verify-tests-cover-changed-lines
Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.