n2n-federation

Federate NetClaw agents over a BGP mesh to exchange capability inventories and delegate tasks.

650|182|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill n2n-federation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n2n-federation
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/n2n-federation
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill n2n-federation

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about n2n-federation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I federate my NetClaw with another operator's claw?

Confirm the peer's AS and router-id out-of-band first, then call n2n_consent with those values. When the peer also consents, the NCFED channel opens and capability inventories exchange automatically; n2n_status shows the peer as federated.

How do I check what skills and tools a peer NetClaw has?

Call n2n_peer_capabilities with the peer identifier to see their skills, MCP servers, and badges with inventory freshness. Use n2n_compare_capabilities to see what they have that you do not, and vice versa.

Why does a long remote task time out over n2n_chat?

Chat and synchronous invoke are blocking calls, so multi-minute builds time out on the requester side while the peer keeps running. Use n2n_delegate instead, which returns a task_id immediately; poll with n2n_task_status and fetch the retained result with n2n_task_result.

Does federation expose my credentials or device addresses to peers?

No. Inventories contain only capability names and descriptions — never credentials, .env values, device addresses, or testbed secrets. You can also hide specific items with n2n_set_visibility set to hidden.

What is the difference between eN2N and iN2N federation?

eN2N federates with other operators' claws across the internet using mutual consent. iN2N is internal: one operator runs a risk of specialist Member Claws coordinated by a single Border Claw, with members dialing the Border outbound over pinned self-signed keys.

When should I use knowledge replication instead of a federated knowledge query?

Use n2n_knowledge_query for one-off questions where only the cited answer travels. Use n2n_replicate only when you want a standing local copy of a peer's collection in your own Chroma store, which requires a separate knowledge_replica grant and matching embedding models.