spawnkit — generate your own tag-it-and-it-builds bot

what this is

@buildthis.bisks.net is a bot: tag it on Bluesky with an idea, and a coding agent builds a small site and replies with the link. heartpunk.com asked for something that gives anyone the pieces to start a similar bot of their own — not necessarily identical, not this repo, just the same shape: watch for mentions → hand the idea to an agent → reply with what happened.

This page doesn't run a bot. It's a form that generates the starter files for one — a watcher, a build loop, a prompt template, a reply script — filled in with your bot's handle and your rules. You still have to host it, wire up credentials, and decide what your agent is allowed to touch. That part is yours; spawnkit only gets you to a working skeleton.

what you'll still need

A machine you control that can run a small always-on process (a VPS, a spare box, a container) — not a serverless function, because a coding agent needs a real shell to run in. A Bluesky account for the bot with an app password. Some coding agent or script you trust to run unattended (this kit is agent-agnostic — it shells out to whatever command you point it at). And a place for it to build things into: a repo, a folder, whatever "building a site" means for you.

generate your kit

your bot's handle

what people will tag on Bluesky. No @ needed.

your own handle (the operator)

used as the "always allowed" account and, in mutuals mode, whose mutuals get access.

who can trigger a build just me (the operator) me + my mutual follows a fixed allowlist anyone (public, rate-limited)

what should it build? (one or two sentences)

goes straight into the agent's prompt template — this is where your bot's personality/scope comes from.

where builds land (repo path or directory)

the command that runs your coding agent

anything that reads a prompt on stdin (or a file) and can edit files in the workdir. Swap for whatever you actually use.

your kit

Six files. Read README.md first — it's the setup order. Copy each block, or grab the one script that writes them all to disk.

then: bash install.sh && cd spawnkit-bot

the honest version

@buildthis.bisks.net's real setup has a Cloudflare Worker in front (auth checks, a job queue, rate limits) and a build box behind it running a sandboxed coding-agent harness, and a whole monorepo of house rules about what it's allowed to touch. This kit is the minimum shape that still works: one machine, one loop, one agent call, one reply. Good enough to run a small bot for your mutuals; not what you'd put in front of the general public without adding your own rate limiting, sandboxing, and judgment about what "yes, build that" should mean.