Onboards new users to the Eddytor MDM platform via MCP connection, authentication, and first table creation. Activates for Eddytor onboarding, MCP setup, workspace exploration, or first table creation — even without the phrase "getting started."
Deploys self-hosted Eddytor on Azure Kubernetes Service (AKS). Builds on eddytor-deploy-helm — only the Azure-specific deltas live here. Activates for AKS, Azure Kubernetes, az aks, deploy on Azure, Azure Database for PostgreSQL Flexible Server, Azure Blob storage, or quota/vCPU errors during cluster creation.
Installs self-hosted Eddytor on any Kubernetes cluster using the published OCI Helm chart. Activates for deploying Eddytor on Kubernetes, Helm install, the eddytor chart, ingress/TLS, external vs bundled Postgres, or scaling the engine — cluster-agnostic. Cloud-specific skills (AKS/GKE/EKS/Hetzner) build on this one.
Backup, restore, and secret rotation for self-hosted Eddytor. Activates for backup, restore, disaster recovery, key rotation, rotate secrets, the encryption key (EDDYTOR_ENCRYPTION_KEY), the API key secret (EDDYTOR_API_KEY_SECRET), OAuth signing keys, Postgres backups, or recovering a lost admin key.
Deploys self-hosted Eddytor on Amazon EKS — the AWS-specific deltas on top of the cluster-agnostic Helm skill. Activates for EKS, Elastic Kubernetes Service, eksctl, deploy on AWS, RDS for Postgres, S3 object store, ALB/NLB ingress, or IRSA — even without the phrase "deploy on EKS."
Deploys self-hosted Eddytor on Hetzner Cloud — the budget path. Hetzner has no managed Kubernetes, so you bring your own k3s (hetzner-k3s or k3sup) plus the Hetzner Cloud Controller Manager and hcloud-csi driver, then install the chart. Activates for Hetzner, hcloud, hetzner-k3s, k3s on Hetzner, Hetzner Object Storage, Hetzner Load Balancer, or "cheapest way to self-host Eddytor."
Best practices for high-performance bulk reads from Eddytor over Apache Arrow Flight SQL. Activates for Flight SQL, ADBC, Arrow, bulk export, large result sets, BI tools, connecting Tableau/Power BI/pandas, or "the query is too big for REST" — even without the phrase "Flight SQL."
Best practices for the Eddytor Python SDK (`eddytor-sdk` on PyPI) — connecting, querying to pandas/Arrow, ingesting data, and using table handles. Activates for the Python SDK, eddytor-sdk, EddytorClient, query to a DataFrame, pandas/pyarrow integration, or scripting Eddytor from Python — even without "SDK."