shipstaticPublish 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 folder, put it online, or get a link others can open. Not for HTML the user only wants to see, download or keep as a file.
Install via ClawdBot CLI:
clawdbot install shipstatic-com/shipstaticGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Accesses sensitive credential files or environment variables
/etc/passwdSends data to undocumented external endpoint (potential exfiltration)
WEBHOOK → https://api.shipstatic.comAccesses system directories or attempts privilege escalation
/var/log/Calls external URL not in known-safe list
https://github.com/shipstatic/shipGenerated Oct 7, 2026
A growth team uses ShipStatic to deploy a statically generated marketing site (Next.js export, Astro, or Hugo) to a custom domain with instant rollbacks. They label each deploy with the release version and link the production domain to the latest deployment.
Developer relations teams publish documentation, changelogs, and API references as static sites under an internal subdomain. Each versioned release is deployed separately and can be swapped instantly for rollback during incidents.
Freelance web designers deploy client websites from a local build folder and reserve custom domains ahead of launch. They validate DNS records with the CLI before handing off the site to the client.
Marketers spin up temporary static landing pages for product launches and events, deploy them with a JSON output to capture the deployment URL, and point a subdomain at the active version.
Data teams export static HTML reports or simple dashboards and host them on a private subdomain. Access is controlled by internal DNS or auth layers added in front of ShipStatic.
ShipStatic offers free internal subdomains (like my-site.shipstatic.com) with instant deploys, and charges for custom domains, higher bandwidth, or team features. The CLI drives adoption by making deployment a one-command operation.
Developers and agencies integrate the ShipStatic CLI into CI/CD pipelines, paying per deployment, stored GB, or request volume. The `--json` output and environment variables make it easy to automate within existing workflows.
Agencies managing multiple client sites use ShipStatic to deploy and rollback sites for clients, with labels and domain linking per project. Team plans include shared access, role management, and higher deployment quotas.
💬 Integration Tip
Set the SHIP_API_KEY environment variable in CI and use `--json` to capture the deployment URL for automated domain linking or notifications; for scripts, validate domains first with `ship domains validate` and always use subdomains, not apex domains.
Scored Oct 27, 2026
AI Analysis
The skill's external API calls (api.shipstatic.com) are consistent with its stated purpose of static hosting deployment and domain management. The credential access is limited to the documented SHIP_API_KEY environment variable for authentication, and there is no evidence of hidden instructions, credential harvesting, or obfuscation.
Audited Apr 18, 2026 · audit v1.0
Use when building UI with shadcn/ui components, Tailwind CSS layouts, form patterns with react-hook-form and zod, theming, dark mode, sidebar layouts, mobile navigation, or any shadcn component question.
Tailwind reference tool. Use when working with tailwind in frontend contexts.
A product creation skill based on the "Bee Website Builder" Open API. It is used to create a new product under a specified site language and product group, w...
A product update skill based on the "Bee Website Builder" Open API. It is used to update an existing product under a specified site language and supports upd...
Build WCAG 2.1 AA compliant websites with semantic HTML, proper ARIA, focus management, and screen reader support. Includes color contrast (4.5:1 text), keyboard navigation, form labels, and live regions. Use when implementing accessible interfaces, fixing screen reader issues, keyboard navigation, or troubleshooting "focus outline missing", "aria-label required", "insufficient contrast".
Use when building Vue 3 applications with Composition API, Nuxt 3, or Quasar. Invoke for Pinia, TypeScript, PWA, Capacitor mobile apps, Vite configuration.