Back to skills
extension
Category: Development & EngineeringNo API key required

monitoring-deployments

Use this skill when monitoring Spotify deployments, checking deployment status, viewing deploy progress, or tailing deployment logs. Triggers on "check deployment", "deploy status", "monitor deploy", "what's deploying", or when user runs /monitor-deploy.

personAuthor: jakexiaohubgithub

Monitoring Deployments

Monitor Spotify deployments via the Tugboat CLI with optional GCP log tailing.

Prerequisites

Check if tugboat exists. If not, auto-install:

uv tool install --from git+ssh://git@ghe.spotify.net/warpspeed/tugboat-cli.git tugboat-cli

Workflow

1. Get component

Use provided component name/pattern, or ask the user.

2. List installations

tugboat installations list --component=<component-or-pattern>

3. Get deployment status

tugboat deployments show --installation=<installation-id> <deployment-id>

For full JSON details:

tugboat deployments dump --installation=<installation-id> <deployment-id>

4. Get version info

tugboat version <component-id> show <version-id>

5. Summarize

Present concisely: state, progress %, version/commit, errors.

6. Offer log tailing

When in-progress or failed, offer to tail GCP logs. Parse log info from tugboat output and run:

gcloud logging tail "<filter>" --project=<project>

Batch mode

For patterns like fan-audio-*, show a table of all matching components.

Errors

  • Auth issues → gcloud auth login
  • Missing tugboat → auto-install
  • Bad component → list available ones