steam-publish
Publish or update a game on Steam with Steamworks and SteamPipe: configure depots and packages, upload builds with steamcmd, set a build live on a branch, and run the release checklists. Use for Steam publishing, app_build.vdf/steamcmd uploads, depots, beta branches, or a store page release.
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill steam-publish --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Steam Publish (Steamworks + SteamPipe) Take a finished build to a live Steam store page. Two tracks run in parallel and both must be approved before release: the **store page** (presence) and the **build** (SteamPipe upload + the release checklists). This skill is the operational checklist; deep build-script, CI/CD, and troubleshooting detail lives in `references/steampipe-build-scripts.md`. ## When to use - Use when setting up a Steam app, building/editing the store page, configuring depots and packages, uploading a build via SteamPipe/steamcmd, managing beta branches, or releasing and updating a Steam title. - Triggers: `steam_appid.txt`, the Steamworks SDK `tools/ContentBuilder`, `app_build_*.vdf`, `steamcmd`, "publish on Steam", "depot", "set build live". **When *not* to use:** publishing on itch.io (use `itch-publish`); writing the Steamworks **API** in-game (achievements/cloud/overlay live in engine SDK integrations, not here); store/financial *advice* (pricing strategy, tax) — direct the user to Steamworks docs and their own counsel. ## Prerequisites (do these once, in order) 1. **Partner account + Steam Direct fee.** Each new app requires the Steam Direct recoupable fee (
- When to use
- Prerequisites (do these once, in order)
- Core workflow
- Patterns
- 1. SteamPipe ContentBuilder layout (Steamworks SDK)
- 2. Minimal app build script — scripts/appbuild1000.vdf
- 3. Upload the build (Windows; substitute the platform builder elsewhere)
- 4. Iterate safely with a preview build (uploads nothing)
- Pitfalls
- References
- Related skills
What does the steam-publish skill do?
Publish or update a game on Steam with Steamworks and SteamPipe: configure depots and packages, upload builds with steamcmd, set a build live on a branch, and run the release checklists. Use for Steam publishing, app_build.vdf/steamcmd uploads, depots, beta branches, or a store page release.
How do I install it?
Run `npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill steam-publish --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From gamedev-skills/awesome-gamedev-agent-skills, a repository with 406 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.