Agent skill
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/monitor-deploy
SKILL.md
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://[email protected]/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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?