cybrix-deploy — Claude Code plugin: ship static sites to a live URL
Builds a static site, uploads it to Cybrix hosting and hands back a live HTTPS address in the chat. No Git, no dashboards.
/plugin marketplace add anthropics/claude-plugins-community
/plugin install cybrix-deploy@claude-communityWhat cybrix-deploy does
The skill works out what kind of project it is looking at: Next.js with output: 'export', Astro, Vite, Hugo, Eleventy, Jekyll, Zola or plain HTML. Then it runs the build, locates the output folder among dist, out, public, _site, build and .output/public, and pushes the files to Cloudflare's edge. You get a link like https://my-site.cbrx.cc. The author promises the whole trip takes under 60 seconds.
Environment variables get scanned before any build runs. The skill opens .env, .env.local, .env.production and .env.example, then searches sources for process.env.X and import.meta.env.X. For each hit it asks what to do: send the value encrypted along with the deploy, set it later in the dashboard, or skip it. Names that smell like secrets (*_SECRET, *_PRIVATE_KEY, DATABASE_URL) sitting behind a client-side prefix such as NEXT_PUBLIC_* or VITE_* are blocked unless you confirm out loud.
An access token has to exist first. Grab a free one at app.cybrix.cc (no card asked for) and keep it in CYBRIX_TOKEN, ~/.config/cybrix/token or .cybrix/token at the project root — the skill tries those three spots in that order. Projects shipping a Dockerfile or a Node, Go, Python, Ruby server entry point are refused, since only static output is accepted. The free plan covers one project on a *.cbrx.cc address, and the gzipped bundle has to stay under 100 MB.
What it helps with
- put a finished static build on the internet behind HTTPS
- see which environment variables the build needs and decide what to do with each
- find the output folder when a framework puts it somewhere unusual
- catch a secret that leaked into a client bundle before it leaves your machine
- deploy a Next.js, Astro or Hugo site without Git or manual uploads
Example prompts for the agent
- Deploy this with cybrix
- Build the site and push it to cybrix, the token is in
CYBRIX_TOKEN - Check the environment variables, then deploy with cybrix
How to install cybrix-deploy
Plugin marketplace
/plugin marketplace add anthropics/claude-plugins-community/plugin install cybrix-deploy@claude-communityStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about cybrix-deploy
How do I install cybrix-deploy in Claude Code?
Add the marketplace with /plugin marketplace add anthropics/claude-plugins-community, then install the plugin: /plugin install cybrix-deploy@claude-community.
What does cybrix-deploy do?
It runs your static build, uploads the result to Cybrix and returns a live *.cbrx.cc link right in the chat. You stay out of any dashboard.
Do I need a Cybrix token, and where do I get one?
Yes, deploys fail without it. Get a free token at app.cybrix.cc and store it in CYBRIX_TOKEN, ~/.config/cybrix/token or .cybrix/token at the project root.
Source text
cybrix-deploy · MIT
# Cybrix — deploy from Claude Code [](https://github.com/cybrixcc/cybrix-skills/blob/master/plugins/cybrix-deploy/.claude-plugin/plugin.json) [](./LICENSE) [](https://claude.ai/code) [](https://cybrix.cc) **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](https://claude.ai/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](https://app.cybrix.cc) — no credit card required. **3. Set your token:** ```bash export CYBRIX_TOKEN=vd_your_token_here ``` To persist across sessions: ```bash 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 1. Detects your project type (Next.js, Astro, Vite, Hugo, Eleventy, plain HTML, and more) 2. Scans for environment variables your build needs — asks how to handle each one 3. Runs the build and locates the output directory 4. Uploads to Cybrix and polls until the site is live 5. 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.X` and `import.meta.env.X` references - 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: 1. `$CYBRIX_TOKEN` environment variable 2. `~/.config/cybrix/token` 3. `.cybrix/token` in 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](https://cybrix.cc/pricing) --- ## Troubleshooting <details> <summary><strong>"CYBRIX_TOKEN is not set"</strong></summary> Set it with `export CYBRIX_TOKEN=vd_...` or save to `~/.config/cybrix/token` as shown above. </details> <details> <summary><strong>"Output directory not found"</strong></summary> 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. </details> <details> <summary><strong>"Build failed"</strong></summary> Claude shows the last 40 lines of output. Fix the error (missing `node_modules`, missing env vars, TypeScript errors) then say "deploy again". </details> <details> <summary><strong>"Free tier project limit reached"</strong></summary> Free plan is limited to 1 project. Upgrade at [cybrix.cc/pricing](https://cybrix.cc/pricing) or delete an existing project from your [dashboard](https://app.cybrix.cc/dashboard). </details> <details> <summary><strong>"Bundle too large"</strong></summary> Gzipped output exceeds 100 MB. Common causes: source maps in production output, `node_modules` accidentally in `dist`, large unoptimised assets. </details> --- ## Support - Bug in the skill — [open an issue](https://github.com/cybrixcc/cybrix-skills/issues) - Account or deploy problem — `[email protected]` or [app.cybrix.cc](https://app.cybrix.cc) - Contributing a fix — see [CONTRIBUTING.md](./CONTRIBUTING.md) --- ## License MIT — see [LICENSE](./LICENSE).
© cybrixcc · MIT · cybrixcc/cybrix-skills
