uncertainty-and-units
No security findings. Scanned 1 time, most recently 2026-10-21.
Second scanner: NVIDIA SkillSpector
Independent static run, no language model, over the same files as the Cisco scan above. How the two scanners compare across the whole corpus: Two scanners, one corpus.
What this skill does
Tracks physical units and propagates measurement uncertainty in scientific calculations using pint and uncertainties. Use for unit conversion and dimensional checking, GUM uncertainty budgets, Type A and Type B evaluation, coverage factors and expanded uncertainty, Monte Carlo propagation, significant-figure and plus-minus reporting, error propagation through curve fits, CODATA constants, auditing Python code for stripped units or broken uncertainty propagation, and order-of-magnitude plausibility checks using dimensionless groups (Reynolds, Peclet, Damkohler, Knudsen, Biot, Womersley),…
- Package
- 15 files, 229 KB
- SKILL.md
- 2740 words, 12+ sections
- Code
- Python (7)
- Allowed tools
ReadWriteEditBash- License
- MIT
- Compatibility
- Requires Python 3.12+. The numeric CLIs need pint, uncertainties, NumPy, and SciPy; the static auditor is standard-library only. All bundled tooling runs locally with no network access.
SKILL.md covers: Uncertainty and units · Scope · Current release and installation · Non-negotiable workflow · The failures this skill exists to prevent · A unit stripped at an unknown scale · Offset temperature arithmetic · Logarithmic units that add by multiplying · A correlation destroyed by a round trip · A covariance matrix silently rescaled · A linearization that was never checked · Bundled local CLIs
Findings
No findings. SAFE
What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 21 KB |
references/domain-conversions.md | doc | 9.9 KB |
references/gum-methodology.md | doc | 12 KB |
references/pint-recipes.md | doc | 8.9 KB |
references/plausibility-scales.md | doc | 12 KB |
references/reporting-rules.md | doc | 7.0 KB |
references/review.md | doc | 6.8 KB |
references/uncertainties-recipes.md | doc | 7.9 KB |
scripts/_common.py | script | 22 KB |
scripts/audit_units.py | script | 21 KB |
scripts/check_plausibility.py | script | 36 KB |
scripts/convert_units.py | script | 12 KB |
scripts/format_result.py | script | 12 KB |
scripts/propagate_uncertainty.py | script | 28 KB |
scripts/uncertainty_budget.py | script | 14 KB |
External hosts referenced
pint.readthedocs.io www.bipm.org docs.scipy.org uncertainties.readthedocs.io github.com iapws.org physics.nist.gov www.grc.nasa.gov arxiv.org cie.co.at goldbook.iupac.org ilac.org jcgm.bipm.org numpy.org nvlpubs.nist.gov pypi.org bionumbers.hms.harvard.edu book.bionumbers.org doi.org export.arxiv.org pint-pandas.readthedocs.io pint-xarray.readthedocs.io websites.umich.edu
Hostnames that appear in the skill's files. Referencing a host is not a finding; compare against the findings above and the skill's stated purpose.
Package contents recorded 2026-10-22 at commit 593377bb0487. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.
What we checked
- Static analyzer. Pattern rules over SKILL.md and bundled files: known-bad commands, exfiltration URLs, secrets, obfuscation.
- Bytecode analyzer.
- Pipeline analyzer.
- Correlation analyzer.
- Behavioral analyzer. Checks what the skill asks the agent to do against what its description claims it does.
- Trigger analyzer. Looks for instructions that fire on conditions the user did not ask for.
What we did not check
- Runtime behaviour. The skill was not executed; findings come from reading its files.
- Anything fetched at install or run time, including remote scripts, package dependencies, and URLs the skill tells the agent to open.
- Content the analyzers cannot read: images, binaries, and some non-English text.
- Known scanner bypass classes. See the methodology and limitations page.
Sources
- Repository: https://github.com/K-Dense-AI/scientific-agent-skills
- Raw scan result: skills-uncertainty-and-units-scan.json
- Badge for your README:
- Request a re-scan