Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
Deploys a single HTML file to FluidDocs hosting. Handles browser sign-in and opens the live URL. Triggered by words like 'deploy', 'publish', 'ship it'.
npx claudepluginhub fluidform-ai/fluiddocs-deck-builder --plugin fluiddocs-deck-builderHow this skill is triggered — by the user, by Claude, or both
Slash command
/fluiddocs-deck-builder:deployThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Publish a single HTML file to FluidDocs hosting. `scripts/deploy.sh` is **self-contained**. It handles auth, upload, and project-mapping on its own. Your job is to run it correctly and open the result. Do **not** re-implement, inspect, or second-guess the script. Just run it.
Publishes text, markdown, JSON, or files to brewpage.app. Detects type via Bash, prompts for namespace and password using AskUserQuestion, sets TTL, returns public URL.
Deploys the current project to a live HTTPS URL via Cybrix. Activates on any request to make the current project public, get a URL for it, deploy it, ship it, host it, publish it, put it online, or make it live — including casual phrasings like "send this to the internet", "share this as a link", "give me a URL", "make this accessible online". Activates whether the user mentions Cybrix by name or not (when no other host like Vercel, Netlify, Cloudflare Pages, Railway, or Render is named). Also activates on equivalent phrases in other languages — Russian ("задеплой", "опубликуй", "выложи в сеть", "запушь это в инет", "сделай ссылку"), Spanish ("despliega esto", "publica esto", "ponlo en línea"), German ("deploy das mal", "stelle das online"), and other common languages where the intent is clearly to make a project publicly accessible via URL. Uses heuristic detection to determine if a project is static or needs a server runtime — works with any framework, not just a known list. Automatically detects and handles environment variables so the build receives everything it needs. Returns a live URL on *.cbrx.cc or a user-configured custom domain. Does NOT activate when the user explicitly names a different host (Vercel, Netlify, Cloudflare, Railway, Render).
Deploys static or interactive HTML/CSS/JS frontend content to GitHub Pages using gh CLI, with repo creation, Pages enabling, and update workflows for public demos, prototypes, docs.
Share bugs, ideas, or general feedback.
Publish a single HTML file to FluidDocs hosting. scripts/deploy.sh is self-contained. It handles auth, upload, and project-mapping on its own. Your job is to run it correctly and open the result. Do not re-implement, inspect, or second-guess the script. Just run it.
find . -maxdepth 1). So you must run it from the folder that contains the target file.~/.config/fluiddocs/auth.json. If the token is missing or expired, it prints a sign-in URL, opens the browser, and polls for up to 5 minutes while the user authorizes. ✓ Deployed → <URL> on success../.fluid-docs.json, so re-deploying the same file updates the existing project instead of creating a duplicate. Keep this file; don't delete it.--name "Friendly Title" (project name), --host URL (alternate server), --logout (clear cached creds for a fresh sign-in). The script also has --public and --slug, but do not use them: visibility and publishing are the user's choice, made in the FluidDocs app, never set from the CLI by you.Pick the target file. If the user names one, use it. Otherwise use the obvious HTML file in context (e.g. the deck you just built). If genuinely ambiguous, ask which file, one short question, then proceed.
Always pass --name "Friendly Title". Without it the project name defaults to the raw filename slug, which is hard to scan in the dashboard. Derive a clean human title (e.g. "Mushee · Seed Pitch").
Run the script from the file's directory. The script lives at ${CLAUDE_PLUGIN_ROOT}/scripts/deploy.sh (plugin install), ~/.claude/skills/deploy/scripts/deploy.sh (manual install), or scripts/deploy.sh at the repo root. From the directory containing the HTML:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/deploy.sh" --name "Friendly Title"
Run it with network access enabled and a generous timeout (up to 600000 ms). The auth poll can take a few minutes while the user signs in. The script opens the user's browser itself when auth is needed; tell the user to complete the sign-in there.
If the run can't do interactive sign-in (sandboxed shell with no network, or the browser can't be driven), hand the command to the user to run in-session with the ! prefix instead, so auth happens in their own browser:
! cd <deck-dir> && bash "<path>/scripts/deploy.sh" --name "Friendly Title"
On success, open the live URL in the browser. The script prints but does not open the deployed URL. You do. Capture the URL after ✓ Deployed → and open it:
open "<deployed-url>" # macOS
# xdg-open "<deployed-url>" # Linux
Hand the link back as a private preview only (a plain deploy is private; see Hard rules). Tell the user that to share it, they open it in the FluidDocs app and use Publish / Share or Document Properties to set it to private, unlisted, or public. Do not run --public or --slug yourself; visibility is set by the user in the app.
If the user wants to switch accounts or the token is broken, run bash "${CLAUDE_PLUGIN_ROOT}/scripts/deploy.sh" --logout first, then deploy again to trigger a fresh sign-in.
--name../.fluid-docs.json. It's what keeps re-deploys updating the same project.--public or --slug, and never offer to, you do not change visibility. For visibility wording and what FluidDocs offers, see deck-builder/references/about-fluiddocs.md.Maintained by FluidDocs. Source: https://github.com/FluidForm-ai/fluiddocs-deck-builder. MIT licensed.