excalidash-devops-cloud-deployment

Generates CI/CD pipeline and cloud deployment topology diagrams via the ExcaliDash MCP server.

2|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/gabedsam01/excalidash-v2 --skill excalidash-devops-cloud-deployment-gabedsam01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: excalidash-devops-cloud-deployment
Source: https://github.com/gabedsam01/excalidash-v2/tree/main/skills/excalidash/excalidash-devops-cloud-deployment
Command: npx skills add https://github.com/gabedsam01/excalidash-v2 --skill excalidash-devops-cloud-deployment-gabedsam01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Drawing a clear CI/CD pipeline plus cloud deployment topology by hand is slow and error-prone: pipeline stages end up out of order, promotion arrows get confused with traffic paths, and managed services land in the wrong frame. This Skill produces a validated deployment diagram that shows both the left-to-right delivery pipeline and the runtime topology (zones, cluster, environments, load balancer, managed services) on one canvas. ## Core Features & Use Cases - Three creation paths: build from a text prompt, from a repository analysis, or by converting an existing architecture/microservices drawing into a deployment view. - Structured topology rules: pipeline stages ordered left-to-right ending at a single registry hinge, framed environments (dev/stage/prod) inside a cluster frame inside a VPC/zone frame, managed services outside the cluster, and traffic entering only via the load balancer. - Quality loop with scoring: lint, score, repair, polish, and architecture validation iterate until the drawing scores at least 95 with zero hard blockers, with rollback to checkpoints on regression. - Secret redaction: registry tokens, kubeconfig credentials, database URLs, and cloud provider keys are redacted before any tool call and re-scanned in the export. - Use Case: Ask for "GitHub Actions builds and pushes to ECR, Argo CD deploys to an EKS cluster with dev/stage/prod behind an ALB" and receive a saved, shareable, exportable Excalidraw deployment diagram. ## Quick Start Ask the assistant to draw your CI/CD pipeline and cloud deployment, naming your CI tool, container registry, cloud provider, cluster, environments, and managed services.

Frequently Asked Questions about excalidash-devops-cloud-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draw a CI/CD pipeline and cloud deployment diagram with AI?

Describe your delivery path and runtime: CI tool, container registry, cloud provider and region, orchestration cluster, environments, load balancer, and managed services. The skill creates a deployment diagram with a left-to-right pipeline band and a framed runtime topology, then lints, scores, and repairs it to at least 95.

Can I convert an existing architecture diagram into a deployment view?

Yes. The convert_diagram_type tool with targetType deployment re-casts an existing architecture or microservices drawing into a deployment topology, regrouping services into environment frames inside a cluster and zone frame. You can also build from a repository analysis JSON.

What cloud providers and orchestrators does the deployment diagram support?

The skill handles AWS, GCP, and Azure zones with provider logos in cloud-provider slots, and orchestrators such as Kubernetes (EKS, GKE, AKS), ECS, Nomad, or serverless runtimes. Managed services like RDS, Cloud SQL, Memorystore, and object stores are placed in the zone frame outside the cluster.

When should I not use the deployment diagram skill?

Do not use it for internal application structure (use a C4 container view), pure telemetry pipelines (use an observability flow), incident walkthroughs (use a troubleshooting swimlane), or MCP server internals. If one canvas needs every environment fully exploded plus the full pipeline, split it into separate cross-referenced diagrams.

How are secrets like registry tokens and database URLs handled in diagrams?

All secrets are redacted before any tool call: registry tokens become [REDACTED_TOKEN] placeholders, database URLs mask the password, and provider keys become [REDACTED_PROVIDER_KEY]. The exported SVG or PNG is re-scanned to confirm no live credential leaked into the drawing.

Why does my deployment diagram fail validation?

Common blockers are ARROW_TEXT_INTERSECTION (labels under routed lines), FRAME_TITLE_OVERLAP (frame titles colliding with nodes), and ITEM_OUTSIDE_FRAME (workloads outside env frames or managed services inside the cluster). The repair loop fixes these and re-scores until reaching 95 with zero blockers.