net-path-probe

Benchmark latency, jitter, and loss across internal network targets.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/ekkus93/vscode_skills --skill net-path-probe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: net-path-probe
Source: https://github.com/ekkus93/vscode_skills/tree/main/skills/net-path-probe
Command: npx skills add https://github.com/ekkus93/vscode_skills --skill net-path-probe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires nettools-core.

What problem does it solve?

Measure internal path performance between targets to identify LAN/service degradation by benchmarking latency, jitter, and packet loss using the bundled NETTOOLS helper.

Core Features & Use Cases

  • Deterministic internal path probes with latency, jitter, and loss measurements across multiple targets.
  • Comparative analysis to identify degraded links and isolate network issues at site, service, or LAN scope.
  • Use case: compare performance between a pair of internal services to determine where degradation originates.

Quick Start

Run deterministic internal path probes against targets to quickly compare performance and identify degraded links.

Frequently Asked Questions about net-path-probe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I measure network latency, jitter, and packet loss between internal services?

To measure network latency, jitter, and packet loss, you can benchmark internal path quality between targets to identify degraded links and isolate LAN or service-wide network issues. The probe performs deterministic measurements across multiple internal targets.

What is the best way to compare network performance between wired and wireless LAN segments?

Comparing network performance across wired and wireless LAN segments requires running path probes against targets in each scope. This benchmarks latency, jitter, and loss to isolate exactly where degradation originates within the site.

Do I need Python 3 and the nettools-core dependency to run internal path probes?

Yes, running internal path probes requires a Python 3 environment and the bundled nettools-core dependency. You also need an adapter configured for either live or fixture-based probing to execute the measurements.

Can I use fixture-based probing instead of live network targets for path diagnostics?

Yes, you can use fixture-based probing instead of live network targets for path diagnostics. The probe supports an adapter that allows deterministic testing against fixtures, enabling safe internal path quality analysis without impacting live environments.

How do I isolate where service degradation originates when comparing internal network paths?

To isolate where service degradation originates, run comparative path probes between the internal service targets. Benchmarking latency, jitter, and loss across these paths highlights the specific degraded link causing the network performance drop.