How this command is triggered — by the user, by Claude, or both
Slash command
/gcp-iot:status [--project <project-id>]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# GCP Status Command Quick health check of all GCP IoT services showing current status at a glance. ## What This Command Does 1. Check GCP authentication status 2. List Cloud Run services with health 3. Show Pub/Sub topics and subscriptions 4. Display recent error count 5. Show overall system health ## Execution Steps ### Step 1: Authentication Check ### Step 2: Cloud Run Services ### Step 3: Pub/Sub Resources ### Step 4: Error Count (Last Hour) ### Step 5: Generate Status Dashboard ## Health Determination **🟢 HEALTHY**: - All Cloud Run services responding - No errors in l...
Quick health check of all GCP IoT services showing current status at a glance.
gcloud auth list --filter=status:ACTIVE --format="value(account)"
gcloud config get-value project
gcloud run services list --project=[PROJECT_ID] \
--format="table(SERVICE,REGION,LAST_DEPLOYED,URL)"
# Topics
gcloud pubsub topics list --project=[PROJECT_ID] --format="value(name)"
# Subscriptions with key info
gcloud pubsub subscriptions list --project=[PROJECT_ID] \
--format="table(name.basename(),topic.basename(),pushConfig.pushEndpoint:label=PUSH_ENDPOINT)"
gcloud logging read "severity>=ERROR AND timestamp>=\"$(date -u -d '1 hour ago' '+%Y-%m-%dT%H:%M:%SZ')\"" \
--project=[PROJECT_ID] \
--format="value(severity)" | wc -l
## GCP IoT Status Dashboard
**Project**: [project-id]
**Account**: [email]
**Checked**: [timestamp]
### 🟢 Overall Health: HEALTHY / 🟡 DEGRADED / 🔴 UNHEALTHY
---
### Cloud Run Services
| Service | Region | Status | URL |
|---------|--------|--------|-----|
| api-service | us-central1 | 🟢 Running | https://... |
| ws-service | us-central1 | 🟢 Running | https://... |
### Pub/Sub
| Topic | Subscriptions | Status |
|-------|---------------|--------|
| telemetry | 2 | 🟢 OK |
| events | 1 | 🟢 OK |
### Subscriptions
| Name | Type | Endpoint/Status |
|------|------|-----------------|
| telemetry-push | PUSH | https://ws-service... |
| telemetry-pull | PULL | Active |
### Recent Activity
- Errors (1h): [count]
- Warnings (1h): [count]
---
### Quick Actions
- View logs: `/gcp:logs errors`
- Run diagnostic: `/gcp:diagnose`
- Trace telemetry: `/gcp:trace`
🟢 HEALTHY:
🟡 DEGRADED:
🔴 UNHEALTHY:
/gcp:status
/gcp:status --project my-iot-project
npx claudepluginhub maxcogar/agent-armory --plugin gcp-iot/statusDisplay Conductor project status including overall progress, active tracks summary, and next actions. Optional [track-id] [--detailed] for per-track task details and blockers.
/statusDisplays compact planning status from task_plan.md: current phase and progress, phase list with icons, error count, and planning file checks.
/statusShows active and recent Codex jobs for this repository in a compact Markdown table, including review-gate status. Pass job ID for full details; supports --wait, --timeout-ms, --all.
/statusDisplays current design system state from .interface-design/system.md including direction, foundation, depth, tokens, patterns, and last updated time. Suggests setup options if no system found.
/statusChecks current session status and measures goal drift to assess alignment and progress in the conversation.
/statusDisplays status of tasks in the orchestration system, including summaries, distributions, detailed views, timelines, and velocity reports with filters for date, status, agent, priority, and type.