Diagnose BGP session and route-propagation problems such as flapping sessions and missing routes.
Diagnoses BGP session and route-propagation problems on whichever routing platform the caller is targeting, by reading session/route state and mapping it to that platform's own documented likely causes — not a configuration-change skill.
This skill is diagnostic-shaped: the "procedure" is a decision tree (check session state → if Established, check whether routes are received → if
received, check whether they're best-path selected → …), and the useful output is a diagnosis plus
supporting evidence, not a single created or deleted record. Each references/<platform>/procedure.md is a decision tree, and a diagnostic step is complete when the operator or caller knows which documented cause applies, not when platform state changes.
This skill only reads session and route state, so it has no destructive-action confirmation gates. It does not clear sessions or reset peers; a remediation action of that kind would need its own confirmation gate like any other destructive step.
The BGP session state machine's six named states — Idle, Connect, Active, OpenSent, OpenConfirm,
Established — come from RFC 4271, and each vendor's own CLI reports them verbatim: Juniper Junos's show bgp neighbor output uses these exact six words for its State/Last state fields (confirmed in Juniper's command-reference documentation), and Cisco IOS-XE and FRRouting are consistent with this vocabulary, though the documentation used here gives less field-by-field confirmation than Juniper's — see each vendor's own procedure.md for exactly what is and isn't verified. Only Established has a consistent, universally-observed second meaning
across all three vendors: once a session reaches Established, the same output field that showed the
state name is commonly repurposed to show a route/prefix count instead (confirmed for both Cisco
IOS-XE's summary-table state/PfxRcd column and Juniper's show bgp summary State field) — a numeric
value in that field position is itself evidence the session is up, not evidence of anything about the
state machine itself.
Not universal — do not assume across vendors:
procedure.md rather than assuming one vendor's order generalizes.references/juniper-junos/procedure.md's explicit-unknowns section); it is not safe to assume it matches either Cisco's or FRR's documented order just because the underlying concepts
are similar.See references/INDEX.md for which platforms have a procedure, and each platform file for how it
implements this shape concretely, including exactly which of the above each vendor's documentation does and doesn't confirm.
platform argument. Check
references/INDEX.md; if no matching row exists, stop: this skill doesn't cover it yet.references/<platform>/procedure.md to start from; the platform file is organized by symptom, not
by a linear operation sequence.references/<platform>/procedure.md and follow its decision tree for that symptom exactly
— it maps each observed state to that platform's own documented likely causes and the next check to
run.references/INDEX.md. A platform not listed there needs a new
reference file before this skill can be used for it.SKILL.md only changes for two reasons: a bug in the universal concepts/router logic above, or
adding a pointer to a newly-supported platform. Platform-specific decision-tree content — a new
documented cause, a corrected CLI/API output pattern, a vendor-specific state name — belongs in that
platform's own references/<platform>/procedure.md, never here.
Each platform assumes its own authenticated CLI/API session — see references/INDEX.md for which,
and that platform's procedure.md for the specific read-only checks it uses.
references/INDEX.md before proceedingprocedure.md decision tree was followed for the identified symptom