Help us improve
Share bugs, ideas, or general feedback.
From chittyos-devops
Check health status of ChittyOS services across the ecosystem.
npx claudepluginhub chittyos/chittymarket --plugin chittyos-devopsHow this skill is triggered — by the user, by Claude, or both
Slash command
/chittyos-devops:chitty-healthThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Check health status of ChittyOS services across the ecosystem.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.
Share bugs, ideas, or general feedback.
Check health status of ChittyOS services across the ecosystem.
/health [service-name|all]
| Parameter | Required | Default | Description |
|---|---|---|---|
| service-name | No | all | Specific service or "all" for full check |
| Service | Domain | Expected Response |
|---|---|---|
| chittyid | id.chitty.cc | {"status":"ok","service":"chittyid"} |
| chittyauth | auth.chitty.cc | {"status":"ok","service":"chittyauth"} |
| chittyschema | schema.chitty.cc | {"status":"ok","service":"chittyschema"} |
| chittyregistry | registry.chitty.cc | {"status":"ok","service":"chittyregistry"} |
| Service | Domain | Expected Response |
|---|---|---|
| chittyconnect | connect.chitty.cc | {"status":"ok","service":"chittyconnect"} |
| chittyapi | api.chitty.cc | {"status":"ok","service":"chittyapi"} |
| chittymcp | mcp.chitty.cc | {"status":"ok","service":"chittymcp"} |
curl -s https://{service}.chitty.cc/health | jq .
for service in id auth connect api registry schema mcp; do
echo -n "$service: "
curl -s "https://$service.chitty.cc/health" --max-time 5 | jq -r '.status // "DOWN"'
done
# Check response time
time curl -s https://{service}.chitty.cc/health
# Check SSL certificate
curl -vI https://{service}.chitty.cc 2>&1 | grep -A2 "Server certificate"
# Check Cloudflare headers
curl -sI https://{service}.chitty.cc | grep -i "cf-"
| Status | Meaning | Action |
|---|---|---|
{"status":"ok"} | Healthy | None needed |
| Connection refused | Not deployed | Run /deploy |
| DNS error | No DNS record | Configure in Cloudflare |
| 502/503 | Worker error | Check wrangler logs |
| Timeout | Performance issue | Check worker metrics |
# View worker logs
wrangler tail {worker-name} --env production
# Check deployment status
wrangler deployments list