Skill environment deployment
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.From its SKILL.md
npx -y skills add zavora-ai/skill-environment-deploymentAssembled 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 file declares
Copied from the file, not written here
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 healthpromote_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/
references/
- cross-mcp-workflows.md822 B
- examples.md2.0 KB
- tool-sequences.md2.3 KB
scripts/
- deploy_readiness.pyruns699 B
- .gitignore29 B
- LICENSE738 B
- README.md2.4 KB