Vibe Deploy
ListedAutomatically deploys code based on sentiment analysis of developer comments, optimizing for positive team morale.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add swan4er/vibe-deploy --skill vibe-deploy -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
swan4er
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 3 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 5 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: api.timeweb.cloud, get.docker.com, getcomposer.org, go.dev, timeweb.cloud.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
get.docker.comundeclaredraw.githubusercontent.comsource hostgo.devundeclaredgetcomposer.orgundeclaredtimeweb.cloudundeclaredapi.github.comsource hostapi.timeweb.cloudundeclaredWhat it found (3 of 5)
- SKILL.md:516contacts get.docker.com
curl -fsSL https://get.docker.com | sh - SKILL.md:548contacts go.dev
wget -q https://go.dev/dl/go${GO_VERSION:-1.23}.0.linux-amd64.tar.gz - SKILL.md:565contacts getcomposer.org
curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer
No credential access: failed
Touches credential material in 16 places.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
What it found (3 of 16)
- SKILL.md:47SSH private keys or config
ssh -i ~/.ssh/timeweb_deploy root@<IP> "cd /opt/app && git pull origin main && docker compose down && docker compose up -d --build" - SKILL.md:52SSH private keys or config
ssh -i ~/.ssh/timeweb_deploy root@<IP> "cd /opt/app && git pull origin main && npm ci --omit=dev && npm run build && pm2 restart app" - SKILL.md:57SSH private keys or config
ssh -i ~/.ssh/timeweb_deploy root@<IP> "cd /opt/app && git pull origin main && source venv/bin/activate && pip install -r requirements.txt && systemctl restart…
No pipe-to-shell installers: failed
Runs code fetched at install time in 4 places.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
What it found (3 of 4)
- SKILL.md:516remote script piped into a shell
curl -fsSL https://get.docker.com | sh - SKILL.md:526remote script piped into a shell
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash - SKILL.md:565remote script piped into an interpreter
curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
Pinned to a commit: passed
Scanned swan4er/vibe-deploy at 8638bebb28.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 8638bebb28
- Manifest
- SKILL.md
- Scanned
- 18 files, 2,844 lines
About this skill
What it does
The vibe-deploy skill allows AI agents to deploy Vibe.js applications, handling tasks like building and pushing code to a designated server. It simplifies the process of getting Vibe.js projects live by automating common deployment steps. This includes compiling assets and transferring files securely.
When to use it
- You're developing a Vibe.js application and need to deploy it quickly.
- You want to automate your Vibe.js deployment workflow, reducing manual effort.
- You’re managing multiple Vibe.js projects and require consistent deployment processes.
- You need to update an existing Vibe.js application on a remote server with minimal downtime.
Key capabilities
- Vibe.js application deployment
- Automated build process
- Secure file transfer
- Server-side code execution
Example prompts
- "Deploy my Vibe.js app to the staging server."
- "Build and push the latest version of my Vibe project."
- “Update the production environment with the changes from the
mainbranch.”
Tips & gotchas
Ensure you have configured the necessary SSH keys or credentials for secure access to your deployment servers before using this skill. The skill's effectiveness depends on a properly structured Vibe.js project and a correctly set up server environment.