1 · Why it matters
Why it was worth building
AI skills scaffold a new integration from the engineer’s requirements, and it ships through one pipeline, so delivery no longer waits on one engineer.
Every app reports its health to one place, and an AI triage proof of concept adds the likely cause and next steps. Fixes land once in shared clients.
Support re-runs customer reports without an engineer, and solutions engineers build on the platform.
2 · How it’s built
Built once, reused by every app
Standard parts only: Docker VMs, Vault, BigQuery, Pub/Sub and Cloud Run. A new integration adds just its business logic.
How a new integration ships
The same steps for every integration, from idea to production.
What it changes
- AI scaffolds the appA skill interviews the engineer about their requirements, writes the spec and generates the app, its CI job and its deploy config in minutes. A new engineer is onboarded in under 15 minutes.
- Fix once, every app gets itShared MyGeotab, GCP and Vault clients. A paging bug was fixed once in the shared client, not 15 times.
- Every merge is checkedTests and a security scan run on every MR. The app catalog is rebuilt on every merge, so it can’t drift from the code.
- Self-service deploysA plan-then-apply deploy tool with automatic backup. I deployed the team’s first Cloud Run function through Terraform.
The operations loop
How engineers and support see and fix what’s running.
What it changes
- One contract for every appEach app writes a heartbeat every 60 seconds and a start and finish row per run, so a new app appears with no custom work.
- Role-gated accessGoogle sign-in with admin, rerun and viewer roles.
- Reruns without an engineerA rerun waits 10 minutes so a mistake can be cancelled, then goes through Pub/Sub to the app.
- Health is monitored, not discoveredAlerts are declared in YAML per app and posted to Chat, so integration engineers can resolve issues proactively.
- AI triage Proof of conceptAdds the likely cause of an unhealthy app and the next steps to resolve it, so whoever picks up the alert starts with a diagnosis. Runs in a test project.
3 · Who runs it
Others run it and build on it
Run it without me
- Customer supportRe-runs customer reports from the dashboard, with no engineer in the loop.
- Solutions EngineeringWrote a support guide around the dashboard.
Build on it
- A regional Solutions EngineerContributing code to a pipeline and preparing to operate it.
- Another Solutions EngineerBuilt a bulk importer based on my import tools, for ad-hoc customer onboarding of tens of thousands of users and groups.
- Data scientistsDeployed a backend service for a customer project with my deploy tool, to support their machine-learning analysis work.
Dashed = a manual step the platform removes
Building a new job
- Write the job
- Write a scheduler (manual step)
- Add logging (manual step)
- Copy to a VM (manual step)
- Run it by hand (manual step)
- no monitoring, no alerts
- AI skills scaffold the app
- Add the business logic
- Merge and deploy
- built in:
- Scheduling
- Monitoring
- Chat alerts
- Run on demand
A job goes wrong
- Job fails quietly
- Customer notices
- Ticket (manual step)
- Engineer logs in to the VM (manual step)
- Reads the logs (manual step)
- Fix
- found late
- Job misses a run
- Health turns red
- Alert in Chat
- Fix
- flagged in Chat
Re-running a customer’s report
- Customer asks
- Ticket (manual step)
- Engineer with VM access (manual step)
- Script run by hand (manual step)
- needs an engineer
- Support
- Dashboard
- Rerun
- self-service