automateyournetwork/netclaw/aws-architecture-diagram

Claude Code and agent skill by automateyournetwork/netclaw

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

AWS architecture diagrams — generate visual network topology diagrams from live AWS infrastructure. Use when drawing AWS network diagrams, visualizing VPCs, mapping Transit Gateway topology, or generating architecture documentation.

Install

npx vskill@latest install automateyournetwork/netclaw/aws-architecture-diagram

SKILL.md

The same SKILL.md was published earlier as automateyournetwork/netclaw/aws-architecture-diagram.

AWS Architecture Diagram

MCP Server

  • Command: uvx awslabs.aws-diagram-mcp-server@latest (stdio transport)
  • Requires: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION (or AWS_PROFILE)
  • Dependency: Requires graphviz installed on the system (apt install graphviz or brew install graphviz)

Key Capabilities

  • Auto-discovery: Scan AWS account and render infrastructure as a diagram
  • Network topology: VPCs, subnets, route tables, IGW, NAT GW, TGW connections
  • Service mapping: EC2, ELB, RDS, Lambda placed in their VPC/subnet context
  • Multiple formats: PNG, SVG, PDF output
  • Filtered views: Scope diagram to specific VPCs, services, or tags

Workflow: Network Architecture Diagram

When a user asks "draw our AWS network" or "show me the architecture":

  1. Generate diagram: Use diagram tool scoped to networking resources
  2. Include: VPCs, subnets (public/private), IGW, NAT GW, TGW, VPN, peering connections
  3. Label: CIDR blocks, subnet names, AZ placement
  4. Connections: Show routing paths — TGW attachments, peering links, VPN tunnels
  5. Output: PNG or SVG file for sharing in Slack or documentation
  6. Report: Architecture summary alongside the diagram

Workflow: VPC Detail Diagram

When focusing on a specific VPC:

  1. Scope to VPC: Filter diagram to one VPC by ID or tag
  2. Show subnets: Public, private, isolated — grouped by AZ
  3. Show route tables: Main and custom route tables with key routes
  4. Show gateways: IGW, NAT GW, VPC endpoints
  5. Show security: NACLs, security group relationships
  6. Output: Detailed VPC topology diagram

Workflow: Multi-Account Network Diagram

When documenting cross-account architecture:

  1. Hub-spoke topology: Show Transit Gateway as the hub
  2. VPC attachments: Each spoke VPC with its CIDR and purpose
  3. Route propagation: Show which routes propagate where
  4. VPN/DX: On-premises connections via VPN or Direct Connect
  5. Inspection VPC: Network Firewall placement if applicable
  6. Output: Enterprise network topology diagram

Integration with Other Skills

SkillHow They Work Together
aws-network-opsDiscover VPCs/TGWs first, then diagram them
aws-cloud-monitoringAdd CloudWatch metrics annotations to diagram
aws-cost-opsAnnotate diagram with cost per resource
markmap-vizGenerate mindmap alternative for simpler overviews

Diagram Scoping Tips

ScopeWhen To Use
Full accountInitial architecture review or documentation
Single VPCTroubleshooting or VPC-specific audit
TGW + attachmentsMulti-VPC connectivity review
Subnet-levelSecurity audit or routing investigation
Tagged resourcesApplication-specific or team-specific views

Important Rules

  • Graphviz required — the MCP server generates Graphviz DOT files and renders them; graphviz must be installed
  • Large accounts may produce complex diagrams — scope with filters for clarity
  • Region-specific — diagram shows resources in the configured AWS_REGION only
  • Read-only — only discovers and renders, never modifies resources
  • Record in GAIT — log diagram generation for audit trail

Environment Variables

  • AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION (or AWS_PROFILE)

Failure Behavior

  • 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.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
674
Repository forks
189
7-day trend score
33

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/automateyournetwork/netclaw/aws-architecture-diagram/badge)](https://verified-skill.com/skills/automateyournetwork/netclaw/aws-architecture-diagram)

Something wrong with this skill or its page? Tell us.