B

B — Some risk signals Graded October 16, 2026Minor concerns worth a quick check.Based on public adoption and transparency signals as of October 16, 2026. Our opinion, not a code audit or security guarantee.

AI agent skill · Developer tools, Data & databases

drawio-skill

Agent skill that turns natural language, code, Terraform/K8s, SQL, OpenAPI, AsyncAPI, Protobuf and GraphQL sources into editable, tested draw.io architecture diagrams: incremental sync, multi-view projection, drift diff, CI architecture tests, whiteboard derasterize, interactive HTML/PPTX/Mermaid exports.

Bottom line: Signal-based grade (4/7 points): very widely starred on GitHub, public source code. This reflects adoption and transparency, not a code review.

Popularity score
45/100
Rank
#207 of 500
GitHub stars
10.2k

What it does

Converts natural language, code, infrastructure-as-code (Terraform/Kubernetes), SQL, APIs (OpenAPI/AsyncAPI), Protobuf, and GraphQL into interactive draw.io architecture diagrams. Supports incremental syncing, multi-view projections, drift detection, CI testing, and exports to HTML, PPTX, and Mermaid formats.

Who it’s for

Engineering teams and architects who need to auto-generate and maintain living architecture documentation from code and infrastructure definitions. Builders integrating diagram generation into CI/CD pipelines or AI agent workflows.

Copy-paste setup

Check these steps against the project’s own instructions before running anything.

Verify against the repo README at https://github.com/Agents365-ai/drawio-skill (opens external site) for current setup instructions. Likely installation via npm or integration as an MCP server; exact steps depend on agent platform (Claude Desktop, custom frameworks, etc.). Check repository for mcpServers JSON configuration or CLI invocation patterns.

Risks

  • Credential exposure: May parse infrastructure files (Terraform, K8s manifests) containing secrets, API keys, or connection strings—ensure inputs are sanitized and outputs are access-controlled.
  • Prompt injection: Natural language input could be crafted to inject malicious diagram logic or exfiltrate metadata about infrastructure topology.
  • Data exfiltration: Generated diagrams may inadvertently expose sensitive architecture details, internal service names, or database schemas if sent to external draw.io cloud or third-party export services.
  • Supply chain risk: Dependency on draw.io format and potential external rendering services; verify whether diagrams are processed locally or transmitted remotely.
  • Code parsing vulnerabilities: Parsing multiple languages (SQL, GraphQL, Protobuf) may introduce injection or DoS risks if the parser is not hardened against malformed input.

How to stay secure

Hardening Guide: drawio-skill

Least-privilege permissions

  • Restrict file access: Only grant the skill permission to read infrastructure files it needs; block access to sensitive folders, credential vaults, and unrelated systems.
  • Control output destinations: Limit where diagrams can be saved or exported (e.g., only to internal storage, not cloud services or public URLs).
  • Separate user roles: Ensure only authorized team members can run the skill and view generated diagrams; prevent junior staff from accessing sensitive infrastructure topology.
  • Rotate credentials before parsing: If possible, temporarily revoke or mask secrets in Terraform/Kubernetes files before feeding them to the skill.

Network isolation

  • Keep processing local: Ensure diagram generation and rendering stays within your private network; configure the skill to never send data to external draw.io cloud services without explicit approval.
  • Block outbound connections: Use firewalls to prevent the skill from reaching unfamiliar APIs, file-sharing services, or cloud storage without prior authorization.
  • Validate export services: If diagrams must be exported (to PowerPoint, HTML, etc.), verify the export process stays on-premises or uses only trusted, vetted vendors.
  • Segment from production: Run the skill on isolated systems separate from live infrastructure; prevent it from directly querying production databases.

Monitoring

  • Log all diagram generation: Record what infrastructure files were parsed, who requested the diagram, and where outputs were sent.
  • Audit input/output content: Scan generated diagrams for unexpected service names, database credentials, or sensitive IP addresses; flag unusual patterns.
  • Track file access: Monitor which users access infrastructure source files before and after skill execution to detect misuse.
  • Alert on suspicious parsing: Set up warnings if the skill encounters malformed or unusually large files, which may indicate attack attempts.

Red flags to watch for

  • Diagrams containing plaintext secrets: If exported diagrams include API keys, passwords, or connection strings, immediately revoke those credentials.
  • Unexpected external connections: Any attempt by the skill to contact cloud services, CDNs, or unknown domains outside your approved vendor list.
  • Permission escalation requests: If the skill suddenly demands access to credential stores, admin accounts, or production systems it didn't need before.
  • Garbled or suspicious diagram logic: If the skill generates components or connections that don't match your actual infrastructure, this may indicate prompt injection or parser abuse.

Alternatives

  • Mermaid CLI – Open-source diagram-as-code with native support for flowcharts and architecture; no AI agent integration but lightweight and fully local.
  • Structurizr – Domain-specific language (DSL) and tooling for C4 model diagrams; requires explicit schema definition rather than auto-inference.
  • CloudSkew / Lucidchart APIs – Cloud-based diagramming with programmatic access; more mature but SaaS-dependent and typically require manual schema mapping.
  • PlantUML – Text-based UML and diagram generation; lower-level control but requires manual layout and no built-in infrastructure-as-code parsing.

Sources