Steam Store Launch Ops

This is a triage router for indie Steam launches that stops you from dumping generic marketing advice when someone says "my wishlists are weak." It forces you to pick one packet first: page promise audit, wishlist signal check, demo readiness gate, event timing workback, or launch ops runbook. The diagnostic model separates visibility, conversion, proof, timing, and ops bottlenecks honestly, and it bakes in the one-shot Steam constraints most teams forget, like the single demo notify window or Next Fest readiness gates. If the real problem is broader GTM work or build issues, it routes you out. Useful when you need to turn late-stage launch stress into one clear next artifact instead of rewriting everything at once.

skills.sh installs: 143
GitHub stars: 22
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add akillness/oh-my-skills --skill steam-store-launch-ops --agent claude-code

Installs into .claude/skills of the current project.

Files

Steam Store Launch Ops

Use this skill as a packet-first Steam launch router.

The job is not to dump generic marketing advice. The job is to:

identify the current Steam hook,
choose the single best packet,
separate visibility, promise, proof, timing, and ops honestly,
make one-shot Steam constraints explicit,
route broader marketing, player-feedback, build, or performance work outward when those are the real problems.

Read these when needed:

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly