seis-cloud

Plans and validates cloud deployments with provider-neutral records and rollback contracts.

1|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-cloud-emirhankudun-ux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seis-cloud
Source: https://github.com/emirhankudun-ux/SEIS/tree/main/plugins/seis/skills/seis-cloud
Command: npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-cloud-emirhankudun-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cloud deployment work often becomes hidden state, one-off commands, and leaked secrets. This Skill keeps hosting, server, VPN, and infrastructure work explicit, reversible, secret-safe, and validated inside the SEIS ecosystem. ## Core Features & Use Cases - Provider-Neutral Readiness: Maintains deployment records like deploy/cloud-environment.json, deploy/provider-matrix.json, and deploy/server-targets.json so cloud state stays traceable across Cloudflare, Vercel, Netlify, GCP, and other providers. - Access-Audience Classification: Separates public cloud surfaces from team/workplace VPN cloud targets, including GCP Compute with WireGuard and scoped SSH access profiles. - Gated Mutation Workflow: Runs plan and preflight checks first, requiring explicit user confirmation of provider, target, URL, and rollback owner before any deploy command. - Use Case: Before shipping a static site, run npm run check:cloud-environment and npm run check:server-target to verify configuration, then generate a self-hosted operator handoff bundle with npm run cloud:self-hosted:kit. ## Quick Start Ask the agent to plan and validate a SEIS cloud deployment for a specific provider and target before running any mutating commands.

Frequently Asked Questions about seis-cloud

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

FAQPage Schema
How do I validate a cloud deployment before deploying?▼

Run preflight checks such as `npm run check:cloud-environment`, `npm run check:server-target`, and `npm run check:cloud-access-policy` before any mutation. Deploy commands stay gated until you explicitly confirm the provider, target, public URL, and rollback owner.

How do I set up a team VPN cloud server with GCP and WireGuard?▼

Classify the target as team/workplace VPN cloud, then use the self-hosted kit via `npm run cloud:self-hosted:kit -- --ssh-target root@HOST --peer-public-key CLIENT_PUBLIC_KEY`. It creates an operator handoff bundle under `dist/` for SSH, WireGuard, and release roots.

Which cloud providers does this deployment workflow support?▼

It supports Cloudflare, Vercel, Netlify, Render, Firebase, Supabase, Neon, Convex, GitHub Pages, and Google Cloud when authenticated and scoped. Provider-neutral records in `deploy/` keep changes traceable across all of them.

Can deployment commands run without user confirmation?▼

No. Mutating cloud commands require explicit confirmation of the provider, project or site, path, public URL, and rollback owner. Plan and preflight commands run first so every change stays reversible and auditable.

Why must VPN source ranges avoid 0.0.0.0/0?▼

Broad ranges like `0.0.0.0/0` or `::/0` expose team VPN cloud surfaces to everyone, violating the access policy. The workflow enforces narrow, approved peer ranges and validates them with `npm run check:cloud-access-policy`.