zstack-ops

Estrellas12

Forks3

Actualizado1 de julio de 2026 a las 16:05

Use when operating, debugging, or extending ZStack workspaces, deployments, provider resources, domains, telemetry, or API-driven deploy flows.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

idanbeck

idanbeck/claude-skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	zstack-ops
description	Use when operating, debugging, or extending ZStack workspaces, deployments, provider resources, domains, telemetry, or API-driven deploy flows.

ZStack Ops

Scope

Use this skill for ZStack control-plane work: workspace provisioning, deploy failures, live logs, Fly resources, domains/DNS, telemetry, and API automation.

Work from /Users/idanbeck/zerg-stack/zstack unless the task names another repo.

Safety

Prefer the ZStack API over direct database edits.
Do not print API tokens, session cookies, or provider credentials.
Use /private/tmp/zstack-cookie.txt for curl cookies and overwrite it between sessions.
When fly cannot find auth locally, pass FLY_ACCESS_TOKEN from ~/.fly/config.yml inside the same command and never echo it.
Confirm the target workspace, environment, branch, and provider app before changing live infrastructure.

Auth

Set the base URL and log in with a cookie jar:

ZSTACK_BASE_URL=https://zergstack.com
ZSTACK_COOKIE=/private/tmp/zstack-cookie.txt
curl -sS -c "$ZSTACK_COOKIE" \
  -H 'content-type: application/json' \
  -d "{\"email\":\"$ZSTACK_EMAIL\",\"password\":\"$ZSTACK_PASSWORD\"}" \
  "$ZSTACK_BASE_URL/api/auth/login"

Verify the session:

curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/auth/me"

Discover State

List workspaces:

curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/workspaces"

Read one workspace and its environments:

curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/workspaces/<workspace-slug>"
curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/envs/<environment-id>"

Read provider resources, domains, and telemetry:

curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/envs/<environment-id>/resources"
curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/envs/<environment-id>/domains"
curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/envs/<environment-id>/telemetry"

Deploy Debugging

Find recent deploys:

curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/deploys?app=<app-slug>&env=<env-name>&limit=5"

Read a deploy and logs:

curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/deploys/<deploy-id>"

Stream logs while a deploy is running:

curl -N -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/deploys/<deploy-id>/stream?after=0"

Diagnose in this order:

Read deploy.status, deploy.error, branch, commit, and release fields.
Inspect the last 200 log lines, then find the first fatal build/runtime error.
Check whether the app deploy failed, the machine started but health failed, or the control-plane status is stale.
Compare zstack.yaml source settings with the target repo's deploy files (fly.toml, Dockerfile, package files, migration docs).
For Fly-backed apps, compare API resources with fly status, fly logs, fly machines list, and fly volumes list.

Retry Deploy

Trigger a manual deploy:

curl -sS -b "$ZSTACK_COOKIE" \
  -H 'content-type: application/json' \
  -d '{"branch":"<branch-name>"}' \
  "$ZSTACK_BASE_URL/api/envs/<environment-id>/deploy"

After triggering, stream the returned deploy id until it reaches success or failed.

Relevant API Surface

POST /api/auth/login
GET /api/auth/me
GET /api/workspaces
GET /api/workspaces/:slug
GET /api/envs/:id
POST /api/envs/:id/deploy
POST /api/envs/:id/restart
POST /api/envs/:id/suspend
GET /api/envs/:id/resources
PATCH /api/envs/:id/resources
POST /api/envs/:id/resources/apply
GET /api/envs/:id/domains
POST /api/envs/:id/domains
POST /api/envs/:id/domains/:domainId/check
POST /api/envs/:id/domains/:domainId/apply-dns
POST /api/envs/:id/domains/:domainId/wire
GET /api/envs/:id/telemetry
GET /api/deploys
GET /api/deploys/:id
GET /api/deploys/:id/stream

Más de este repositorio

mismo repositorio

zergboard-skill

idanbeck/claude-skills

Read and manage Zergboard cards, boards, and workspaces. Use when the user asks to check Zergboard, view cards, find tasks, check sprint/cycle status, manage work items, invite guests, or interact with their Zergboard boards from the CLI.

2026-07-2212

blink-skill

idanbeck/claude-skills

Blink Camera Skill

2026-07-2212

doordash

idanbeck/claude-skills

Order food on DoorDash for the Beck family using the DoorDash CLI (dd-cli), composing a balanced order that covers everyone's tastes and is age-appropriate for the kids, then placing it only after Idan approves the exact items, total cost, tip, card, and ETA. Use when Idan wants to order dinner/food for the family, wants a DoorDash recommendation, or says "order us food." Reads Personal/Family Food Profile.md for tastes, allergies, and rules.

2026-07-2212

voice-mode

idanbeck/claude-skills

Talk to Claude by voice. Records the mic, transcribes with ElevenLabs Scribe (hosted STT, no local Whisper), sends the text to Claude via the local `claude` CLI, and speaks the reply back with ElevenLabs TTS. Use when the user wants a spoken/voice conversation, voice input, or to dictate to Claude.

2026-07-2212

substack-skill

idanbeck/claude-skills

Create, edit, publish, schedule, and manage Substack posts. Use when the user asks to draft or publish a Substack post, list/edit their Substack drafts, schedule a post, or upload images to Substack. Supports multiple accounts/publications.

2026-07-0312

digital-twin

idanbeck/claude-skills

Generate audio or video of a specific person (the user) saying arbitrary text. Clones the user's voice with ElevenLabs (Professional Voice Clone) and drives a talking-head video with fal.ai audio-driven avatar models. Use when the user wants to make their voice say something, produce a talking-head video of themselves, or build/manage their voice/face twin.

2026-07-0112

name	zstack-ops
description	Use when operating, debugging, or extending ZStack workspaces, deployments, provider resources, domains, telemetry, or API-driven deploy flows.

ZStack Ops

Scope

Use this skill for ZStack control-plane work: workspace provisioning, deploy failures, live logs, Fly resources, domains/DNS, telemetry, and API automation.

Work from /Users/idanbeck/zerg-stack/zstack unless the task names another repo.

Safety

Prefer the ZStack API over direct database edits.
Do not print API tokens, session cookies, or provider credentials.
Use /private/tmp/zstack-cookie.txt for curl cookies and overwrite it between sessions.
When fly cannot find auth locally, pass FLY_ACCESS_TOKEN from ~/.fly/config.yml inside the same command and never echo it.
Confirm the target workspace, environment, branch, and provider app before changing live infrastructure.

Auth

Set the base URL and log in with a cookie jar:

ZSTACK_BASE_URL=https://zergstack.com
ZSTACK_COOKIE=/private/tmp/zstack-cookie.txt
curl -sS -c "$ZSTACK_COOKIE" \
  -H 'content-type: application/json' \
  -d "{\"email\":\"$ZSTACK_EMAIL\",\"password\":\"$ZSTACK_PASSWORD\"}" \
  "$ZSTACK_BASE_URL/api/auth/login"

Verify the session:

curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/auth/me"

Discover State

List workspaces:

curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/workspaces"

Read one workspace and its environments:

curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/workspaces/<workspace-slug>"
curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/envs/<environment-id>"

Read provider resources, domains, and telemetry:

curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/envs/<environment-id>/resources"
curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/envs/<environment-id>/domains"
curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/envs/<environment-id>/telemetry"

Deploy Debugging

Find recent deploys:

curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/deploys?app=<app-slug>&env=<env-name>&limit=5"

Read a deploy and logs:

curl -sS -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/deploys/<deploy-id>"

Stream logs while a deploy is running:

curl -N -b "$ZSTACK_COOKIE" "$ZSTACK_BASE_URL/api/deploys/<deploy-id>/stream?after=0"

Diagnose in this order:

Read deploy.status, deploy.error, branch, commit, and release fields.
Inspect the last 200 log lines, then find the first fatal build/runtime error.
Check whether the app deploy failed, the machine started but health failed, or the control-plane status is stale.
Compare zstack.yaml source settings with the target repo's deploy files (fly.toml, Dockerfile, package files, migration docs).
For Fly-backed apps, compare API resources with fly status, fly logs, fly machines list, and fly volumes list.

Retry Deploy

Trigger a manual deploy:

curl -sS -b "$ZSTACK_COOKIE" \
  -H 'content-type: application/json' \
  -d '{"branch":"<branch-name>"}' \
  "$ZSTACK_BASE_URL/api/envs/<environment-id>/deploy"

After triggering, stream the returned deploy id until it reaches success or failed.

Relevant API Surface

POST /api/auth/login
GET /api/auth/me
GET /api/workspaces
GET /api/workspaces/:slug
GET /api/envs/:id
POST /api/envs/:id/deploy
POST /api/envs/:id/restart
POST /api/envs/:id/suspend
GET /api/envs/:id/resources
PATCH /api/envs/:id/resources
POST /api/envs/:id/resources/apply
GET /api/envs/:id/domains
POST /api/envs/:id/domains
POST /api/envs/:id/domains/:domainId/check
POST /api/envs/:id/domains/:domainId/apply-dns
POST /api/envs/:id/domains/:domainId/wire
GET /api/envs/:id/telemetry
GET /api/deploys
GET /api/deploys/:id
GET /api/deploys/:id/stream