This skill takes a finished build to a live Steam store page. The agent writes the app_build and depot_build VDF scripts, checks them with a bundled Python script, runs a preview build and drives steamcmd to upload. The user does the partner-site steps and reports the IDs they produce.
It covers the two parallel tracks that both need approval, the store page and the build, plus beta branches, the Content Survey, the Coming Soon period and the manual release clicks. A reference adds multi-depot scripts, CI login tokens, patch-size hygiene, Steam Deck review and a troubleshooting table.
What You Get
- A minimal app_build script and a multi-depot layout with depot_build scripts, file mappings, exclusions and file properties
- A bundled checker, check_steam_build.py, that parses the VDF, resolves paths and reports files and bytes per depot with error and warning codes
- steamcmd upload commands for Windows, Linux and macOS, with a preview dry run first
- Beta branch steps, CI login token handling and patch-size hygiene
- A Steam Deck and Steam Machine review checklist
- A troubleshooting table for failed application info, status 6, login denied and previews that upload nothing
- Dated version notes on the app fee, review times and waiting periods
Common Use Cases
- Writing the first app_build script for a one-depot game
- Fixing Failed to get application info or status 6 on upload
- Testing a build on a password-protected beta branch before default
- Uploading from CI without a password in the scripts
What Makes It Unique
The skill separates what the agent does from what only the account owner can do, including the manual steps that cannot be scripted: promoting a build to default, posting Coming Soon and releasing. Its checker reports file counts and sizes per depot before any upload, which exposes a wrong mapping, and it records the Steam fees and waiting periods with a verification date.
Under The Hood
The agent loads the SKILL.md and reads the SteamPipe reference when it needs depth. It writes VDF scripts and runs the bundled Python checker, which its docstring says is read-only, with no network use and no steamcmd or login file access. It then runs steamcmd on your machine, which logs in to Steam with a build account and uploads your build files over the network; the user types the password and Steam Guard code at the prompt. For CI the reference restores a saved login token from a secret, so the token must be protected. The agent does not commit secrets.