Agent skill
diagnose-maestro-deployment
Diagnoses failed Maestro cluster deployments by analyzing Helm releases, pod status, and resource conflicts
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/diagnose-maestro-deployment
SKILL.md
Diagnose Maestro Deployment
Automatically diagnoses failed Maestro cluster deployments by:
- Analyzing deployment output to identify resource groups and cluster names
- Checking Helm release status in both service and management clusters
- Inspecting pod states and error conditions
- Identifying resource conflicts and timing issues
- Generating a detailed analysis report with root cause and recommendations
Prerequisites:
- Azure CLI installed and logged in
- kubectl and kubelogin installed
- Access to the failed deployment output or cluster information
Usage:
# Diagnose using deployment output file
diagnose-maestro-deployment /path/to/deployment.output
# Diagnose using cluster names directly
diagnose-maestro-deployment --svc-rg <resource-group> --svc-cluster <cluster-name> --mgmt-rg <resource-group> --mgmt-cluster <cluster-name>
#!/bin/bash
# Execute the diagnostic script
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
exec "$SCRIPT_DIR/scripts/diagnose.sh" "$@"
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?