Agent skill

Deployment Review

by fossasia in fossasia/eventyay-interpretation

A skill your agent uses to review deployments, validate production readiness, or assist with deployment procedures.

Apache-2.0Auto-check: notesDevOps & Cloud

Install Deployment Review

skills CLI

$ npx skills add fossasia/eventyay-interpretation --skill deployment-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install fossasia/eventyay-interpretation deployment-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/fossasia/eventyay-interpretation.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/deployment-review .claude/skills/deployment-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "deployment-review" agent skill from https://github.com/fossasia/eventyay-interpretation/tree/dev/.agents/skills/deployment-review into .claude/skills/deployment-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-review", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/fossasia/eventyay-interpretation/tree/dev/.agents/skills/deployment-review

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add fossasia/eventyay-interpretation --skill deployment-review -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install fossasia/eventyay-interpretation deployment-review --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/fossasia/eventyay-interpretation.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/deployment-review .agents/skills/deployment-review && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "deployment-review" agent skill from https://github.com/fossasia/eventyay-interpretation/tree/dev/.agents/skills/deployment-review into .agents/skills/deployment-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-review", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add fossasia/eventyay-interpretation --skill deployment-review -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install fossasia/eventyay-interpretation deployment-review --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/fossasia/eventyay-interpretation.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/deployment-review .cursor/skills/deployment-review && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "deployment-review" agent skill from https://github.com/fossasia/eventyay-interpretation/tree/dev/.agents/skills/deployment-review into .cursor/skills/deployment-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-review", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/fossasia/eventyay-interpretation.git --path .agents/skills/deployment-review

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add fossasia/eventyay-interpretation --skill deployment-review -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install fossasia/eventyay-interpretation deployment-review --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/fossasia/eventyay-interpretation.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/deployment-review .gemini/skills/deployment-review && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "deployment-review" agent skill from https://github.com/fossasia/eventyay-interpretation/tree/dev/.agents/skills/deployment-review into .gemini/skills/deployment-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-review", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install fossasia/eventyay-interpretation deployment-review

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add fossasia/eventyay-interpretation --skill deployment-review -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/fossasia/eventyay-interpretation.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/deployment-review .github/skills/deployment-review && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "deployment-review" agent skill from https://github.com/fossasia/eventyay-interpretation/tree/dev/.agents/skills/deployment-review into .github/skills/deployment-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-review", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add fossasia/eventyay-interpretation --skill deployment-review -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install fossasia/eventyay-interpretation deployment-review --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/fossasia/eventyay-interpretation.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/deployment-review .opencode/skills/deployment-review && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "deployment-review" agent skill from https://github.com/fossasia/eventyay-interpretation/tree/dev/.agents/skills/deployment-review into .opencode/skills/deployment-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deployment-review", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: deployment-review
GitHub stars: 1.6k
Token cost: ~1.1k tokens
SKILL.md length: 392 words
Files: 1
Skills in repo: 38
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

A skill your agent uses to review deployments, validate production readiness, or assist with deployment procedures.

Works in 4 steps: Stop portal container: docker-compose… → Revert to previous image/tag or restore… → If DB schema rolled forward: uv run… → …
Review deployments
SKILL.md covers Pre-Deployment Checklist, Startup Sequence, Reverse Proxy (Caddy) and Health Monitoring, plus 4 more sections
Calls uv, node and docker-compose; needs SECRET_KEY and API_KEY_ENCRYPTION_KEY

What it does

Deployment Review is an agent skill from fossasia/eventyay-interpretation. Use this skill to review deployments, validate production readiness, or assist with deployment procedures. Reference: DEPLOYMENTGUIDE.md, docker-compose.yml, Caddyfile, Dockerfile.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Deployment and Containers. It works with Docker. The repository describes itself as: A plugin for live interpretation of video streams. The licence is Apache-2.0.

When your agent uses it

Review deployments
Validate production readiness
Assist with deployment procedures

Example prompts

“/deployment-review”

Requirements

Python 3
Docker
A credential in SECRET_KEY
A credential in API_KEY_ENCRYPTION_KEY

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Stop portal container: docker-compose stop portal
Revert to previous image/tag or restore .:/app source.
If DB schema rolled forward: uv run alembic downgrade -1 (one step back).
Restart: docker-compose up portal -d

What it can do on your machine

Read from SKILL.md and the folder at commit 1ca0139. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- uv
- node
- docker-compose
- uvicorn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- SECRET_KEY
- API_KEY_ENCRYPTION_KEY
- ADMIN_PASSWORD
- JWT_SECRET
- JVB_AUTH_PASSWORD
- JICOFO_AUTH_PASSWORD
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Deployment Review loads about 1.1k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 392 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~52
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:68

Ensure `MEDIAMTX_WHIP_BASE` in `.env` matches the Caddy-exposed HTTPS URL for MediaMTX.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from fossasia/eventyay-interpretation at commit 1ca0139, republished under its Apache-2.0 licence (© fossasia). 392 words, ~1,085 tokens.

Download SKILL.mdSave it as .claude/skills/deployment-review/SKILL.md (or your agent's skills folder).

name: deployment-review
description: Use this skill to review deployments, validate production readiness, or assist with deployment procedures. Reference: `DEPLOYMENT_GUIDE.md`, `docker-compose.yml`, `Caddyfile`, `Dockerfile`.

Skill: Deployment Review

Use this skill to review deployments, validate production readiness, or assist with deployment procedures. Reference: DEPLOYMENT_GUIDE.md, docker-compose.yml, Caddyfile, Dockerfile.

Pre-Deployment Checklist

Code Validation

bash

uv sync --python 3.13 --dev
uv run pytest tests/ -v
node --check static/js/interpreter-booth.js
node --check static/js/whep-listener.js
uv run alembic upgrade head

Environment Variables (must be set in production)

Variable	Requirement
`SECRET_KEY`	32+ char random string — NOT `change-me`
`API_KEY_ENCRYPTION_KEY`	32+ char random string — required if transcription API keys are stored
`ADMIN_PASSWORD`	Set — empty string disables admin login
`JWT_SECRET`	Recommended — otherwise falls back to `SECRET_KEY`
`DATABASE_URL`	`postgresql+asyncpg://user:pass@host/db` for production
`MEDIAMTX_WHIP_BASE`	Browser-reachable HTTPS URL (e.g. `https://media.example.com:8889`)
`JITSI_DOMAIN`	Hostname of self-hosted Jitsi
`JITSI_BASE_URL`	Full HTTPS URL of Jitsi
`DOCKER_HOST_ADDRESS`	Host LAN/public IP for JVB ICE candidates
`JVB_AUTH_PASSWORD`	Change from `changeme`
`JICOFO_AUTH_PASSWORD`	Change from `changeme`

Database

Run uv run alembic upgrade head on first deploy and after any migration PR.
Verify portal-data Docker volume is mounted and persistent.
For PostgreSQL: ensure asyncpg is available (included in SQLAlchemy[asyncio] dependency).

Startup Sequence

1. docker-compose up mediamtx jitsi-* -d
2. docker-compose up portal -d
   → portal container runs: alembic upgrade head && uvicorn ...
3. Verify: curl http://localhost:8000/healthz
   → expected: {"ok": true, "server": "fastapi", "mediamtx_ok": true}
4. Open admin panel: http://localhost:8000/admin/
5. Create event → room → booths → invite tokens
6. Distribute invite links to interpreters

Reverse Proxy (Caddy)

Caddyfile is provided for TLS termination and routing:

Portal: localhost:8000 → HTTPS.
MediaMTX WHIP/WHEP: localhost:8889 → exposed via separate subdomain or path.
Jitsi: localhost:8443 → HTTPS.

Ensure MEDIAMTX_WHIP_BASE in .env matches the Caddy-exposed HTTPS URL for MediaMTX.

Health Monitoring

Endpoint: GET /healthz

json

{"ok": true, "server": "fastapi", "mediamtx_ok": true}

ok: false — FastAPI itself is down.
mediamtx_ok: false — MediaMTX Control API unreachable.

Docker health check: configured in docker-compose.yml for portal service (10s interval).

Rollback Procedure

Stop portal container: docker-compose stop portal
Revert to previous image/tag or restore .:/app source.
If DB schema rolled forward: uv run alembic downgrade -1 (one step back).
Restart: docker-compose up portal -d

Show full SKILL.md (149 more words)Show less

Zero-Downtime Deploy Notes

VoxBento uses in-memory booth state (BoothRegistry). A portal restart:

Drops all active WS connections.
Loses all in-memory participant state (active interpreter, chat history).
Browser clients will reconnect (WebSocket auto-reconnects in interpreter-booth.js).
MediaMTX stream continues unaffected — WHIP/WHEP connections survive portal restart.
Recommend deploying during low-traffic periods (between sessions).

Scaling Notes

Current architecture is single-process (module-level BoothRegistry).
Multiple uvicorn workers (--workers N) would not share booth state — do NOT use.
Horizontal scaling requires Redis-backed booth state (see TD-03 in TECHNICAL_DEBT_REPORT.md).
MediaMTX and Jitsi can be scaled independently.

Post-Deploy Verification

GET /healthz → {ok: true, mediamtx_ok: true}
Admin login at /admin/login.
Create test event + booth + invite token.
Open invite link in browser → redirected to booth page.
Verify Jitsi iframe loads.
Click "Mic Test" → confirm level meter activates.
Click "Go Live" → WHIP connects to MediaMTX.
Open /listener/{event_slug} in second tab → WHEP audio plays.

Files

Just SKILL.md in .agents/skills/deployment-review of fossasia/eventyay-interpretation.

Open the folder on GitHubat commit 1ca0139

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in fossasia/eventyay-interpretation, which our catalogue first saw on October 7, 2026.

fossasia/voxbento.agents/skills/deployment-review

Compare with similar skills

Deployment Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Deployment Review compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Deployment Review this skillfossasia/eventyay-interpretation	1.6k	—	~1.1k	Automated safety check: Notes	Apache-2.0	5 days ago
GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb	6.7k	—	~4k	Automated safety check: Notes	Apache-2.0	today
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit	260	6 repos	~1.1k	Automated safety check: Notes	Custom licence	7 mo ago
LangBot Deployment Guidelangbot-app/LangBot	18k	—	~1.2k	Automated safety check: Notes	Apache-2.0	yesterday
Reflexo ReleaseMyriad-Dreamin/typst.ts	1.2k	—	~1.5k	Automated safety check: Pass	Apache-2.0	2 days ago
Classical Poem Silk VideoMr-funny/hbg-classical-poem-silk-video	361	—	~1.6k	Automated safety check: Pass	MIT	2 mo ago

Similar skills

GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
6.7k GitHub stars~4k tokensUpdated today
DevOps & CloudAuto-check: notes
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
260 GitHub starsUsed in 6 repos~1.1k tokens
DevOps & CloudAuto-check: notes
LangBot Deployment Guide
langbot-app/LangBot
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
18k GitHub stars~1.2k tokensUpdated yesterday
DevOps & CloudAuto-check: notes
Reflexo Release
Myriad-Dreamin/typst.ts
Guide Reflexo/typst.ts release preparation and operator handoffs.
1.2k GitHub stars~1.5k tokensUpdated 2 days ago
DevOps & CloudAuto-check passed
Classical Poem Silk Video
Mr-funny/hbg-classical-poem-silk-video
Turn Chinese classical poems and ci into coherent vertical Chinese-art videos with poem-driven scene grouping, GPT ImageGen stills, Docker-only Gemini I2V, retained model-generated ambience, Gemini…
361 GitHub stars~1.6k tokensUpdated 2 mo ago
DevOps & CloudAuto-check passed
1panel App Builder
arch3rPro/1Panel-Appstore
A skill your agent uses when packaging Docker deployments as 1Panel local app store apps, including GitHub projects, docker-compose.yml files, docker run commands, app metadata, version directories…
214 GitHub stars~1.3k tokensUpdated yesterday
DevOps & CloudAuto-check passed

Questions about Deployment Review

What does Deployment Review do?

A skill your agent uses to review deployments, validate production readiness, or assist with deployment procedures. Deployment Review is an agent skill from fossasia/eventyay-interpretation. Use this skill to review deployments, validate production readiness, or assist with deployment procedures.

When should I use Deployment Review?

Deployment Review fits situations like: review deployments; validate production readiness; assist with deployment procedures.

How do I install Deployment Review in Claude Code?

Run `npx skills add fossasia/eventyay-interpretation --skill deployment-review -a claude-code`. Or copy the skill folder (.agents/skills/deployment-review in fossasia/eventyay-interpretation) into .claude/skills/deployment-review in your project. Claude Code loads it when a task matches its description.

How do I install Deployment Review in Codex?

Run `npx skills add fossasia/eventyay-interpretation --skill deployment-review -a codex`. Or copy the skill folder (.agents/skills/deployment-review in fossasia/eventyay-interpretation) into .agents/skills/deployment-review in your project. Codex loads it when a task matches its description.

Can I use Deployment Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fossasia/eventyay-interpretation --skill deployment-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deployment-review, .gemini/skills/deployment-review, .github/skills/deployment-review and .opencode/skills/deployment-review in your project.

What does Deployment Review need to run?

Going by SKILL.md and its folder, Deployment Review needs the command-line tools its instructions call (uv, node, docker-compose and uvicorn) and credentials named SECRET_KEY, API_KEY_ENCRYPTION_KEY, ADMIN_PASSWORD and JWT_SECRET. Our summary lists: Python 3; Docker; A credential in SECRET_KEY; A credential in API_KEY_ENCRYPTION_KEY.

Does Deployment Review access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Deployment Review safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Deployment Review use?

Deployment Review is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Deployment Review use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Deployment Review?

Skills that share tags, products or a category with Deployment Review: GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars), LangBot Deployment Guide (langbot-app/LangBot, 18k stars) and Reflexo Release (Myriad-Dreamin/typst.ts, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Deployment Review?

fossasia (a GitHub organization) maintains it in fossasia/eventyay-interpretation, which has 1,551 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on October 5, 2026.

Source: fossasia/eventyay-interpretation on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Deployment Review

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Skill: Deployment Review

Pre-Deployment Checklist

Code Validation

Environment Variables (must be set in production)

Database

Startup Sequence

Reverse Proxy (Caddy)

Health Monitoring

Rollback Procedure

Zero-Downtime Deploy Notes

Scaling Notes

Post-Deploy Verification

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from fossasia/eventyay-interpretation

Related

Questions about Deployment Review