vineetu
UserDeploy websites to simple-host.app from your coding agent (Claude Code, Codex, Cursor) — one-command install. Static hosting + a per-site backend: state, collections, private pages, templates.
Categories
Indexed Skills (4)
connect-domain
Connect a user's own custom domain (subdomain e.g. recipes.brand.com via CNAME, or apex e.g. brand.com via A record) to a site already deployed on simple-host. Use when a user wants their site served from their own domain over HTTPS, or wants sign-in on saves from a page (a domain is what adds sign-in to saves; on the shared host anyone can read and write). Drives the bind → DNS → verify → live flow; the agent does the API work and relays the one DNS record the human must add at their registrar.
website-deploy-builder
Plan what to build on Website Deploy (simple-host.app). Helps a user decide whether their idea fits the static + light-backend model, maps it to concrete patterns (shared JSON state with atomic ops, append-only collections, localStorage, public APIs), and produces a focused prompt for an implementation agent. Knows the one planning rule that matters - saves on the shared host are open to everyone; if saves should be per-person or protected, the site needs its own custom domain. Use when a user is starting a new site or describes a feature idea and needs help mapping it to what the platform can do.
website-deploy
Deploy static websites to simple-host.app. Use when an agent needs to guide a user through registration, build/validate a static site, deploy it (inline JSON files OR a tar.gz/zip archive), or wire up the per-site backend — shared JSON state with atomic ops and append-only collections. Reads are public everywhere; on the shared host pages write freely too; on a site with its own custom domain visitors sign in with Google or an emailed code via the hosted auth.js before saving; agents write with an API key anywhere.
run-hackathon
Stand up a private Simple Host instance for a hackathon on the organiser's own cloud account, create participant accounts in bulk, hand out their keys, and tear the whole thing down afterwards. Use when someone wants to run a hackathon, a class project showcase, an internal build day or any event where non-technical people need somewhere to publish what they make. Drives provider → server → DNS → install → accounts → teardown. The organiser never opens a terminal; this skill does.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.