Skill environment deployment

Skill zavora-ai/skill-environment-deployment

Environment deployment skill — health checks, promotion, rollback, drift detection

Install

npx -y skills add zavora-ai/skill-environment-deployment

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Manage environments and deployments — inspect environments, run health checks, scale workers, promote releases, rollback, and detect configuration drift. Use when deploying services, checking environment health, scaling workers, promoting between environments, rolling back, or detecting drift.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, 336 tokens by cl100k_base, as published. Nobody here has run it

Environment & Deployment Management

You manage environments safely. Always run health checks before promoting, detect drift proactively, and maintain rollback capability.

Decision Tree

├── "deploy", "promote", "release"? → promote_release (after run_checks)
├── "health", "status", "check"? → inspect_environment / run_checks
├── "scale", "workers", "capacity"? → scale_workers / worker_status
├── "rollback", "revert"? → rollback_release
├── "drift", "out of sync"? → detect_drift / sync_environment
├── "audit", "who deployed"? → audit_trail

Key Workflows

Safe Promotion (3 calls)

run_checks(env: "staging") → verify health
promote_release(from: "staging", to: "production", version: "v2.3.1")
run_checks(env: "production") → verify post-deploy health

Rollback (2 calls)

rollback_release(env: "production", to_version: "v2.3.0")
run_checks(env: "production") → verify rollback succeeded

MUST DO

Run health checks before AND after promotion
Never promote directly to production without staging verification
Maintain rollback capability for every deployment
Detect and resolve drift before promoting

MUST NOT DO

Never deploy without health checks
Don't scale to zero without explicit confirmation
Don't promote with detected drift (resolve first)

What ships with it: 8 files

9.7 KB alongside SKILL.md, 1 of them executable

assets/

environment-status.md794 B

references/

scripts/

deploy_readiness.pyruns699 B

Gives 0 of the 12 instructions most ship operate skills give in 336 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

Document a rollback plan before deploymentin 41 of 779, across 22 files
Update the changelogin 21 of 779, across 19 files
Run the test suitein 20 of 779
Create an annotated git tagin 20 of 779
Clean up feature flags after full rolloutin 18 of 779, across 10 files
Verify deployment health after launchin 18 of 779, across 10 files
Test both feature flag statesin 17 of 779, across 9 files
Verify the working tree is cleanin 17 of 779
Make database migrations backward-compatiblein 16 of 779, across 8 files
Set up error monitoring before launchin 15 of 779, across 7 files
Monitor metrics at each rollout stagein 14 of 779, across 5 files
Create a GitHub releasein 14 of 779

Said here and by no other author read

run health checks before promotion
detect drift before promoting
resolve drift before promoting

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.