Summary
Recurring conversation pattern: users check network health, transaction status, and validator state via ad-hoc commands. A dedicated Omni skill could standardize and accelerate these operations.
Evidence
- Conversation
f877356c (2026-03-16): "Check last transaction status" — manually queried RPC endpoints, checked block production, investigated mempool
- Existing diagnostic scripts in
numbers-network/api/ (health, info, platform, metrics) and rpc/rpc_test.py are underutilized
Proposed Skill: network-health
A skill that provides:
- Quick health check: Query both mainnet and testnet health endpoints, report validator status
- Transaction lookup: Given a tx hash, fetch status and receipt from the appropriate network
- Block production check: Compare latest block timestamp to current time, flag if stale
- Disk usage check: SSH or gcloud to check disk usage on validator/archive nodes
- Mempool status: Check pending transaction count
Impact
Low-medium — reduces time-to-diagnosis during incidents and standardizes operational checks across conversations.
Generated by NREM Mode with Omni
Summary
Recurring conversation pattern: users check network health, transaction status, and validator state via ad-hoc commands. A dedicated Omni skill could standardize and accelerate these operations.
Evidence
f877356c(2026-03-16): "Check last transaction status" — manually queried RPC endpoints, checked block production, investigated mempoolnumbers-network/api/(health, info, platform, metrics) andrpc/rpc_test.pyare underutilizedProposed Skill:
network-healthA skill that provides:
Impact
Low-medium — reduces time-to-diagnosis during incidents and standardizes operational checks across conversations.
Generated by NREM Mode with Omni