deploy
/deploy
Build Keryx and redeploy it to the user's Hermes host (rsync to /opt/keryx, rebuild the keryx container, verify /api/health). Use when the user says "redeploy", "deploy", or "merge and redeploy" after the merge is done.
Assessment and security
- Files in this package
- 2
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 03.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: deploy.sh
What it does and when to use it
Build Keryx and redeploy it to the user's Hermes host (rsync to /opt/keryx, rebuild the keryx container, verify /api/health). Use when the user says "redeploy", "deploy", or "merge and redeploy" after the merge is done.
Triggers from the description
Original author description
Build Keryx and redeploy it to the user's Hermes host (rsync to /opt/keryx, rebuild the keryx container, verify /api/health). Use when the user says "redeploy", "deploy", or "merge and redeploy" after the merge is done.
How it works
- Preconditions
- Run
- Report
SKILL.md preview
--- name: deploy description: Build Keryx and redeploy it to the user's Hermes host (rsync to /opt/keryx, rebuild the keryx container, verify /api/health). Use when the user says "redeploy", "deploy", or "merge and redeploy" after the merge is done. --- # Deploy Production is the Hermes host `root@192.168.1.100`. Keryx lives flat in `/opt/keryx` and is built by the Hermes compose project in `/opt/hermes` (`docker compose up -d --build keryx`). ## Preconditions - Be on `main` with the merged changes pulled (`git pull --ff-only`). Deploying a branch is wrong unless the user explicitly asks for it. - `.claude/skills/check/check.sh` passed, or at least `npm run build` just ran, because the container copies `backend/static`. ## Run ```bash .claude/skills/deploy/deploy.sh ``` The script: 1. Reads the expected version from `backend/app.py`. 2. Builds the front end. 3. Rsyncs `backend/` to `/opt/keryx` (deleting removed files, excluding `.venv`, caches, tests, logs). 4. Rebuilds and restarts the `keryx` service. 5. Polls `/api/health` on the host until it answers, then checks the reported version matches. Override `KERYX_HOST`, `KERYX_REMOTE_DIR` or `KERYX_COMPOSE_DIR` in the environment if the host layout changes. The script never touches Hermes' data directory. ## Report State the version reported by health, and whether it is a parity rebuild (no app change since the last deploy) or a real update. If health never answers, show the container logs: ```bash ssh root@192.168.1.100 'docker logs --tail 50 keryx' ```
Files in this package (2)
- SKILL.md 2 KB
- deploy.sh 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · rafreid/keryx | 100 | MIT |
| zeitlos/lucity | 100 | AGPL-3.0 |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| zeitlos/lucity | 100 | AGPL-3.0 |
| microsoft/power-platform-skills | 100 | MIT |
| friendlyinternet/nuxt-crouton | 100 | MIT |
| wraith-proxy/wraith-skills | 100 | MIT |
| jikig-ai/soleur | 100 | Apache-2.0 |
| curiositech/windags-skills | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version e23681aeffe4 (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
- 95demo-data
Build a synthetic Hermes data directory and run a Keryx dev server against it on port 9121 for browser checks and screenshots. Use whenever Keryx must be seen running locally, never against real Hermes data. - 100stacked-prs
Open and merge Keryx's stacked pull requests in order with gh (retarget each to main, merge-commit, keep branches). Use when building a multi-PR feature stack or when the user says "merge all in order". - 100bdb-deploy
Use when the user wants to build and deploy a project to a real server via rsync over SSH — "deploy this", "push the build live", "sync to production". Not for git push/PR workflows, and not a replacement for a real CI pipeline; this is the direct-deploy path. - 100deploy-mcp
Deploy the FutureSearch MCP server to staging or production on GKE. Use when the user wants to deploy, redeploy, roll back, scale replicas, or check deployment status. Triggers on deploy, redeploy, staging, production, rollout, scale, replicas. - 100rsync
rsync copies and synchronizes files locally or over SSH, sending only the parts that changed. Use when someone asks to "copy files to a server", "sync two directories", "mirror a folder", "make incremental backups with hard links", "deploy a build to a remote host", "resume a… - 100pb-deploy-saas
Deploy a SaaS app to the BDB fleet: preflight of the fleet skills, a guardrail plan, green CI, the deploy after GO (Incus via Forgejo CI, or direct rsync), and a health URL check. Use for "deploy this to the fleet", "deploy the SaaS app", "ship to the Incus instance".