What problem does it solve?
Network operators running separate NetClaw instances have no safe way to discover what a peer's agent can do or to offload work to it without sharing credentials. This Skill establishes mutual-consent federation over the BGP mesh so claws exchange signed, secret-free capability inventories and route tasks between each other.
Core Features & Use Cases
- Capability federation: Consent with a peer, browse their skills and MCP servers via
n2n_peer_capabilities, and compare inventories with n2n_compare_capabilities — credentials and device addresses are never exchanged.
- Async task delegation: Submit long-running work (CML lab rebuilds, config pushes) with
n2n_delegate and poll results via n2n_task_status/n2n_task_result, surviving channel drops and daemon restarts.
- Federated knowledge and iN2N risks: Route document questions to the peer whose RAG collection is authoritative, replicate corpora locally, and coordinate a Border Claw with specialist Member Claws.
- Use Case: Ask your own NetClaw "does Nicholas's claw have pyATS?" and get an answer from the locally cached inventory, then delegate a testbed build to that peer and retrieve the result when it completes.
Quick Start
Ask your NetClaw to federate with a peer by confirming their AS and router-id out-of-band, then run n2n_consent and query n2n_peer_capabilities to see what their claw can do.