This skill guides a coding agent through getting a game build onto an itch.io page and keeping it updated. The user creates the page in the browser; the agent works out the user/game target, picks channel names, prepares a portable build folder and pushes it with butler push.
It leads with a dry run that lists every file without logging in, then covers the page settings people miss: the HTML kind, the played-in-browser tick, platform tags and the AI generation disclosure. A reference covers CI uploads with a pinned, checksum-verified butler install.
What You Get
- Push patterns for one channel per platform, including an HTML channel
- A table of how channel names set the first platform tag
- Filtered, hidden and conditional pushes with ignore globs, hidden channels and if-changed
- A verify list built on butler push —dry-run, butler validate and butler status
- A gotcha list for installers, pre-compressed builds, HTML5 builds that download or show a blank page, invalid target errors and leaked API keys
- A CI reference with a GitHub Actions workflow, a full flag table and the update-check API
Common Use Cases
- Publishing a first Windows, macOS and Linux build to a new page
- Fixing an HTML5 game that shows a download button when it should play
- Pushing a jam build and updating it later
- Uploading builds from GitHub Actions on a version tag
What Makes It Unique
The skill is built around one command, butler push, and the traps around it that the channel name does not fix: the page Kind, the browser play tick and the platform tags are page settings the user changes on Edit game. It also keeps a dry run, which needs no credentials, as the first check and ties the HTML5 limits and the itch.io AI disclosure rule to dated version notes.
Under The Hood
The agent loads the SKILL.md and reads the CI reference only when it uploads from CI. It runs butler commands on your machine: version, validate and push with a dry run need no login, while a real push uploads your build folder to itch.io over the network using credentials from butler login or a BUTLER_API_KEY environment variable. The user runs the browser login. In CI the reference downloads a pinned butler release with curl, checks its SHA-256, unzips and runs it. The agent may also write a workflow file and a version file.