Ship a website by
talking to your AI.
Describe what you want — an AI builds it and it's live in about a minute. Pick the way that fits where you are:
Add the skill to your agent.
Works with Claude Code, the ChatGPT desktop app, Cursor, Codex CLI, opencode, GitHub Copilot — anything that can read and write files on your machine. One line teaches your agent the whole platform (deploy, state & collections, private pages, widgets). Then just say “deploy this folder” or “build me a waitlist page.” The installer knows each agent's skills folder (and the right Windows paths), so you don't have to.
ChatGPT: this needs the desktop app, in the mode that can open a folder and edit files. A plain ChatGPT chat in a browser can't install anything — use the third option below instead.
npx skills add vineetu/simple-host
GitHub Copilot CLI: Copilot can't unzip skills into its own sandboxed ~/.copilot folder, so install them from your terminal with the universal installer — name the agent and use --copy (Windows symlinks need admin), adding each skill:
npx skills add vineetu/simple-host -g -a github-copilot -s website-deploy --copy -y npx skills add vineetu/simple-host -g -a github-copilot -s website-deploy-builder --copy -y npx skills add vineetu/simple-host -g -a github-copilot -s connect-domain --copy -y
Other tools · manual install · Windows
| Tool | Skills folder · macOS / Linux | Windows · PowerShell |
|---|---|---|
| Claude Code | ~/.claude/skills/ | $env:USERPROFILE\.claude\skills\ |
| ChatGPT desktop Codex CLI | ~/.agents/skills/ | $env:USERPROFILE\.agents\skills\ |
| Cursor | ~/.cursor/skills/ | $env:USERPROFILE\.cursor\skills\ |
| opencode | ~/.config/opencode/skills/ | $env:USERPROFILE\.config\opencode\skills\ |
| Hermes | ~/.hermes/skills/ | $env:USERPROFILE\.hermes\skills\ |
| OpenClaw | ~/.openclaw/skills/ | $env:USERPROFILE\.openclaw\skills\ |
| Anything else | Point it at the skills directory it reads — the files are identical. | |
| Claude.ai / Desktop | Paid plan with Code execution on. Skills settings → “+ Create skill”, upload each ZIP separately: website-deploy.zip website-deploy-builder.zip connect-domain.zip | |
Download https://simple-host.app/skills.zip and unzip it into your skills folder — create it if it doesn't exist. Use the one folder that matches whichever agent you are: • Claude Code <home>/.claude/skills/ • ChatGPT desktop, Codex CLI <home>/.agents/skills/ • Cursor <home>/.cursor/skills/ • opencode <home>/.config/opencode/skills/ Work out <home> from the shell you are actually in: $HOME on macOS, Linux, and in PowerShell; %USERPROFILE% only in cmd. Put the three skill folders straight in, with no extra folder wrapped around them. Then list your skills, confirm website-deploy, website-deploy-builder and connect-domain all appear, and ask me what I'd like to build.
GitHub Copilot CLI sandboxes its own ~/.copilot folder, so a download-and-unzip can't reach it — add each skill by URL with Copilot's own command instead:
copilot skill add https://simple-host.app/skills/website-deploy/SKILL.md copilot skill add https://simple-host.app/skills/website-deploy-builder/SKILL.md copilot skill add https://simple-host.app/skills/connect-domain/SKILL.md
These fetch one file each. website-deploy's SKILL.md points at reference documents for framework builds, packaging, and the backend; it cites each one by full URL as well as by relative path, so an agent installed this way can still fetch them on demand.
mkdir -p ~/.claude/skills && curl -fsSL https://simple-host.app/skills.zip -o /tmp/sh-skills.zip && unzip -o /tmp/sh-skills.zip -d ~/.claude/skills
New-Item -ItemType Directory -Force "$env:USERPROFILE\.claude\skills" | Out-Null Invoke-WebRequest https://simple-host.app/skills.zip -OutFile "$env:TEMP\sh-skills.zip" Expand-Archive "$env:TEMP\sh-skills.zip" "$env:USERPROFILE\.claude\skills" -Force
There's also curl -fsSL https://simple-host.app/install.sh | sh (macOS/Linux) — it only does the unzip above; read it first if you prefer. Hermes installs from the URL directly: hermes skills install https://simple-host.app/skills/website-deploy/SKILL.md --name website-deploy. OpenClaw auto-discovers any SKILL.md under ~/.openclaw/skills/.
Build it right here.
Describe your site in the chat and it builds and previews it in seconds. Nothing to install, nothing to download — great from a phone.
Copy a prompt, paste back the result.
For a chat that can't touch your files. Copy the prompt below, paste it into the chat, and it hands you a ready-to-publish site as one block. Paste that back at simple-host.app and hit Publish. (One 6-digit email code to publish — no password.)
Curious what you can build? Static pages with a real backend when you need it — forms, counters, guestbooks, comments, private pages. See the full reference →
Before you publish
Who can see my site?
Anyone with the link. Sites are served on the public internet at
sites.simple-host.app/<you>/<site>/ — there is
no sign-in in front of them and no “unlisted” mode. They are not listed
in a directory unless you choose to share them, but treat a link as
public. If you need a page only certain people can open, connect your
own domain and set a view password on it.
Is the data my site collects private?
No. The per-site store — shared state and collections, which is what powers RSVP forms, counters, guestbooks, and comments — is public and unauthenticated. Anyone who knows the site name can read it and write to it. It is a scratchpad, not a database. Never put passwords, API keys, tokens, or anyone's personal information in it.
The practical version: a sign-up form on a Simple Host site is fine for a party or a team lunch. It is not fine for anything you would mind a stranger reading.
Can someone else change my site?
Not the files. Deploying a new version needs your API key, and today every site has exactly one owner — there is no way to grant a colleague deploy access yet. The data your site collects is a different story: see the answer above.
What is this actually good for?
Anything that is a page: a portfolio, a résumé, an event invite, a launch or coming-soon page, docs, a menu, a mockup you want feedback pins on. Add the backend when the page needs to remember something across visitors — an RSVP list, a vote, a counter, a guestbook.
What it is not: nothing runs on the server. No PHP, no Node, no Python, no database you control, no server-side rendering. If your idea needs a login system or private records, it needs a different host.
How much does it cost, and what happens to my site?
Nothing, and it stays up until you delete it. The server keeps recent versions of each site so you can roll back. Deleting a site removes its files, every version, and its stored data — that is not reversible.