Cybrix Deploy — Deploy de Sites Estáticos via Claude
cybrixcc/cybrix-skills
Deploy sites estáticos direto do Claude Code para HTTPS live em <60s
Ver no GitHubSkill para Claude Code que automatiza o deploy de sites estáticos em segundos, sem Git, GitHub ou DevOps. Detecta o tipo de projeto, roda o build, envia para a rede edge do Cloudflare e retorna uma URL HTTPS pronta para uso — tudo via conversa no chat.
Instalação
npx convez-ai cybrixcc/cybrix-skills1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Designers e criadores que usam Claude para builds estáticos e precisam publicar rapidamente
- Prototipagem rápida de Next.js, Astro, Vite, Hugo sem infraestrutura
- Deploy de portfolios e landing pages sem configuração DevOps
Veredito

Solução prática para eliminar fricção no deploy de sites estáticos, com UX conversacional zero-config. Ideal para criadores não-técnicos, mas limitado a projetos estáticos e requer account Cybrix (gratuita).
README
A tradução para o português deste README ainda está na fila.
Cybrix — deploy from Claude Code
Tell Claude to deploy. Get a live HTTPS URL in under 60 seconds.
Cybrix is a hosting service for static sites built for coaches, designers, and creators who build with Claude but don't do DevOps. This plugin adds a cybrix-deploy skill to Claude Code — Claude runs the build, packages the output, uploads it to Cloudflare's edge network, and hands you a live URL directly in the chat.
No Git. No GitHub account. No config files. No dashboards. Just talk.
> Deploy this with cybrix
✓ Detected static site (Next.js export)
✓ Building... done in 8s
✓ Uploading to Cybrix... done
✓ Live at: https://my-site.cbrx.cc
Your site is live. Connect a custom domain in dashboard.
Quick start
1. Install the skill — run inside Claude Code:
/plugin marketplace add cybrixcc/cybrix-skills
/plugin install cybrix-deploy@cybrix-skills
2. Get a free API token at app.cybrix.cc — no credit card required.
3. Set your token:
export CYBRIX_TOKEN=vd_your_token_here
To persist across sessions:
mkdir -p ~/.config/cybrix && echo "vd_your_token_here" > ~/.config/cybrix/token
4. Open Claude Code in your project and say:
Deploy this with cybrix
What Claude does
- Detects your project type (Next.js, Astro, Vite, Hugo, Eleventy, plain HTML, and more)
- Scans for environment variables your build needs — asks how to handle each one
- Runs the build and locates the output directory
- Uploads to Cybrix and polls until the site is live
- Returns the live URL directly in the chat
Works in any language — "deploy this", "задеплой это", "despliega esto" — Claude understands the intent.
Supported project types
Static sites only. Detection is heuristic — works with any framework that produces a static output folder.
| Result | Examples |
|---|---|
| [deploy] | Next.js (output: 'export'), Astro, Vite, Hugo, Eleventy, Jekyll, Zola, plain HTML |
| [skip] | Dockerfile present, Node/Go/Python/Ruby server entry points |
Output directories checked in order: dist, out, public, _site, build, .output/public.
Environment variables
Before running the build, Claude scans your project for environment variables the build will need:
- Reads
.env,.env.local,.env.production,.env.example - Greps source files for
process.env.Xandimport.meta.env.Xreferences - Shows you what it found and asks how to handle each:
- Paste here — sent encrypted with the deploy
- Set later — configure in the Cybrix dashboard after deploy
- Skip — build may fail or the site may not work correctly
Claude warns if a variable is used in code but missing from your env files, and refuses to forward anything that looks like a private secret (*_SECRET, *_PRIVATE_KEY, DATABASE_URL) inside a client-bundle prefix (NEXT_PUBLIC_*, VITE_*) without your explicit confirmation.
Token lookup order
The skill looks for your token in this order:
$CYBRIX_TOKENenvironment variable~/.config/cybrix/token.cybrix/tokenin the project root
Pricing
| Plan | Projects | Deploys | Domain | Deploy history | Commercial use |
|---|---|---|---|---|---|
| Free | 1 | Unlimited | *.cbrx.cc | 7 days | [allowed] |
| Pro — $9/mo | 10 | Unlimited | Custom domain | 90 days + rollback | [allowed] |
Both plans allow commercial use. No Fair Use restrictions.
Pro also includes Telegram deploy alerts. → cybrix.cc/pricing
Troubleshooting
Set it with export CYBRIX_TOKEN=vd_... or save to ~/.config/cybrix/token as shown above.
Run your build manually first (npm run build, hugo, etc.) to confirm it works, then retry. If the output path is non-standard, tell Claude the correct path when prompted.
Claude shows the last 40 lines of output. Fix the error (missing node_modules, missing env vars, TypeScript errors) then say "deploy again".
Free plan is limited to 1 project. Upgrade at cybrix.cc/pricing or delete an existing project from your dashboard.
Gzipped output exceeds 100 MB. Common causes: source maps in production output, node_modules accidentally in dist, large unoptimised assets.
Support
- Bug in the skill — open an issue
- Account or deploy problem —
support@cybrix.ccor app.cybrix.cc - Contributing a fix — see CONTRIBUTING.md
License
MIT — see LICENSE.