workspace/skills/telemetry-ops/SKILL.md
Comprehensive network telemetry and event collection across multiple protocols.
npx skillsauth add automateyournetwork/netclaw telemetry-opsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Comprehensive network telemetry and event collection across multiple protocols.
telemetry-ops
This meta-skill provides a unified interface to all NetClaw telemetry receivers: syslog, SNMP traps, IPFIX/NetFlow, and gNMI streaming telemetry. It enables holistic network monitoring by aggregating events from multiple sources.
| Skill | MCP Server | Protocol | Default Port |
|-------|------------|----------|--------------|
| syslog-receiver | syslog-mcp | RFC 5424/3164 UDP | 514 |
| snmptrap-receiver | snmptrap-mcp | SNMPv1/v2c/v3 UDP | 162 |
| ipfix-receiver | ipfix-mcp | IPFIX/NetFlow UDP | 2055 |
| gnmi-telemetry | gnmi-mcp | gNMI gRPC | 57400 |
1. Configure device to send syslog to NetClaw (UDP 514)
2. Configure SNMP traps to NetClaw (UDP 162)
3. Configure NetFlow/IPFIX export to NetClaw (UDP 2055)
4. Add device to gNMI targets for streaming telemetry
5. Start all receivers
6. Verify data is being received from each source
1. Query syslog for error messages around incident time
2. Check SNMP traps for linkDown events
3. Analyze flows for traffic anomalies
4. Subscribe to gNMI telemetry for real-time interface state
1. Use syslog_get_severity_counts for error distribution
2. Use snmptrap_get_counts for trap type breakdown
3. Use ipfix_top_talkers for bandwidth consumers
4. Use gnmi_get for current device state
logging host 10.0.0.1 transport udp port 514
logging trap informational
logging source-interface Loopback0
snmp-server enable traps
snmp-server host 10.0.0.1 version 2c public
flow exporter NETCLAW
destination 10.0.0.1
transport udp 2055
export-protocol ipfix
netconf-yang
gnmi-yang
gnmi-yang secure-server
Since ngrok doesn't support UDP, use these alternatives:
| Service | UDP Support | Best For | |---------|-------------|----------| | Pinggy | Yes | Quick tunnel setup | | Tailscale | Yes | Persistent mesh VPN | | LocalXpose | Yes | Full protocol support |
┌─────────────────┐
│ Cisco Cat 9300 │
└────────┬────────┘
│
┌────────────────────┼────────────────────┐
│ │ │ │ │
▼ ▼ ▼ ▼ │
┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐
│ Syslog │ │ SNMP │ │ IPFIX │ │ gNMI │
│ UDP 514 │ │ UDP 162 │ │UDP 2055 │ │TCP 57400│
└────┬────┘ └────┬────┘ └────┬────┘ └────┬────┘
│ │ │ │
▼ ▼ ▼ ▼
┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐
│syslog- │ │snmptrap-│ │ ipfix- │ │ gnmi- │
│ mcp │ │ mcp │ │ mcp │ │ mcp │
└────┬────┘ └────┬────┘ └────┬────┘ └────┬────┘
│ │ │ │
└───────────┴─────┬─────┴───────────┘
│
┌─────┴─────┐
│ NetClaw │
│ Agent │
└───────────┘
/mcp-servers/syslog-mcp/README.md/mcp-servers/snmptrap-mcp/README.md/mcp-servers/ipfix-mcp/README.md/mcp-servers/gnmi-mcp/README.mdtesting
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.
testing
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.
development
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.
tools
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.