troubleshooting-health-checks

# Health Check Troubleshooting Skill

## Core Purpose

This skill enables Claude to troubleshoot Mission Control health checks by analyzing check configurations, diagnosing failure patterns, identifying timeout and error root causes, and recommending configuration adjustments to improve reliability.

Note: Read @skills/troubleshooting-health-checks/reference/query-syntax.md to for query syntax

## Health check troubleshooting workflow

Copy this checklist and track your progress:

```
Troubleshooting Progress:
- [ ] Step 1: Gather health check information
- [ ] Step 2: Analyze failure patterns
- [ ] Step 3: Cross-reference configuration issues
- [ ] Step 4: Create diagnostic summary
- [ ] Step 5: Verify remediation steps
```

## Gather health check information

To begin with, get the id of the check in question.
Use `search_health_checks` with query syntax to find checks. Read @skills/troubleshooting-health-checks/reference/query-syntax.md to for query syntax
Else, if you could not get the health check Id from the user provided name, use `list_all_checks` to get complete metadata for all health checks .

Then, follow this procedure:

- **Historical Context**: Use `get_check_status` to retrieve execution history
- **Investigate the check specification**: Understand the intention of the check.
- **Investiagte the chagnes to the canray**: Use `search_catalog_changes(<canary_uuid>)` to get the changes on the canary.
  Look for the change details to see any new changes on the specification.

## Analyze failure patterns

Examine the historical data to identify patterns. Look for:

- **Intermittent failures**: Passes sometimes, fails others
  - Suggests: Network instability, load-related issues, race conditions
- **Consistent failures**: Always failing
  - Suggests: Configuration error, endpoint down, authentication issue
- **Recent pattern changes**: Was passing, now failing
  - Suggests: Recent deployment, config change, infrastructure change
- **Timeout patterns**: Fail