Loading the registry…
Drive a benchtop oscilloscope via VISA / USBTMC for hardware bring-up and waveform verification. Supports two scopes auto-detected at connect time — Keysight / Agilent InfiniiVision DSO5000-series (tested DSO5012A) and RIGOL DS1000Z-series (tested DS1102Z-E). Use this skill ANY time the user mentions the scope, oscilloscope, 示波器, DSO5012A, DS1102Z-E, DS1000Z, capturing waveforms, taking screenshots from the scope, CSV waveform data, SCPI commands, trigger setup, or pre/post-bridge measurements. Also use when the user reports problems like "trace is missing", "trigger isn't firing", "波形抓不到", or wants to verify firmware output on hardware. Self-contained — bundles the helper script and a venv bootstrap so it works without `~/Work/scope/` being set up. Knows the project-specific quirks (×100 probe lock on Keysight, BMP-not-PNG on Keysight, channel-display footgun, AUTO-SCALE override, RIGOL USBTMC pipe-stall recovery, RIGOL binary-block settle delay).
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'humoran/tt-skills (oscilloscope)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'humoran/tt-skills (oscilloscope)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
8 findings · 6.8s
v0.3.74
1 finding · 1.2s
v0.1.0
0 findings · 3.6s
v0.1.0
1 finding · 3.6s
v2.3.8
0 findings · 1.2s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 0.9s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 17, 2026 | Caution95 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Caution badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 10 findings above stand exactly as their scanners reported them, at full severity.