Menü
Check macOS GHA runner status for the getditto org
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | work-runners |
| description | Check macOS GHA runner status for the getditto org |
Use this skill when the user asks to run the migrated command work-runners or invokes $work-runners.
Query the getditto org's macOS runner group and report status.
Runner group ID 8 is the "macOS" group in the getditto org.
gh api orgs/getditto/actions/runner-groups/8/runners --jq '{
total: .total_count,
online: [.runners[] | select(.status == "online")] | length,
offline: [.runners[] | select(.status == "offline")] | length,
offline_names: [.runners[] | select(.status == "offline") | .name],
busy: [.runners[] | select(.busy == true)] | length,
busy_names: [.runners[] | select(.busy == true) | .name]
}'
Format as a concise summary:
## macOS GHA Runners (getditto)
Online: 34/34
Offline: 0
Busy: 5 — mac-ami01, mac-ami02, mac-ami03, mac-ami04, mac-ami05
If any runners are offline, list them with a warning:
⚠ Offline: 2 — mac-ami14, mac-ami22
If all runners are online and none are offline, report clean:
✓ All 34 runners online
If called with --detail or --verbose argument, also show per-runner status:
gh api orgs/getditto/actions/runner-groups/8/runners --jq '.runners | sort_by(.name) | .[] | "\(.status)\t\(.busy)\t\(.name)\t\(.labels | map(.name) | join(", "))"'
Format as a table.
End-of-day — draft and post daily comments for tracked tickets missing a comment
Morning startup workflow for daily notes, yesterday summary, agenda, status comments, meeting sections, and daily branch setup. Use when invoked as `$work-start` or when the user asks to start the work day.
Track a Linear ticket or GitHub PR in today's daily note with fields and timestamped activity. Use when invoked as `$work-track` or when the user asks to track a work item.
Start work on a Linear ticket by gathering context, planning, creating a branch/worktree, implementing, testing, opening a draft PR, and updating Linear. Use when invoked as `$linear-plan` or when the user asks to start a Linear ticket.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.