monitor-deploy_skill

This skill helps you monitor Spotify deployments by using Tugboat CLI, showing status, progress, and optionally tails logs.
  • Shell

3

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill tdhopper/dotfiles2.0 --skill monitor-deploy

  • SKILL.md1.5 KB

Overview

This skill monitors Spotify deployments using the Tugboat CLI and can optionally tail GCP logs for live insight. It helps check deployment status, view progress, summarize version and errors, and follow logs when a deployment is in progress or failed. Use it interactively or via the /monitor-deploy trigger for quick checks.

How this skill works

The skill ensures tugboat is available and auto-installs it if missing. It lists installations for a component, fetches deployment details and version information, and summarizes state, progress, version/commit, and errors. When needed, it parses log filters from tugboat output and runs gcloud logging tail to stream logs for the relevant project.

When to use it

  • Check current deployment status for a specific component or installation
  • Monitor progress of an ongoing deployment and estimate completion
  • Investigate failed deployments and surface errors and failing steps
  • Tail production or staging logs when a deployment is stuck or exhibiting issues
  • Quickly scan multiple components with a name pattern in batch mode

Best practices

  • Provide a precise component name or pattern to avoid long lists
  • Use installation IDs when available for direct lookups
  • If tugboat is missing, allow the tool to auto-install to avoid interruptions
  • When tailing logs, ensure you are authenticated with gcloud (gcloud auth login)
  • Use the full JSON dump when you need detailed fields or trace IDs for log correlation

Example use cases

  • Check deployment status: run tugboat deployments show to get state, progress, and errors
  • Batch monitor: query installations for fan-audio-* and display a table of matching deployments
  • Investigate failure: fetch deployments dump for detailed JSON, then tail GCP logs filtered by the parsed filter
  • Confirm version: run tugboat version <component-id> show <version-id> to validate the deployed commit
  • Live troubleshooting: when a deployment is stuck, stream gcloud logging tail with the parsed filter to watch events in real time

FAQ

The skill auto-installs tugboat using the configured tool installer command. If that fails, install tugboat manually with the provided uv tool install command.

How do I stream logs for a failing deployment?

When the deployment is in-progress or failed, the skill extracts a log filter from tugboat output and runs gcloud logging tail "<filter>" --project=<project>. Make sure you are authenticated with gcloud (gcloud auth login).

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational