Agent skill

Topolograph Igp Analysis

by automateyournetwork in automateyournetwork/netclaw

Reason over the OSPF/IS-IS link-state topology as a whole — shortest and backup paths, per-area LSDB, edge and node failure simulation, MPLS-TE/CSPF feasibility, and a timeline of topology change…

Apache-2.0Auto-check passed

Install Topolograph Igp Analysis

skills CLI
$ npx skills add automateyournetwork/netclaw --skill topolograph-igp-analysis -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install automateyournetwork/netclaw topolograph-igp-analysis --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/automateyournetwork/netclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workspace/skills/topolograph-igp-analysis .claude/skills/topolograph-igp-analysis && rm -rf skills-src

Use ~/.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/

Facts

Skill name
topolograph-igp-analysis
GitHub stars
676
Token cost
~1.4k tokens
SKILL.md length
523 words
Files
1
Skills in repo
120
Repo updated
First seen
Licence
Apache-2.0

At a glance

Reason over the OSPF/IS-IS link-state topology as a whole — shortest and backup paths, per-area LSDB, edge and node failure simulation, MPLS-TE/CSPF feasibility, and a timeline of topology change…

  • The question is about what the IGP believes the topology is
  • SKILL.md covers Remote, read-only, Client-side allowlist, Tools and Boundary — when to use…, plus 2 more sections
  • Reaches topolograph.com; needs TOPOLOGRAPH_API_TOKEN
  • What it would do if a link

What it does

Topolograph Igp Analysis is an agent skill from automateyournetwork/netclaw. Reason over the OSPF/IS-IS link-state topology as a whole — shortest and backup paths, per-area LSDB, edge and node failure simulation, MPLS-TE/CSPF feasibility, and a timeline of topology change events. Use when the question is about what the IGP believes the topology is, or what it would do if a link or node failed, rather than what one live device's routing 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 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 IGP believes the topology is
  • What it would do if a link
  • Rather than what one live devices routing table currently shows

Example prompts

  • “/topolograph-igp-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 Igp Analysis loads about 1.4k tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 523 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~105
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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). 523 words, ~1,399 tokens.

Download SKILL.mdSave it as .claude/skills/topolograph-igp-analysis/SKILL.md (or your agent's skills folder).
name
topolograph-igp-analysis
description
Reason over the OSPF/IS-IS link-state topology as a whole — shortest and backup paths, per-area LSDB, edge and node failure simulation, MPLS-TE/CSPF feasibility, and a timeline of topology change events. Use when the question is about what the IGP believes the topology is, or what it would do if a link or node failed, rather than what one live device's routing table currently shows. Read-only.
license
Apache-2.0
user-invocable
true

Topolograph IGP Topology Analysis

Every device-facing routing skill NetClaw has — pyats-routing, pyats-junos-routing, multivendor-device-query — reads one live device's RIB and LSDB. This one reasons over the whole area's link-state database at once, from a graph Topolograph already built, and can simulate a change without touching anything.

It answers "what does the IGP think the topology is, and what would it do if X failed?" — not "what is on this router right now."

Remote, read-only

topolograph-mcp is a remote HTTP MCP registered in config/openclaw.json. There is no local server. It fronts your own Topolograph instance (TOPOLOGRAPH_MCP_URL, default https://topolograph.com/mcp), bearer TOPOLOGRAPH_API_TOKEN.

The server runs with TOPOLOGRAPH_MCP_READ_ONLY=true: mutation tools (upload_graph, add_lsp, update_lsp, delete_lsp) are absent from tools/list and cannot be called. Do not try to reach them — a topology change belongs in the device-write path, gated, not here.

Client-side allowlist

The tool filter is enforced with the DefenseClaw CLI, not a config block:

bash
defenseclaw tool allow topolograph-mcp get_all_graphs
defenseclaw tool allow topolograph-mcp get_graph_by_time
defenseclaw tool allow topolograph-mcp get_network_by_graph_time
defenseclaw tool allow topolograph-mcp get_graph_status
defenseclaw tool allow topolograph-mcp get_network_events
defenseclaw tool allow topolograph-mcp get_adjacency_events
defenseclaw tool allow topolograph-mcp get_events_timeline
defenseclaw tool allow topolograph-mcp get_nodes
defenseclaw tool allow topolograph-mcp get_edges
defenseclaw tool allow topolograph-mcp get_lsps
defenseclaw tool allow topolograph-mcp get_shortest_path
defenseclaw tool allow topolograph-mcp get_cspf_path
defenseclaw tool allow topolograph-mcp get_edge_failure_reaction
defenseclaw tool block topolograph-mcp upload_graph
defenseclaw tool block topolograph-mcp add_lsp
defenseclaw tool block topolograph-mcp update_lsp
defenseclaw tool block topolograph-mcp delete_lsp

The block lines are belt-and-braces: the server already hides those, but a misconfigured (TOPOLOGRAPH_MCP_READ_ONLY=false) instance must not widen NetClaw's surface.

Tools

ToolAnswers
get_all_graphsWhich stored topology snapshots exist (filter by protocol, area, date). Start here to get a graph_time.
get_graph_by_timeThe full graph for one snapshot.
get_graph_statusHealth of a snapshot — is it complete and consistent.
get_network_by_graph_timeWhich prefixes/networks are in the graph, by mask/area.
get_nodesRouters in the area, filterable by role flag (ABR/ASBR, IS-IS overload/attached).
get_edgesAdjacencies, with include=["lsps","is_te_link","lsp_left_bw","edge_key"] for MPLS-TE fields.
get_lspsMPLS-TE LSP tunnels, filter by status, via_node, via_edge.
get_shortest_pathSPF path between two nodes; with_lsps=true accounts for autoroute tunnels.
get_cspf_pathConstrained-SPF feasibility between two nodes — never mutates the graph.
get_edge_failure_reactionWhole-network impact if one or more links fail: stays connected? rerouting pattern? Simulation only.
get_network_events / get_adjacency_eventsRaw topology-change events in a time range.
get_events_timelineThe same events grouped into waves for incident narration.
Show full SKILL.md (225 more words)Show less

Boundary — when to use something else

QuestionSkill
"What does the IGP topology look like / what if this link fails?"this skill
"What is in this router's routing table / LSDB right now?"pyats-routing, pyats-junos-routing, multivendor-device-query
"Is this adjacency actually up on the device?"the platform routing skill
"Push a metric / cost change"device-write path, gated — never here

Topolograph reasons over a stored snapshot. If the question is "is this true on the wire this second", confirm on the device after.

Never

  • Never present a simulation result (get_edge_failure_reaction, get_cspf_path) as something that happened. It is a prediction over a snapshot.
  • Never report a stale graph_time as current — check get_all_graphs for the latest snapshot, and say how old it is.

Failure Behavior

  • If a tool call fails with an authentication or connection error, check that TOPOLOGRAPH_API_TOKEN is set and valid before assuming a data or device problem.
  • On a tool error (timeout, unreachable host, malformed response), report the failure and its error message directly to the user rather than fabricating or guessing at results.
  • For a confirmed read-only call, check connectivity and retry once if appropriate. For any call that changes state or sends a message, a timeout does not prove the action failed: inspect current state or delivery status before retrying, preserve the required approval/change gates, and do not repeat an action whose outcome is unknown.

© 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-igp-analysis of automateyournetwork/netclaw.

Open the folder on GitHubat commit aa90e7d

Compare with similar skills

Topolograph Igp 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.

Topolograph Igp Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Topolograph Igp Analysis this skillautomateyournetwork/netclaw676—~1.4kAutomated safety check: PassApache-2.0
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k4 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Figma use_figma Plugin API Ruleswarpdotdev/warp65k4 repos~4.4kAutomated safety check: PassAGPL-3.0
Stitch to Remotion Walkthrough Videosgoogle-labs-code/stitch-skills8.5k6 repos~3.2kAutomated safety check: NotesApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 4 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • Stitch to Remotion Walkthrough Videos

    google-labs-code/stitch-skills

    Official

    Builds walkthrough videos from Stitch design projects using Remotion, with transitions, zoom effects and text overlays on each screen.

    8.5k GitHub starsUsed in 6 repos~3.2k tokens
    Media & CreativeAuto-check: notes
  • MCP Development

    coollabsio/coolify

    A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 1 repo~949 tokens
    Frontend & DesignAuto-check passed

More from automateyournetwork/netclaw

All 120 skills in this repo
  • EVE-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.

    677 GitHub stars~612 tokensUpdated today
    Auto-check passed
  • 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.

    677 GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • 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.

    677 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Anta Validation

    automateyournetwork/netclaw

    Validate Arista EOS network state against ANTA's pre-built 208-test catalogue, with structured pass/fail verdicts.

    677 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Arista Cvp

    automateyournetwork/netclaw

    Arista CloudVision Portal (CVP) automation via REST API — device inventory, events, connectivity monitoring, tag management (4 tools).

    677 GitHub stars~2.2k tokensUpdated today
    Auto-check: notes
  • AWS Cloud Monitoring

    automateyournetwork/netclaw

    AWS CloudWatch monitoring — metrics, alarms, log queries, VPC flow log analysis, network performance.

    677 GitHub stars~1k tokensUpdated today
    Auto-check passed

Questions about Topolograph Igp Analysis

What does Topolograph Igp Analysis do?

Reason over the OSPF/IS-IS link-state topology as a whole — shortest and backup paths, per-area LSDB, edge and node failure simulation, MPLS-TE/CSPF feasibility, and a timeline of topology change…. Topolograph Igp Analysis is an agent skill from automateyournetwork/netclaw. Reason over the OSPF/IS-IS link-state topology as a whole — shortest and backup paths, per-area LSDB, edge and node failure simulation, MPLS-TE/CSPF feasibility, and a timeline of topology change events.

When should I use Topolograph Igp Analysis?

Topolograph Igp Analysis fits situations like: the question is about what the IGP believes the topology is; what it would do if a link; rather than what one live devices routing table currently shows.

How do I install Topolograph Igp Analysis in Claude Code?

Run `npx skills add automateyournetwork/netclaw --skill topolograph-igp-analysis -a claude-code`. Or copy the skill folder (workspace/skills/topolograph-igp-analysis in automateyournetwork/netclaw) into .claude/skills/topolograph-igp-analysis in your project. Claude Code loads it when a task matches its description.

How do I install Topolograph Igp Analysis in Codex?

Run `npx skills add automateyournetwork/netclaw --skill topolograph-igp-analysis -a codex`. Or copy the skill folder (workspace/skills/topolograph-igp-analysis in automateyournetwork/netclaw) into .agents/skills/topolograph-igp-analysis in your project. Codex loads it when a task matches its description.

Can I use Topolograph Igp 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-igp-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-igp-analysis, .gemini/skills/topolograph-igp-analysis, .github/skills/topolograph-igp-analysis and .opencode/skills/topolograph-igp-analysis in your project.

What does Topolograph Igp Analysis need to run?

Going by SKILL.md and its folder, Topolograph Igp Analysis needs credentials named TOPOLOGRAPH_API_TOKEN. Our summary lists: A credential in TOPOLOGRAPH_API_TOKEN.

Does Topolograph Igp 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 Igp 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 Igp Analysis use?

Topolograph Igp 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 Igp 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 Igp Analysis?

Skills that share tags, products or a category with Topolograph Igp Analysis: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Topolograph Igp 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.