| name | Team Health Scan |
| description | On-demand snapshot of the Team-Health-Watchdog (THW) verdicts. Returns per-team health (🟢/🟡/🔴/🚨/🟪) plus the gates that fired, so an operator can investigate before the next 60s sweep. |
| version | 1.0.0 |
| category | monitoring |
| skillType | claude-skill |
| assignableRoles | ["orchestrator"] |
| triggers | ["team health","health scan","is anything stuck","team-health-scan"] |
| tags | ["team-health","watchdog","monitoring","liveness"] |
| execution | {"type":"script","script":{"file":"execute.sh","interpreter":"bash","timeoutMs":30000}} |
Team Health Scan
Returns the current per-team health verdicts from the Team-Health-Watchdog (THW), the system-level liveness aggregator (Layer 4 of the four-layer liveness stack).
When to use
- Before EOD: "is anything stuck I should know about?"
- After a Slack alert: "you flagged Marketing 🔴; show me the gates."
- During shadow-mode review: inspect candidate detections without waiting for the next sweep.
Verdict tiers
| Code | Display | Meaning |
|---|
healthy | 🟢 | No concerning signals |
stalling | 🟡 | Soft concern; observation-only |
stuck | 🔴 | Sharp concern; action expected |
cascade | 🚨 | Multi-team correlated failure |
stale | 🟪 | Stale-trigger refire — assignee should confirm/cancel |
Usage
bash execute.sh '{}'
bash execute.sh '{"teamId":"marketing"}'
bash execute.sh '{"force":true}'
Response shape
{
"success": true,
"data": {
"verdicts": [
{
"teamId": "marketing",
"verdict": "stuck"