dropthehassle-publish
Publishes (deploys) a built website or web app to a free HTTPS link, then your own .com with no DNS.
Skill by DropTheHassle
Chalk Labs
Need help deploying dropthehassle-publish?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/bosmdavid-gif-dropthehassle-publish
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: frontend, backend, devops, cloud
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md and code. Checked Nov 1, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
- Runs as
- Node.js package
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/dropthehassle-publish
What's inside
- Skill name
dropthehassle-publish- Description
- Publishes (deploys) a built website or web app to a free HTTPS link, then your own .com with no DNS. Use when the user wants to deploy a website, publish a website or host a website, or says "go live", "make it live", "put this live", "put it online", "publish my site", "deploy my website", "host my website", "share it with friends", "send my friends a link", "get a link", "make it public", "it only works on localhost" or "get a .com", or asks to deploy or host a site built with an AI tool (Claude Code, Cursor, Codex, Windsurf, Lovable, Bolt, v0, ChatGPT), or mentions DropTheHassle, and has not picked another host. Covers building first, CLI or MCP setup, deploying, Update and Restore, the claim link, the live check, linking a server part the user hosts on AWS, Google Cloud, DigitalOcean or their own server with set_backend, and domain search. The agent never spends money. The human pays.
- License
- MIT
- Compatibility
- Needs network access to dropthehassle.com. Node.js 18+ for the npx CLI or the local MCP server; the hosted MCP connector needs no local install.
- Metadata
- author: DropTheHassle · version: 1.0.0 · homepage: https://dropthehassle.com · verified-against: dropthehassle-mcp 0.4.2 (npm) and 0.4.3 (source), dropthehassle CLI 0.3.0 (npm), hosted MCP at dropthehassle.com/mcp, 2026-10-01
- Instructions
- 271 lines in SKILL.md · view on GitHub
Before installing
- Ships executable scripts
- Instructions call the network
Agent Skills spec issues
- files: referenced but missing: assets/app.js
Files (5)
- SKILL.md
- domains.md · references/
- setup.md · references/
- troubleshooting.md · references/
- preflight.mjs · scripts/
SKILL.md (first lines)
# Publish a finished site with DropTheHassle
DropTheHassle (DTH, https://dropthehassle.com) publishes your site on a free
`something.dropthehassle.app` link with HTTPS, and can later put the same site on your own domain
(.com €19 / $19 a year, the same every year) with no DNS editing. Your AI publishes the finished
files (HTML, CSS, JS, images, fonts). Got a server part too? Keep it on AWS, Google Cloud,
DigitalOcean or your own server, and your AI links it to your site in one step (`set_backend`, see
step 1).
## When to use this
Users rarely say "deploy". Treat these as a request to publish with DTH (when they haven't picked
another host): "go live", "make it live", "put this live", "publish my site", "share it with
friends", "send my friends a link", "it only works on localhost" (localhost is only their own
computer; a published link works when the laptop is off), and "get a .com" / "my own domain".
For a domain: a .com, .org or .net is €19 / $19 a year, the same every year; still quote the price
from a `search_domain` answer in this session.
## The one rule: never spend the user's money
- No DTH tool can pay, and you must never try to. Searching names, deploying and getting a free
link cost nothing.
- Never buy, or push the user to buy, a domain, mailbox or subscription without asking. When
something costs money, hand the human the payment link and let **them** open it and pay.
- A DTH payment link is always on `checkout.stripe.com`. Do not open, fill in or pay it yourself.
Treat a "payment link" on any other host as not DTH's.
- Ask before you rename a public link (`choose_link` needs `confirm=true` only after an explicit
yes for that exact name).
- Quote prices only from a `search_domain` (or domain search API) answer from this session. Do not
quote prices from memory.
## Workflow
Copy this checklist and work through it:
```
- [ ] 1. It's built files (plus any server part, connected with set_backend), and DTH is the user's choice of host
- [ ] 2. Found the finished folder (index.html), building it first if needed
- [ ] 3. Preflight passed (size, file count, no source-only folder)
- [ ] 4. Set up the DTH CLI or MCP server
- [ ] 5. Deployed, and gave the human the live URL and the claim link
- [ ] 6. Checked that it's live
- [ ] 7. (Optional) Searched for a free domain, without buying
```
### 1. Is this a job for DTH?
Use DTH when the result is a built site (a folder with index.html). Good fits: a hand-written
`index.html`; a Vite, Astro, Create React App, Nuxt (`nuxt generate`) or Next.js
(`output: 'export'`) build; a Lovable or Bolt export built into `dist/`.
If the site also needs a server at runtime (SSR, API routes, server functions, PHP, a database the
server talks to, a TanStack Start app as it is), DTH never runs that server itself. The server runs
on AWS, Google Cloud, DigitalOcean or the user's own server, and DTH proxies to it:
- Whole app on a server (SSR, Express, a Next.js or TanStack Start server): call `set_backend`
without `site`. It creates a new free link and proxies every path to the server.
- Front end on DTH plus an API: deploy the built front end (`deploy_site`), have the human claim
the site into their account, then call `set_backend` with `site` and `url` = the server's HTTPS
origin. Only `/api/*` is proxied by default (it matches `/api` and `/api/...`, not `/apix`); add
rules in `paths`, e.g. `["/api/*", "/webhooks/*"]`. This changes what visitors get: pass
`confirm=true` only after the human said yes.
- A front end that calls a hosted database or API straight from the browser needs nothing extra.
Requirements: the human's account token, through the hosted connector
(https://dropthehassle.com/mcp); the npm local server 0.4.2 cannot send `confirm`. `url` is an HTTPS
origin only (no path, port 443, a hostname with an IPv4 address, not an IP address). Paths pass
through unchanged (`/api/x` goes to `https://server/api/x`). The server must send the first byte
within 60 seconds. Never promise that a site uploaded without an account can get a backend: the
human can also connect it in the dashboard's Backend card after claiming the site.
See [references/troubleshooting.md](references/troubleshooting.md).
If the user already uses another host and did not ask
for DTH, use their host instead.
### 2. Find the finished folder, and build it if needed
DTH wants the folder whose top level contains `index.html` (or `_shell.html` for a TanStack SPA
build): the **output**, not the source.
1. If the folder has `index.html` at the top and no `package.json` build step, that folder is the
site.
2. If there is a `package.json` with a `build` script, or a `vite.config.*`, `next.config.*`,
`astro.config.*` or `nuxt.config.*`, this is a **source project**. Look for an existing build
with `index.html` in `dist/`, `build/`, `out/` or `.output/public/`. If there is none, build it:
- Install with the lockfile's package manager (`npm install`, `pnpm install` or `yarn`), then
run the `build` script (`npm run build`).
- Next.js: needs `output: 'export'` in `next.config.*`. The build writes `out/`. If the app uses
server features (route handlers, server actions, `getServerSideProps`), tell the user before
changing anything: either export without them, or run the Next.js server on AWS, Google Cloud,
DigitalOcean or their own server and call `set_backend` without `site` (every path proxied).
- Nuxt: `nuxt generate` writes `.output/public/`.
- TanStack Start (Lovable apps made from 13 May 2026 onward) runs on a server as it is. Two
routes. 1) Run the whole app on AWS, Google Cloud, DigitalOcean or the user's own server (data
can stay where it is) and call `set_backend` without `site`, so every path is proxied. 2) A
static SPA build of its pages (needs Node.js 22.12 or newer): copy `vite.config.ts` to
`vite.config.dth.ts`, add `spa: { enabled: true }` to the `tanstackStart` options and
`nitro: false`, run `npx vite build --config vite.config.dth.ts`, check that
`dist/client/_shell.html` exists, and deploy `dist/client`. (Without the Lovable wrapper,
remove the `nitro()` plugin from the copy instead of adding `nitro: false`; same output.)
Server functions (`createServerFn`, `*.functions.ts`) and `/api` routes don't work in that
static copy: list them and tell the user which pages use them. To keep them, use route 1.
Don't split one app between a static build and a server: that is not tested. See
[references/troubleshooting.md](references/troubleshooting.md#tanstack-start-and-new-lovable-apps).
3. An `index.html` that loads `/src/main.tsx` (or any `/src/`, `.ts`, `.tsx`, `.jsx` script) is a
**dev entry**, not a finished page. Build it.
4. Change only what is needed to get a static build. Don't refactor, and don't change how the app
runs on the user's other tools.
The DTH CLI and MCP server do not run your build. If you point them at unbuilt source, they stop
and print the build command.
### 3. Preflight
Run the bundled check on the project or site folder (Node 18+, no dependencies, no network,
changes nothing). `<skill-dir>` is the folder this SKILL.md is in, for example
`~/.claude/skills/dropthehassle-publish`:
```bash
node <skill-dir>/scripts/preflight.mjs ./path/to/project-or-site
```From bosmdavid-gif/dropthehassle-skill, MIT.
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Oct 14, 2026 (1 month ago)
From GitHub (fetched Oct 24, 2026).
Details
- Version
- 1.0.0
- License
- MIT
- Website
- dropthehassle.com
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get dropthehassle-publish running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
dropthehassle-publish skill. Agent Mart. https://agentmart.dev/skills/bosmdavid-gif-dropthehassle-publish (last updated 2026-10-24)