Skip to content
SkillScript-led3,513 tokens in use

steam-publish

Ship a game on Steam with Steamworks and SteamPipe: depots, app_build scripts, a script checker, steamcmd uploads, beta branches and release steps.

9,684 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · skills/workflows/steam-publish
npx skills add gamedev-skills/awesome-gamedev-agent-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing steam-publish costs

86tokens idle
3,513tokens in use
6,318tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Script-led

Script-ledMixedModel-led

Most of this skill is scripts, so it behaves much the same whichever model runs it.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: scripts/check_steam_build.py.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter8/15
  • Structure25/25
  • Examples9/15
  • Output15/15
  • Size13/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 126

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity92
  • Maintenance96
  • Community60
  • Maturity24
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers