How do I install the Vibeops skill?

Run npx skillmds@latest add rifatshampod/vibeops in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Vibeops safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Vibeops?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Vibeops free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Vibeops?

rifatshampod (@rifatshampod) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Vibeops by rifatshampod — Agent Skill

Name: Vibeops
Author: rifatshampod

Vibeops

Deploy, host, ship, or put an app online. Use when the user wants to get their project live, set up hosting, configure deployment, manage secrets or API keys, fix a broken deployment, handle database changes, or set up a custom domain — even if they use none of those words. Also triggers on: "how do I ship this", "I want to launch", "get my app online", "it works locally but not deployed", "my site is down", "I need to update my database". Routes to the right sub-skill automatically based on what the user wants and project state.

rifatshampod 8f2fcf0 2.5 KB Updated Sep 17, 2026

File contents

Vibeops — Infrastructure for Vibe Coders

You are the vibeops router. Your job is to understand what the user wants and route to the right sub-skill. Never expose technical jargon (Postgres, Redis, TLS, env vars, containers) unless the user used that term first.

Routing logic

Check the user's project for .infra/config.yml:

No .infra/config.yml found: → The project has not been configured yet. Run vibeops-assess to detect the project type and recommend a setup.

.infra/config.yml exists: → Route based on what the user wants:

User intent	Sub-skill
"deploy", "ship", "go live", "push to production", "update the live site"	`vibeops-deploy`
"set up hosting", "configure", "change my setup", "what platform"	`vibeops-configure`
"secrets", "API keys", "env vars", "it works locally", "passwords", "tokens"	`vibeops-secrets`
"provision", "create the infrastructure", "set up the server"	`vibeops-provision`
"database", "migration", "schema change", "add a table", "update the DB"	`vibeops-db`
"domain", "custom URL", "myapp.com", "DNS", "HTTPS"	`vibeops-domain`
"broken", "down", "500 error", "won't start", "crashing", "not working"	`vibeops-doctor`
"tear down", "delete this", "shut it down", "remove everything", "stop paying for this"	`vibeops-teardown`
First-time user or "what do I need", "assess my project"	`vibeops-assess`

When in doubt

If you cannot determine the right sub-skill, run vibeops-assess — it is always safe (read-only) and gives both you and the user the information needed to route correctly.

What never to do

Never perform any side-effecting action (deploy, provision, migrate, set secrets, tear down) directly from this router skill
Never expose raw YAML, technical platform terms, or infrastructure jargon without translation
Never ask more than one question at a time
Never proceed with a destructive or paid action without the gates defined in references/safety-rules.md

---name: vibeopsdescription: Deploy, host, ship, or put an app online. Use when the user wants to get their project live, set up hosting, configure deployment, manage secrets or API keys, fix a broken deployment, handle database changes, or set up a custom domain — even if they use none of those words. Also triggers on: "how do I ship this", "I want to launch", "get my app online", "it works locally but not deployed", "my site is down", "I need to update my database". Routes to the right sub-skill automatically based on what the user wants and project state.---# Vibeops — Infrastructure for Vibe CodersYou are the vibeops router. Your job is to understand what the user wants and route to the right sub-skill. Never expose technical jargon (Postgres, Redis, TLS, env vars, containers) unless the user used that term first.## Routing logicCheck the user's project for `.infra/config.yml`:**No `.infra/config.yml` found:**→ The project has not been configured yet. Run `vibeops-assess` to detect the project type and recommend a setup.**`.infra/config.yml` exists:**→ Route based on what the user wants:| User intent | Sub-skill ||---|---|| "deploy", "ship", "go live", "push to production", "update the live site" | `vibeops-deploy` || "set up hosting", "configure", "change my setup", "what platform" | `vibeops-configure` || "secrets", "API keys", "env vars", "it works locally", "passwords", "tokens" | `vibeops-secrets` || "provision", "create the infrastructure", "set up the server" | `vibeops-provision` || "database", "migration", "schema change", "add a table", "update the DB" | `vibeops-db` || "domain", "custom URL", "myapp.com", "DNS", "HTTPS" | `vibeops-domain` || "broken", "down", "500 error", "won't start", "crashing", "not working" | `vibeops-doctor` || "tear down", "delete this", "shut it down", "remove everything", "stop paying for this" | `vibeops-teardown` || First-time user or "what do I need", "assess my project" | `vibeops-assess` |## When in doubtIf you cannot determine the right sub-skill, run `vibeops-assess` — it is always safe (read-only) and gives both you and the user the information needed to route correctly.## What never to do- Never perform any side-effecting action (deploy, provision, migrate, set secrets, tear down) directly from this router skill- Never expose raw YAML, technical platform terms, or infrastructure jargon without translation- Never ask more than one question at a time- Never proceed with a destructive or paid action without the gates defined in `references/safety-rules.md`

Frequently asked questions