Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Performs deployment with pre-flight checks, atomic replacement, post-deploy verification, provenance (proving the environment serves the exact commit you pushed), and automatic rollback.
Install Vibe Safe Deploy
$ npx skills add ash1794/vibe-engineering --skill vibe-safe-deploy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ash1794/vibe-engineering vibe-safe-deploy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-safe-deploy .claude/skills/vibe-safe-deploy && rm -rf skills-srcUse ~/.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/
Install the "vibe-safe-deploy" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-safe-deploy into .claude/skills/vibe-safe-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-safe-deploy", 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 install https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-safe-deployType 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.
$ npx skills add ash1794/vibe-engineering --skill vibe-safe-deploy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ash1794/vibe-engineering vibe-safe-deploy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-safe-deploy .agents/skills/vibe-safe-deploy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibe-safe-deploy" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-safe-deploy into .agents/skills/vibe-safe-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-safe-deploy", 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.
$ npx skills add ash1794/vibe-engineering --skill vibe-safe-deploy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ash1794/vibe-engineering vibe-safe-deploy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-safe-deploy .cursor/skills/vibe-safe-deploy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vibe-safe-deploy" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-safe-deploy into .cursor/skills/vibe-safe-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-safe-deploy", 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 https://github.com/ash1794/vibe-engineering.git --path plugins/vibe-engineering/skills/vibe-safe-deploy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ash1794/vibe-engineering --skill vibe-safe-deploy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ash1794/vibe-engineering vibe-safe-deploy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-safe-deploy .gemini/skills/vibe-safe-deploy && rm -rf skills-srcUse ~/.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/
Install the "vibe-safe-deploy" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-safe-deploy into .gemini/skills/vibe-safe-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-safe-deploy", 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.
$ gh skill install ash1794/vibe-engineering vibe-safe-deployInstalls 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).
$ npx skills add ash1794/vibe-engineering --skill vibe-safe-deploy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-safe-deploy .github/skills/vibe-safe-deploy && rm -rf skills-srcUse ~/.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/
Install the "vibe-safe-deploy" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-safe-deploy into .github/skills/vibe-safe-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-safe-deploy", 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.
$ npx skills add ash1794/vibe-engineering --skill vibe-safe-deploy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ash1794/vibe-engineering vibe-safe-deploy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-safe-deploy .opencode/skills/vibe-safe-deploy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vibe-safe-deploy" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-safe-deploy into .opencode/skills/vibe-safe-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-safe-deploy", 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
vibe-safe-deploy- GitHub stars
- 163
- Token cost
- ~730 tokens
- SKILL.md length
- 283 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
Performs deployment with pre-flight checks, atomic replacement, post-deploy verification, provenance (proving the environment serves the exact commit you pushed), and automatic rollback.
- Works in 7 steps: Pre-flight checks — Run all items in… → Backup current state → Deploy using atomic operations → …
- Tasks that involve Deployment
- SKILL.md covers When to Use This Skill, When NOT to Use This Skill, Pre-Flight Checklist and Steps, plus 1 more section
- Needs API_KEY
What it does
Vibe Safe Deploy is an agent skill from ash1794/vibe-engineering. Performs deployment with pre-flight checks, atomic replacement, post-deploy verification, provenance (proving the environment serves the exact commit you pushed), and automatic rollback. Use before any deployment to staging, preview, or production.
Its SKILL.md is about 730 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. The repository describes itself as: 33 engineering discipline skills for Claude Code, OpenAI Codex & Gemini CLI + a CLI for CI/CD enforcement. Extracted from real-world multi-agent system development. Born from… The licence is MIT.
When your agent uses it
- Tasks that involve Deployment
Example prompts
- “Use the vibe-safe-deploy skill to perform deployment with pre-flight checks, atomic replacement, post-deploy verification, provenance (proving the…”
- “/vibe-safe-deploy”
Requirements
- Docker
- A credential in API_KEY
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Pre-flight checks — Run all items in checklist. Stop if any fail.
- Backup current state
- Deploy using atomic operations
- Health check (within 60s timeout)
- If health check fails → automatic rollback
- Verify provenance. "Deploy succeeded" means a job finished, not that the new build is being served.
- Report status: success / failed / rolled-back
What it can do on your machine
Read from SKILL.md and the folder at commit 8f1d71b. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vibe Safe Deploy loads about 730 tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 283 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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 ash1794/vibe-engineering at commit 8f1d71b, republished under its MIT licence (© ash1794). 283 words, ~730 tokens.
Download SKILL.mdSave it as
.claude/skills/vibe-safe-deploy/SKILL.md (or your agent's skills folder).- name
- vibe-safe-deploy
- description
- Performs deployment with pre-flight checks, atomic replacement, post-deploy verification, provenance (proving the environment serves the exact commit you pushed), and automatic rollback. Use before any deployment to staging, preview, or production.
- user-invocable
- true
vibe-safe-deploy
Ship with confidence. Every deployment should be verifiable and reversible.
When to Use This Skill
- Deploying to staging or production environments
- Releasing a new version
- Deploying infrastructure changes
When NOT to Use This Skill
- Local development builds
- CI/CD that already handles these checks
- Deploying documentation (low risk)
Pre-Flight Checklist
Before deploying, verify:
- All tests pass (including integration tests)
- Linting is clean
- No uncommitted changes in working tree
- No secrets in the diff (
grep -r 'API_KEY\|SECRET\|PASSWORD') - Build succeeds
- Database migrations are reversible (if applicable)
Steps
Pre-flight checks — Run all items in checklist. Stop if any fail.
Backup current state:
bash cp -r current_deploy/ current_deploy.prev/ # or: docker tag app:current app:rollbackDeploy using atomic operations:
bash # Use 'install' not 'cp' for atomic file replacement install -m 755 new_binary /path/to/binary # or: docker tag app:new app:current && docker-compose up -dHealth check (within 60s timeout):
- Service starts successfully
- Health endpoint returns 200
- Key functionality works (smoke test)
- No error spikes in logs
If health check fails → automatic rollback:
bash cp -r current_deploy.prev/ current_deploy/ # Restart services with previous versionVerify provenance. "Deploy succeeded" means a job finished, not that the new build is being served.
- Bake the commit SHA into the build or image and serve it at a version endpoint (for example
/version.txt) - After deploy, poll that endpoint until it returns the expected SHA; on timeout, fail and report the SHA it actually served
- Keep environments separate: branch pushes deploy preview (behind auth,
noindex), and only the main branch deploys production - Give the deploy credential the least privilege that works (for example a forced-command SSH key that accepts only
<environment> <sha>)
- Bake the commit SHA into the build or image and serve it at a version endpoint (for example
Report status: success / failed / rolled-back
Output Format
Deployment Report
Status: SUCCESS / FAILED / ROLLED_BACK Version: [version or commit hash] · Served SHA: [value from version endpoint] Duration: [time]
| Step | Status | Duration |
|---|---|---|
| Pre-flight | ✓ | 5s |
| Backup | ✓ | 2s |
| Deploy | ✓ | 10s |
| Health check | ✓ | 15s |
Post-Deploy Verification
- Service running: ✓
- Health endpoint: 200 OK
- Log errors: 0 in last 60s
© ash1794, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/vibe-engineering/skills/vibe-safe-deploy of ash1794/vibe-engineering.
Open the folder on GitHubat commit 8f1d71b
Compare with similar skills
Vibe Safe Deploy 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vibe Safe Deploy this skillash1794/vibe-engineering | 163 | — | ~730 | Automated safety check: Pass | MIT | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Vercelremotion-dev/remotion | 63k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT |
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.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
- Official
Vercel
remotion-dev/remotion
Set up a Codex monitor for Vercel deployments and preview URLs.
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
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…
More from ash1794/vibe-engineering
All 33 skills in this repoVibe Concurrent Test Safety
ash1794/vibe-engineering
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.
Vibe Fuzz Parser Inputs
ash1794/vibe-engineering
Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input).
Vibe Golden File Testing
ash1794/vibe-engineering
Implements snapshot/golden file tests with temporal normalization so tests don't break daily.
Vibe Parallel Task Decomposition
ash1794/vibe-engineering
Analyzes large tasks for independent subtasks that can be safely parallelized.
Vibe Slop Filter
ash1794/vibe-engineering
Strips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails).
Vibe Spec Sync
ash1794/vibe-engineering
Keeps specification documents and code in agreement. An agent skill from ash1794/vibe-engineering.
Related
Categories
Questions about Vibe Safe Deploy
What does Vibe Safe Deploy do?
Performs deployment with pre-flight checks, atomic replacement, post-deploy verification, provenance (proving the environment serves the exact commit you pushed), and automatic rollback. Vibe Safe Deploy is an agent skill from ash1794/vibe-engineering. Performs deployment with pre-flight checks, atomic replacement, post-deploy verification, provenance (proving the environment serves the exact commit you pushed), and automatic rollback.
When should I use Vibe Safe Deploy?
Vibe Safe Deploy fits situations like: tasks that involve Deployment.
How do I install Vibe Safe Deploy in Claude Code?
Run `npx skills add ash1794/vibe-engineering --skill vibe-safe-deploy -a claude-code`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-safe-deploy in ash1794/vibe-engineering) into .claude/skills/vibe-safe-deploy in your project. Claude Code loads it when a task matches its description.
How do I install Vibe Safe Deploy in Codex?
Run `npx skills add ash1794/vibe-engineering --skill vibe-safe-deploy -a codex`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-safe-deploy in ash1794/vibe-engineering) into .agents/skills/vibe-safe-deploy in your project. Codex loads it when a task matches its description.
Can I use Vibe Safe Deploy 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 ash1794/vibe-engineering --skill vibe-safe-deploy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-safe-deploy, .gemini/skills/vibe-safe-deploy, .github/skills/vibe-safe-deploy and .opencode/skills/vibe-safe-deploy in your project.
What does Vibe Safe Deploy need to run?
Going by SKILL.md and its folder, Vibe Safe Deploy needs credentials named API_KEY. Our summary lists: Docker; A credential in API_KEY.
Does Vibe Safe Deploy access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Vibe Safe Deploy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vibe Safe Deploy use?
Vibe Safe Deploy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vibe Safe Deploy use?
About 730 tokens (SKILL.md is roughly 2.9k 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 Vibe Safe Deploy?
Skills that share tags, products or a category with Vibe Safe Deploy: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars) and Vercel (remotion-dev/remotion, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vibe Safe Deploy?
ash1794 (a GitHub user) maintains it in ash1794/vibe-engineering, which has 163 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.
Source: ash1794/vibe-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.