Skip to content
Skills Library
DevOps & cloud · Automation

deploy

/deploy

Deploy / publish a single HTML file (deck, page, doc) to FluidDocs hosting using the self-contained scripts/deploy.sh. Handles browser sign-in / re-auth automatically, then opens the live URL in the browser. Trigger on "deploy", "publish", "ship it", "push it live", "put it online", "host this", or any request to make an HTML file publicly viewable.

Licence
MIT
Last repository change
09.06.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 09.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Deploy / publish a single HTML file (deck, page, doc) to FluidDocs hosting using the self-contained scripts/deploy.sh. Handles browser sign-in / re-auth automatically, then opens the live URL in the browser. Trigger on "deploy", "publish", "ship it", "push it live", "put it online", "host this", or any request to make an HTML file publicly viewable.

Triggers from the description

deploypublishship itpush it liveput it onlinehost this
Original author description

Deploy / publish a single HTML file (deck, page, doc) to FluidDocs hosting using the self-contained scripts/deploy.sh. Handles browser sign-in / re-auth automatically, then opens the live URL in the browser. Trigger on "deploy", "publish", "ship it", "push it live", "put it online", "host this", or any request to make an HTML file publicly viewable.

How it works

  1. What the script does (so you don't have to analyze it)
  2. Procedure
  3. Re-auth
  4. Hard rules
Original SKILL.md headings · 59 lines, 702 words
SKILL.md preview
---
name: deploy
description: Deploy / publish a single HTML file (deck, page, doc) to FluidDocs hosting using the self-contained scripts/deploy.sh. Handles browser sign-in / re-auth automatically, then opens the live URL in the browser. Trigger on "deploy", "publish", "ship it", "push it live", "put it online", "host this", or any request to make an HTML file publicly viewable.
---

# Deploy

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.

## What the script does (so you don't have to analyze it)

- Finds HTML files in the **current directory only** (`find . -maxdepth 1`). So you must run it from the folder that contains the target file.
- If exactly one HTML file is present, it auto-selects it. If several, it prompts for a number.
- Caches an auth token at `~/.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.
- Uploads the file and prints `  ✓ Deployed → <URL>` on success.
- Records the file→project mapping in `./.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.
- Flags you use: `--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.

## Procedure

1. **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.

2. **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"`).

3. **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
   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.

4. **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"
   ```

5. **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:

   ```bash
   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.

## Re-auth

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.

## Hard rules

- Never deploy without `--name`.
- Run from the file's own directory (the script is directory-scoped).
- Preserve `./.fluid-docs.json`. It's what keeps re-deploys updating the same project.
- A plain deploy is private: the returned link is an owner-only preview that only the signed-in owner can open. Do not call it shareable, and do not offer to make it public. Visibility (private, unlisted, public) and publishing are ALWAYS the user's choice, set by them in the FluidDocs app via Publish / Share or Document Properties. Never run `--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`.
- The user asking to "deploy/publish" is the authorization; don't deploy a file they didn't ask for.

---

*Maintained by [FluidDocs](https://fluiddocs.ai). Source: https://github.com/FluidForm-ai/fluiddocs-deck-builder. MIT licensed.*

Versions

RepositoryScoreLicence
This page · fluidform-ai/fluiddocs-deck-builder100MIT
zeitlos/lucity100AGPL-3.0
jeremylongshore/tons-of-skills-marketplace100MIT
zeitlos/lucity100AGPL-3.0
microsoft/power-platform-skills100MIT
friendlyinternet/nuxt-crouton100MIT
wraith-proxy/wraith-skills100MIT
jikig-ai/soleur100Apache-2.0
curiositech/windags-skills100Apache-2.0

Database snapshot: 13.11.2026 · package version 7b34a309ef7d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100share-html
    Publish a local HTML file or static site directory to a configured local share server and return a browser-viewable URL. Use when the user wants to open coding-agent output in a browser on the same machine or another device over a private tailnet.
  • 100host
    Upload files to Cloudflare R2 and return a shareable public URL. Supports any file type (HTML, images, PDFs, etc.) with automatic slug generation, clipboard copy, and hosting history tracking. Use when the user says "host", "host this", "host file", "publish", "publish this",…
  • 100publish-online
    Publish a site, page, report, dashboard, slide deck, document, portfolio or small web app at a ShipStatic link anyone can open, with no account needed and optional built-in password protection. Use when the user asks to publish something, deploy or host a static site or a build…
  • 100publish-to-pages
    Publish presentations and web content to GitHub Pages. Converts PPTX, PDF, HTML, or Google Slides to a live GitHub Pages URL. Handles repo creation, file conversion, Pages enablement, and returns the live URL. Use when the user wants to publish, deploy, or share a presentation…
  • 100pagepin
    Deploy an HTML page, Markdown file, image, or multi-file static site to a pagepin host and get a shareable URL — pagepin renders Markdown and images in a viewer — then run the pin-point review-comment loop (read comments, fix, redeploy, resolve). Use when the user wants to…
  • 100do-deploy
    Deploy popoto: run tests, bump version, tag release, publish to PyPI, deploy docs. Triggered by 'deploy', 'do-deploy', or any request to publish a new version.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.