MemPalace Task Handoff
MemPalace/mempalace
Creates, hands off, claims, executes and closes agent tasks through the MemPalace logstream, with approval of the exact task before it is recorded.
Reason over BGP topology as a whole -- speakers, peering sessions, the route table, VRF/VPN membership, and whether a BGP epoch is bound to a stored IGP graph.
Install Topolograph Bgp Analysis
$ npx skills add automateyournetwork/netclaw --skill topolograph-bgp-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install automateyournetwork/netclaw topolograph-bgp-analysis --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workspace/skills/topolograph-bgp-analysis .claude/skills/topolograph-bgp-analysis && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "topolograph-bgp-analysis" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/topolograph-bgp-analysis into .claude/skills/topolograph-bgp-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topolograph-bgp-analysis", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/topolograph-bgp-analysisType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add automateyournetwork/netclaw --skill topolograph-bgp-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install automateyournetwork/netclaw topolograph-bgp-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workspace/skills/topolograph-bgp-analysis .agents/skills/topolograph-bgp-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "topolograph-bgp-analysis" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/topolograph-bgp-analysis into .agents/skills/topolograph-bgp-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topolograph-bgp-analysis", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill topolograph-bgp-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install automateyournetwork/netclaw topolograph-bgp-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workspace/skills/topolograph-bgp-analysis .cursor/skills/topolograph-bgp-analysis && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "topolograph-bgp-analysis" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/topolograph-bgp-analysis into .cursor/skills/topolograph-bgp-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topolograph-bgp-analysis", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/automateyournetwork/netclaw.git --path workspace/skills/topolograph-bgp-analysis--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add automateyournetwork/netclaw --skill topolograph-bgp-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install automateyournetwork/netclaw topolograph-bgp-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workspace/skills/topolograph-bgp-analysis .gemini/skills/topolograph-bgp-analysis && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "topolograph-bgp-analysis" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/topolograph-bgp-analysis into .gemini/skills/topolograph-bgp-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topolograph-bgp-analysis", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install automateyournetwork/netclaw topolograph-bgp-analysisInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add automateyournetwork/netclaw --skill topolograph-bgp-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/workspace/skills/topolograph-bgp-analysis .github/skills/topolograph-bgp-analysis && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "topolograph-bgp-analysis" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/topolograph-bgp-analysis into .github/skills/topolograph-bgp-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topolograph-bgp-analysis", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add automateyournetwork/netclaw --skill topolograph-bgp-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install automateyournetwork/netclaw topolograph-bgp-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workspace/skills/topolograph-bgp-analysis .opencode/skills/topolograph-bgp-analysis && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "topolograph-bgp-analysis" agent skill from https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/topolograph-bgp-analysis into .opencode/skills/topolograph-bgp-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topolograph-bgp-analysis", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
topolograph-bgp-analysis- GitHub stars
- 676
- Token cost
- ~1.4k tokens
- SKILL.md length
- 537 words
- Files
- 1
- Skills in repo
- 120
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Reason over BGP topology as a whole -- speakers, peering sessions, the route table, VRF/VPN membership, and whether a BGP epoch is bound to a stored IGP graph.
- The question is about what the BGP control plane believes (learned routes
- SKILL.md covers Remote, read-only, Client-side allowlist, Tools and Boundary — when to use…, plus 1 more section
- Reaches topolograph.com; needs TOPOLOGRAPH_API_TOKEN
- BGP-to-IGP correlation) rather than what one live devices BGP table currently shows
What it does
Topolograph Bgp Analysis is an agent skill from automateyournetwork/netclaw. Reason over BGP topology as a whole -- speakers, peering sessions, the route table, VRF/VPN membership, and whether a BGP epoch is bound to a stored IGP graph. Use when the question is about what the BGP control plane believes (learned routes, session state, VRF placement, BGP-to-IGP correlation) rather than what one live device's BGP table currently shows. Read-only.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Session handoff. It works with Model Context Protocol. The repository describes itself as: An AI agent that claws through your network. The licence is Apache-2.0.
When your agent uses it
- The question is about what the BGP control plane believes (learned routes
- BGP-to-IGP correlation) rather than what one live devices BGP table currently shows
Example prompts
- “/topolograph-bgp-analysis”
Requirements
- A credential in TOPOLOGRAPH_API_TOKEN
What it can do on your machine
Read from SKILL.md and the folder at commit aa90e7d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
topolograph.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
TOPOLOGRAPH_API_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Topolograph Bgp Analysis loads about 1.4k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 537 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from automateyournetwork/netclaw at commit aa90e7d, republished under its Apache-2.0 licence (© automateyournetwork). 537 words, ~1,398 tokens.
Download SKILL.mdSave it as
.claude/skills/topolograph-bgp-analysis/SKILL.md (or your agent's skills folder).- name
- topolograph-bgp-analysis
- description
- Reason over BGP topology as a whole -- speakers, peering sessions, the route table, VRF/VPN membership, and whether a BGP epoch is bound to a stored IGP graph. Use when the question is about what the BGP control plane believes (learned routes, session state, VRF placement, BGP-to-IGP correlation) rather than what one live device's BGP table currently shows. Read-only.
- license
- Apache-2.0
- user-invocable
- true
Topolograph BGP Topology Analysis
pyats-routing, pyats-junos-routing and multivendor-device-query each
read one live device's BGP table. This one reasons over BGP topology
Topolograph has already collected via BMP — speakers, sessions, the route
table across every reporting peer, VRF/VPN placement, and whether that BGP
epoch actually corresponds to a stored IGP graph.
It answers "what does BGP believe the topology and route state are" — not "what is in this router's BGP table right now."
Remote, read-only
Same server as topolograph-igp-analysis (spec 119): topolograph-mcp is a
remote HTTP MCP registered in config/openclaw.json, no local server,
fronting your own Topolograph instance (TOPOLOGRAPH_MCP_URL, default
https://topolograph.com/mcp), bearer TOPOLOGRAPH_API_TOKEN. No
second credential — if the IGP skill already works, this one does too.
The server runs with TOPOLOGRAPH_MCP_READ_ONLY=true: mutation tools are
absent from tools/list. None of the 14 BGP tools mutate anything.
Requires Topolograph >= 2.69 and a topolograph-mcp-server build that
includes the BGP tool surface (upstream PR #1). Older instances will list
these tools but every call 404s or returns empty — check TOOLS.md for the
version note before assuming a live instance is broken.
Client-side allowlist
defenseclaw tool allow topolograph-mcp list_bgp_graphs
defenseclaw tool allow topolograph-mcp get_bgp_graph
defenseclaw tool allow topolograph-mcp list_bgp_nodes
defenseclaw tool allow topolograph-mcp list_bgp_sessions
defenseclaw tool allow topolograph-mcp search_bgp_routes
defenseclaw tool allow topolograph-mcp get_bgp_node_route_summary
defenseclaw tool allow topolograph-mcp get_bgp_route_state
defenseclaw tool allow topolograph-mcp compare_bgp_routes
defenseclaw tool allow topolograph-mcp get_bgp_events_timeline
defenseclaw tool allow topolograph-mcp list_bgp_bindings
defenseclaw tool allow topolograph-mcp get_bgp_binding
defenseclaw tool allow topolograph-mcp resolve_route
defenseclaw tool allow topolograph-mcp get_vrf_inventory
defenseclaw tool allow topolograph-mcp list_vpn_routersSame belt-and-braces note as the IGP skill: the server already hides mutation tools; this allowlist is the client-side floor in case a misconfigured instance widens the surface.
Tools
| Tool | Answers |
|---|---|
list_bgp_graphs / get_bgp_graph | Which BGP epochs (BMP collection cycles) exist; the full graph for one. Start here to get a bgp_graph_time. |
list_bgp_nodes | BGP speakers in an epoch — role, ASN, route-reflector/PE/core device role. |
list_bgp_sessions | Peering sessions — eBGP/iBGP, families, policy direction, relation to the IGP topology. |
search_bgp_routes | The route table, whole-graph or scoped to one speaker's resolved RIB view — prefix, community, AS-path, RT, and 15+ other filters. |
get_bgp_node_route_summary | One speaker's route totals: per-RIB-tag histogram, Adj-RIB-Out count. |
get_bgp_route_state | Point-in-time route state as of a timestamp. |
compare_bgp_routes | What changed (added/withdrawn/changed) between two instants, optionally scoped to one router, across a collector restart. |
get_bgp_events_timeline | BGP session/route monitoring events. |
list_bgp_bindings / get_bgp_binding | Whether a BGP epoch's speaker set is matched to a stored IGP graph, and how confidently (source_coverage, matched router IDs). |
resolve_route | Resolve a destination end to end, including a BGP/VPN/MPLS handoff — not just the IGP shortest path. |
get_vrf_inventory / list_vpn_routers | VRF names/RDs/route-targets per router; which routers are VPN-PE candidates for resolve_route. |
Show full SKILL.md (175 more words)Show less
Boundary — when to use something else
| Question | Skill |
|---|---|
| "What BGP speakers/sessions/routes does this topology have?" | this skill |
| "What is in this router's BGP table / VRF right now?" | pyats-routing, pyats-junos-routing, multivendor-device-query |
| "What does the IGP topology look like / what if this link fails?" | topolograph-igp-analysis |
| "Is this BGP epoch actually the same network as that IGP graph?" | this skill — list_bgp_bindings |
| "Push a policy / session change" | device-write path, gated — never here |
Never
- Never present
compare_bgp_routesorresolve_routeoutput as something observed on the wire this second — both describe a stored epoch. Report how old thebgp_graph_timeis. - Never treat a
boundbinding state as permanent —list_bgp_bindingsreflects one BGP epoch matched against one IGP graph; a later epoch can have a differentsource_coverage, orneeds_mappingstate. - Never report an empty result from any of these 14 tools as "no BGP data
exists" without first checking
TOOLS.md's version note — every one of them silently returned empty on Topolograph instances predating the auth fix in v2.69.1/v2.69.2 (spec 120 research R2), which looks identical to "no data" from the caller's side.
© automateyournetwork, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in workspace/skills/topolograph-bgp-analysis of automateyournetwork/netclaw.
Open the folder on GitHubat commit aa90e7d
Compare with similar skills
Topolograph Bgp Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Topolograph Bgp Analysis this skillautomateyournetwork/netclaw | 676 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| MemPalace Task HandoffMemPalace/mempalace | 59k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Memori MCP Memory UsageMemoriLabs/Memori | 17k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Ourmemourmem/omem | 174 | 1 repos | ~3.4k | Automated safety check: Pass | Custom licence | |
| Context RecoverySakuraByteCore/codexmate | 354 | — | ~964 | Automated safety check: Pass | Apache-2.0 | |
| Agent Manager Fleet TUIYoanWai/agent-manager | 580 | — | ~1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Memori MCP Memory Usage
MemoriLabs/Memori
Teaches an MCP-connected agent when and how to call Memori's recall, summary, compaction, augmentation, feedback and quota tools to keep context across sessions.
Ourmem
ourmem/omem
Shared memory that never forgets. An agent skill from ourmem/omem.
Context Recovery
SakuraByteCore/codexmate
Recovers project handoff context from local Codex, Claude Code, Gemini, CodeBuddy, and codexmate-derived sessions.
Agent Manager Fleet TUI
YoanWai/agent-manager
Runs several coding-agent CLIs as real tmux sessions in one terminal UI, color-coded by whether each is working, waiting, idle or blocked.
Claude Code Auto-Capture Hook
NateBJones-Projects/OB1
Fires a Stop hook that captures a Claude Code session transcript automatically when the session ends without a verbal wrap-up.
More from automateyournetwork/netclaw
All 120 skills in this repoEVE-NG Lab Topology Design
automateyournetwork/netclaw
Entry point for designing EVE-NG network labs: classifies the request, gathers missing requirements, proposes options and validates the resulting topology.
ACI Policy Change Deployment
automateyournetwork/netclaw
Deploys Cisco ACI policy changes only behind an approved ServiceNow Change Request, capturing pre and post-change fault baselines and rolling back automatically on a fault delta.
Cisco ACI Fabric Health Audit
automateyournetwork/netclaw
Runs a phased health audit of a Cisco ACI fabric through MCP tools: node status, links, tenant and policy review, faults and endpoint learning.
Anta Validation
automateyournetwork/netclaw
Validate Arista EOS network state against ANTA's pre-built 208-test catalogue, with structured pass/fail verdicts.
Arista Cvp
automateyournetwork/netclaw
Arista CloudVision Portal (CVP) automation via REST API — device inventory, events, connectivity monitoring, tag management (4 tools).
AWS Cloud Monitoring
automateyournetwork/netclaw
AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance.
Related
Works with
Categories
Questions about Topolograph Bgp Analysis
What does Topolograph Bgp Analysis do?
Reason over BGP topology as a whole -- speakers, peering sessions, the route table, VRF/VPN membership, and whether a BGP epoch is bound to a stored IGP graph. Topolograph Bgp Analysis is an agent skill from automateyournetwork/netclaw. Reason over BGP topology as a whole -- speakers, peering sessions, the route table, VRF/VPN membership, and whether a BGP epoch is bound to a stored IGP graph.
When should I use Topolograph Bgp Analysis?
Topolograph Bgp Analysis fits situations like: the question is about what the BGP control plane believes (learned routes; BGP-to-IGP correlation) rather than what one live devices BGP table currently shows.
How do I install Topolograph Bgp Analysis in Claude Code?
Run `npx skills add automateyournetwork/netclaw --skill topolograph-bgp-analysis -a claude-code`. Or copy the skill folder (workspace/skills/topolograph-bgp-analysis in automateyournetwork/netclaw) into .claude/skills/topolograph-bgp-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Topolograph Bgp Analysis in Codex?
Run `npx skills add automateyournetwork/netclaw --skill topolograph-bgp-analysis -a codex`. Or copy the skill folder (workspace/skills/topolograph-bgp-analysis in automateyournetwork/netclaw) into .agents/skills/topolograph-bgp-analysis in your project. Codex loads it when a task matches its description.
Can I use Topolograph Bgp Analysis in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add automateyournetwork/netclaw --skill topolograph-bgp-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/topolograph-bgp-analysis, .gemini/skills/topolograph-bgp-analysis, .github/skills/topolograph-bgp-analysis and .opencode/skills/topolograph-bgp-analysis in your project.
What does Topolograph Bgp Analysis need to run?
Going by SKILL.md and its folder, Topolograph Bgp Analysis needs credentials named TOPOLOGRAPH_API_TOKEN. Our summary lists: A credential in TOPOLOGRAPH_API_TOKEN.
Does Topolograph Bgp Analysis access the network?
SKILL.md names 1 domain. In commands or code: topolograph.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Topolograph Bgp Analysis safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Topolograph Bgp Analysis use?
Topolograph Bgp Analysis is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Topolograph Bgp Analysis use?
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Topolograph Bgp Analysis?
Skills that share tags, products or a category with Topolograph Bgp Analysis: MemPalace Task Handoff (MemPalace/mempalace, 59k stars), Memori MCP Memory Usage (MemoriLabs/Memori, 17k stars), Ourmem (ourmem/omem, 174 stars) and Context Recovery (SakuraByteCore/codexmate, 354 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Topolograph Bgp Analysis?
automateyournetwork (a GitHub user) maintains it in automateyournetwork/netclaw, which has 676 GitHub stars. The repository holds 120 skills in this directory. The repository was last updated on October 9, 2026.
Source: automateyournetwork/netclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.