skills/deploy/SKILL.md
Deploy the atproto-agent-network project. Two separate Cloudflare Workers must be deployed independently — the network worker (API + agents) and the dashboard worker (highswarm.com). Use when deploying changes, fixing the dashboard, or updating agent configs.
npx skillsauth add joelhooks/atproto-agent-network atproto-deployInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This project has two independent Cloudflare Workers. Deploying one does NOT deploy the other.
| Worker | Location | URL | Serves |
|--------|----------|-----|--------|
| network | apps/network/ | agent-network.joelhooks.workers.dev | API, Agent DOs, Relay, WebSocket |
| dashboard | packages/dashboard/ | highswarm.com (highswarm.joelhooks.workers.dev) | Static dashboard SPA |
# Get CF token
export CLOUDFLARE_API_TOKEN=$(secrets lease "atproto-agents::cloudflare_api_key" --raw --ttl 10m --client-id "deploy")
# Deploy network worker (API + agents)
cd apps/network && npx wrangler deploy
# Deploy dashboard (MUST rebuild Vite first!)
cd packages/dashboard && npx vite build && npx wrangler deploy
export CLOUDFLARE_API_TOKEN=$(secrets lease "atproto-agents::cloudflare_api_key" --raw --ttl 10m --client-id "deploy")
# Network
cd apps/network && npx wrangler deploy
# Dashboard — rebuild + deploy
cd ../../packages/dashboard && npx vite build && npx wrangler deploy
When changes are only in packages/dashboard/:
export CLOUDFLARE_API_TOKEN=$(secrets lease "atproto-agents::cloudflare_api_key" --raw --ttl 10m --client-id "deploy-dashboard")
cd packages/dashboard && npx vite build && npx wrangler deploy
# Check the JS bundle hash changed
curl -s https://highswarm.com | grep -o 'index-[A-Za-z0-9]*\.js'
When changes are only in apps/network/, packages/agent/, or packages/core/:
export CLOUDFLARE_API_TOKEN=$(secrets lease "atproto-agents::cloudflare_api_key" --raw --ttl 10m --client-id "deploy-network")
cd apps/network && npx wrangler deploy
# From repo root — always run before deploying
npx turbo typecheck # Type check all packages
npx vitest run # Run tests (1 flaky Catan test is known)
Secrets are namespaced under atproto-agents:: in agent-secrets:
cloudflare_api_key — CF API token for wranglercloudflare_account_id — CF account IDopenrouter_api_key — OpenRouter API key (set as CF worker secret)Worker secrets (set via wrangler secret put):
ADMIN_TOKEN — Admin auth tokenOPENROUTER_API_KEY — For AI GatewayCF_ACCOUNT_ID — For AI Gateway URL constructionGRIMLOCK_GITHUB_TOKEN — For publish tool (GitHub Contents API)Agent model/config changes don't need a deploy — use the API:
ADMIN_TOKEN="grimlock-admin-f5f3ef8419386713454c05b8d475cce1"
BASE="https://agent-network.joelhooks.workers.dev"
# Change agent model
curl -s -X PATCH "$BASE/agents/scout/config" \
-H "Authorization: Bearer $ADMIN_TOKEN" \
-H "Content-Type: application/json" \
-d '{"model": "google/gemini-3-flash-preview"}'
# Stop/start agent loop
curl -s -X POST "$BASE/agents/scout/loop/stop" -H "Authorization: Bearer $ADMIN_TOKEN"
curl -s -X POST "$BASE/agents/scout/loop/start" -H "Authorization: Bearer $ADMIN_TOKEN"
packages/dashboard/dist/ is gitignored. Vite must rebuild before wrangler deploy or you ship stale code.google/gemini-3-flash-preview, NOT google/gemini-3-flash). Check https://openrouter.ai/models for valid IDs.max-age=60. Users may need a hard refresh. Verify with curl -s https://highswarm.com | grep index-.development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.