cloud
/cloud
Show Trinity Cloud Dev dashboard — containers, training farm, issues, PRs, costs. Use when checking agent swarm status, cloud containers, or CI/CD pipeline.
- Author
- trinity-s-ai-dna ↗
- Repository
- trinity ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Show Trinity Cloud Dev dashboard — containers, training farm, issues, PRs, costs. Use when checking agent swarm status, cloud containers, or CI/CD pipeline.
Arguments
/cloud [status|agents|events|full]
Original author description
Show Trinity Cloud Dev dashboard — containers, training farm, issues, PRs, costs. Use when checking agent swarm status, cloud containers, or CI/CD pipeline.
How it works
- Active Containers
- Recent Events (last 20)
- Agent Issues (labeled agent:spawn)
- Agent PRs (feat/issue- branches)
- Container Registry
- Railway Services
- Priorities
- Task
SKILL.md preview
---
name: cloud
description: Show Trinity Cloud Dev dashboard — containers, training farm, issues, PRs, costs. Use when checking agent swarm status, cloud containers, or CI/CD pipeline.
argument-hint: [status|agents|events|full]
allowed-tools: Bash(tri *), Bash(gh *), Bash(cat *), Bash(tail *), Bash(ls *), Bash(python3 *), Bash(date *), Read, Grep, Glob
model: haiku
context: fork
---
# Cloud Dev Dashboard
## Active Containers
!`/Users/playra/trinity-w1/zig-out/bin/tri cloud agents 2>&1 || echo "No tri binary — run zig build first"`
## Recent Events (last 20)
!`if [ -f /Users/playra/trinity-w1/.trinity/cloud_events.jsonl ]; then tail -20 /Users/playra/trinity-w1/.trinity/cloud_events.jsonl; else echo "No cloud events yet"; fi`
## Agent Issues (labeled agent:spawn)
!`gh issue list --repo gHashTag/trinity --label "agent:spawn" --state open --limit 10 2>&1 || echo "gh CLI unavailable"`
## Agent PRs (feat/issue- branches)
!`gh pr list --repo gHashTag/trinity --state open --limit 10 2>&1 || echo "gh CLI unavailable"`
## Container Registry
!`gh api user/packages?package_type=container 2>/dev/null | python3 -c "import sys,json; pkgs=json.load(sys.stdin); [print(f' {p[\"name\"]} — {p.get(\"updated_at\",\"?\")}') for p in pkgs]" 2>/dev/null || echo "No GHCR packages yet"`
## Railway Services
!`gh api repos/gHashTag/trinity/actions/runs --jq '.workflow_runs[:5] | .[] | " \(.name) #\(.run_number) — \(.status) (\(.conclusion // "running"))"' 2>/dev/null || echo "No recent workflow runs"`
## Priorities
!`head -30 /Users/playra/trinity-w1/.trinity/priorities.md 2>/dev/null || echo "No priorities file"`
## Task
Analyze the data above and present a **rich Cloud Dev dashboard** with emojis.
Focus area: $ARGUMENTS (default: status)
### Dashboard Format
ALWAYS output the full dashboard — never compress to one line. Use this format:
```
☁️ ═══════════════════════════════════════════════════
TRINITY CLOUD DEV — AGENT SWARM DASHBOARD
═══════════════════════════════════════════════════
🤖 ACTIVE CONTAINERS
[table: ID, issue#, role, status, uptime]
Total: N/10 slots used
📋 AGENT ISSUES (agent:spawn)
[list: #N — title — assignee — status]
🔀 AGENT PRs
[list: #N — title — branch — checks]
📡 RECENT EVENTS (last 10)
[timestamp] [emoji] event description
...
🏗️ INFRASTRUCTURE
GHCR: [status]
Railway: [status]
Actions: [last 5 runs with status]
🎯 P0 PRIORITIES
[from priorities.md]
📊 STATS
Containers active: N/10
Issues queued: N
PRs open: N
Last spawn: [timestamp]
Last merge: [timestamp]
```
### Status emojis:
- 🟢 Running / healthy
- 🟡 Pending / building
- 🔴 Failed / errored
- ⚪ Idle / no containers
- 🔵 Completed successfully
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · trinity-s-ai-dna/trinity | 100 | MIT |
| browser-use/browser-use | 100 | MIT |
| antgroup/agent3sigma-canary | 100 | Apache-2.0 |
| opensearch-project/opensearch-agent-skills | 100 | Apache-2.0 |
| atakanelik34/bilinc-memory-history | 96 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 5e5705303d69 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100agents
Agent swarm development dashboard — live Railway containers, issue queue, PR pipeline, JSONL events, pool utilization, and queue drain status. Use when checking agent dev tasks, spawning status, or monitoring issues #315-#319. - 88trinity-fleet-ops
Inspect and safely operate Trinity 11 Cloudflare Workers, Secrets Store, D1, KV, R2, AI and integrations. Use for staging and production work. Prefer proof of runner, permissions, isolation and deployment receipts. - 100dev-containers-docker-remote-development
Use this skill when standardizing developer toolchains and isolated runtime environments using VS Code Dev Containers. - 88dev-loop-dev-container
Use when the user asks about development containers, devcontainer.json, Dev Containers in VS Code/GitHub Codespaces, Docker-based dev environments, or reproducible development setups. Do NOT use for: production Dockerfiles, or CI/CD pipelines. - 100gcp-cloud-run-serverless-containers
Use this skill when deploying fully managed containerized microservices that autoscale to zero on Google Cloud Run. - 100cloud-architect
Use this agent when you need to design, evaluate, or optimize cloud infrastructure architecture at scale. Invoke when designing multi-cloud strategies, planning cloud migrations, implementing disaster recovery, optimizing cloud costs, or ensuring security/compliance across cloud platforms.