Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →automateyournetwork/bgp-registry-intel
BGP and registry intelligence — RPKI origin validation (is this announcement authorised?), RDAP registry ownership and abuse contacts, PeeringDB interconnection data, RIPEstat routing status and prefix visibility, RIPE Atlas anchors.
Passed 14 of 19 test cases with the skill, and 6 of 19 without it.
and 13 more in the full report
11 fixed6 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our team updated our ROA in the regional registry 10 minutes ago, but querying routing intelligence still returns the old validation state due to local caching. Provide the specific parameter required when performing a lookup to bypass the 5-minute RPKI cache and fetch live validator data.
| Checked | Without skill | With skill |
|---|---|---|
| The response identifies setting the fresh parameter to true to bypass cached validation results. | Missed | Passed |
The instructions your model reads when the skill loads.
bgp-intel-mcp (NetClaw-authored, spec 081 / roadmap R9)$BGP_INTEL_MCP_CMDRPKI
not-foundis NOTinvalid.
Most of the internet has no ROA. Unsigned address space is the overwhelmingly common case, not an
anomaly. If you report not-found as a hijack, a misconfiguration, or a security finding, you will
generate false incidents at scale and the operator will stop trusting you.
| State | Means | Actionable? |
|---|---|---|
valid | A ROA authorises this origin AS | No — healthy |
invalid + reason: as | A ROA covers this prefix; a different AS is authorised | Yes — possible hijack |
invalid + reason: length | Correct AS, but the prefix is more specific than the ROA permits | Yes — usually a local misconfiguration, different fix |
not_found | No ROA exists. RFC 6811 calls this NotFound | No — the normal case |
The two invalid reasons are different findings. as means someone else is announcing your space;
length usually means you announced a /24 under a /22 ROA. Never collapse them.
validation_unavailable is not not_found. If the validator is unreachable you get the former, and
the RPKI state is genuinely unknown. Do not infer "unsigned" from "could not ask", and do not fall back to
guessing from routing or registry data.
| Tool | Answers |
|---|---|
rpki_validate | Is this prefix legitimately announced by this AS? Nothing else in NetClaw does this |
registry_lookup | Who is this IP/prefix/ASN allocated to? |
registry_abuse_contact | Who do I report abuse to? |
routing_as_overview | Who holds this ASN; is it announced at all? |
test cases passed, vs 6 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.