automateyournetwork/gtrace-path-analysis
workspace/skills/gtrace-path-analysis/SKILL.md
Network path tracing and monitoring — traceroute with MPLS/ECMP/NAT detection, continuous MTR monitoring, and distributed GlobalPing probes from 500+ worldwide locations. Use when tracing the path to a destination, diagnosing slow network routes, detecting MPLS or ECMP load balancing, running MTR for intermittent packet loss, or testing reachability from global vantage points.
$ install --global
skillsauthnpx skillsauth add automateyournetwork/netclaw gtrace-path-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 10:33 PM1.5s1 file scanned
SKILL.md
- name:
- gtrace-path-analysis
- description:
- Network path tracing and monitoring — traceroute with MPLS/ECMP/NAT detection, continuous MTR monitoring, and distributed GlobalPing probes from 500+ worldwide locations. Use when tracing the path to a destination, diagnosing slow network routes, detecting MPLS or ECMP load balancing, running MTR for intermittent packet loss, or testing reachability from global vantage points.
- license:
- Apache-2.0
- user-invocable:
- true
- { "openclaw":
- { "requires": { "bins": ["python3", "gtrace"], "env": ["GTRACE_MCP_BIN"] } } }
Network Path Analysis with gtrace
How to Call the gtrace MCP Tools
python3 $MCP_CALL "gtrace mcp" TOOL_NAME '{"param":"value"}'
When to Use
- Trace the path between two endpoints and identify each hop (router, latency, loss)
- Detect MPLS labels, ECMP load balancing, and NAT translation points along the path
- Monitor a path continuously with MTR to identify intermittent packet loss or latency spikes
- Run distributed traceroutes from 500+ GlobalPing probe locations worldwide to compare paths from different vantage points
- Verify transit providers, peering, and routing policy by inspecting AS-level path data
- Troubleshoot asymmetric routing, suboptimal paths, or blackholes
Available Tools
| Tool | Purpose | Requirements |
|------|---------|-------------|
| traceroute | Advanced traceroute with MPLS, ECMP, and NAT detection | cap_net_raw |
| mtr | Continuous MTR monitoring with packet loss and jitter stats | cap_net_raw |
| globalping | Distributed traceroute/ping from 500+ worldwide probe locations | Internet access (optional GLOBALPING_API_KEY) |
Workflow: Path Troubleshooting
When asked "why is traffic slow to X?" or "trace the path to X":
Step 1: Traceroute
Run an advanced traceroute to see every hop, latency, and any MPLS/ECMP/NAT indicators.
python3 $MCP_CALL "gtrace mcp" traceroute '{"target":"8.8.8.8"}'
For IPv6:
python3 $MCP_CALL "gtrace mcp" traceroute '{"target":"2001:4860:4860::8888"}'
Step 2: Continuous Monitoring with MTR
If the traceroute shows packet loss or high latency at a specific hop, run MTR to monitor continuously and confirm the problem is persistent.
python3 $MCP_CALL "gtrace mcp" mtr '{"target":"8.8.8.8","count":100}'
Step 3: Global Perspective
Compare paths from multiple worldwide locations to determine if the issue is local or global.
python3 $MCP_CALL "gtrace mcp" globalping '{"target":"8.8.8.8","from":"US,EU,Asia"}'
Workflow: MPLS Path Verification
Verify MPLS label-switched paths and label stacks along the path:
python3 $MCP_CALL "gtrace mcp" traceroute '{"target":"10.0.0.1"}'
Look for MPLS label information in the hop details. Useful for verifying traffic engineering and MPLS VPN paths.
Workflow: ECMP Load Balancing Verification
Detect if traffic is being load-balanced across multiple equal-cost paths:
python3 $MCP_CALL "gtrace mcp" traceroute '{"target":"192.168.1.1"}'
ECMP detection reveals when multiple next-hops exist at a given TTL, indicating load balancing.
Tool Parameters
traceroute
target(required): IP address or hostname to trace
mtr
target(required): IP address or hostname to monitorcount(optional): Number of probe rounds to send
globalping
target(required): IP address or hostname to probefrom(optional): Comma-separated list of probe locations (countries, cities, regions, ASNs)
Output Format
All tools return structured results including:
- traceroute — hop number, IP, hostname, RTT per probe, MPLS labels, ECMP paths, NAT detection
- mtr — hop number, loss%, sent/recv counts, best/avg/worst/stdev RTT
- globalping — per-probe-location results with path data, useful for global path comparison
Important Rules
- Traceroute and MTR require
cap_net_rawcapability on the gtrace binary (set during install) - GlobalPing uses the public GlobalPing API — set
GLOBALPING_API_KEYfor higher rate limits - Always start with a single traceroute before running continuous MTR
- Use GlobalPing to differentiate local vs global path issues
- Cross-reference hop IPs with
asn_lookupandgeo_lookupfrom gtrace-ip-enrichment skill for full context - Record all path analysis in GAIT
Related Skills
automateyournetwork/humanrail-escalation
testing
VerifiedTrustedCommunity
Human-in-the-loop escalation via HumanRail — route low-confidence agent decisions, pre-destructive operation approvals, and ambiguous incident tickets to real human engineers. Human answers are verified and returned as structured output. Workers are paid via Lightning Network. Use when the agent is uncertain, when a destructive change needs explicit human sign-off beyond a ServiceNow CR, or when an ambiguous ticket requires human triage before automated handling.
491SKILL.mdUpdated May 12, 2026
automateyournetwork/eve-ng-node-operations
testing
VerifiedTrustedCommunity
Manage EVE-NG node lifecycle. Use when listing nodes, checking runtime state, creating or deleting nodes, starting or stopping nodes or whole labs, verifying node details, or wiping node NVRAM back to factory defaults.
491SKILL.mdUpdated May 12, 2026
automateyournetwork/eve-ng-lab-management
development
VerifiedTrustedCommunity
Manage EVE-NG labs and platform inventory. Use when listing labs, checking lab metadata, creating or deleting labs, importing or exporting lab archives, checking EVE-NG health or auth, or verifying available node images before build work.
491SKILL.mdUpdated May 12, 2026
automateyournetwork/eve-ng-console-ops
tools
VerifiedTrustedCommunity
Execute live CLI commands on running EVE-NG nodes over telnet console. Use when running show commands, making live config changes, verifying protocol state, testing connectivity, checking console readiness, or interacting with IOS, Junos, VPCS, EOS, or NX-OS nodes.
491SKILL.mdUpdated May 12, 2026