Online Speed Test

Problem it addresses

When troubleshooting network issues, engineers first need to confirm basic client-to-server link behavior: public egress limits, ISP path problems, or slow application services. Browser-based speed tests depend on a UI environment, while scripts often add dependencies and setup. This skill consolidates common metrics into a directly runnable local workflow, making it easier to capture evidence in CI, ops scripts, or agent workflows.

How it works

It emits multiple diagnostic signals rather than a single “speed” number:

• Download speed: checks bandwidth availability from server to client.
• Upload speed: tests outbound path constraints.
• Ping latency: observes RTT and basic connectivity.
• Public IP and ISP: helps identify the egress IP owner.
• City lookup: adds geographic context for path analysis.
• ASCII charts: renders test progress as terminal-friendly text.

The entrypoint is python speedtest_skill.py. Multi-node support helps compare latency and bandwidth across nodes, and the plain-text output is suitable for saving or forwarding as part of incident logs.

Limits

It is best for quick baseline network checks, not strict SLA acceptance. Results can vary with local network, ISP QoS, node load, and DNS path. Pair it with ping, traceroute, and application access logs. For continuous monitoring, wire outputs into thresholds and baselines.