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 SDKtools/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)
- Partner account + Steam Direct fee. Each new app requires the Steam Direct recoupable
fee (USD $100 per app at time of writing). You receive an App ID — find it on your
Steamworks homepage. Treat the App ID as the key to everything below. - A dedicated build account with least privilege. Builds require a Steam account in your
partner group with Edit App Metadata and Publish App Changes To Steam. Create a
separate build account with only those permissions (not your admin login). Releasing the
app additionally needs Manage pricing and discounts. - Download the Steamworks SDK on the upload machine. The SteamPipe tools are under
tools/ContentBuilder/.
> Security note: never commit account passwords or the config.vdf login token to the repo.
> See the CI/CD section in the reference for the supported token workflow.
（为兼容发布已截断）
