Steam Store Page Editor

Steam Store Page Editor

Use this skill to improve Steam store pages through a report-first workflow: diagnose the page, prioritise fixes, then produce maintainable source copy and Steam-ready output.

Core Workflow

1. Identify the task type:

• Audit: evaluate existing Steam page content and produce a report.
• Rewrite: improve supplied copy without a full market report.
• Build: create a page draft from a game brief.
• Export: convert maintainable Markdown/YAML source into Steam-flavoured BBCode.
• Visual brief: assess or specify capsule, screenshot, GIF, and trailer direction.

1. Gather inputs from the user or provided files:

• game title, genre, target audience, platform status, release state, price, short description, long description, tags, capsule/screenshot/trailer notes, current Steam URL or draft, and known comparable games
• traffic, wishlist, UTM, review, or playtest data if available

1. If current Steam policy, asset dimensions, event timing, or platform behaviour matters, verify against official Steamworks documentation before making definitive claims.
2. Produce an audit report first unless the user explicitly asks only for copy, formatting, or a narrow edit.
3. Convert recommendations into edited copy only after naming the positioning problem being solved.
4. Preserve an editable source version before producing Steam-ready BBCode.
5. Flag assumptions, missing evidence, and open questions rather than inventing market data.

Reference Routing

Read only the reference files needed for the task:

• For full audits and scoring: read [references/audit-rubric.md](references/audit-rubric.md).
• For market positioning, comparable games, tags, review tiers, and competitor patterns: read [references/comparable-analysis.md](references/comparable-analysis.md).
• For short description, About This Game structure, hooks, feature-benefit copy, and rewrite patterns: read [references/steam-copy-patterns.md](references/steam-copy-patterns.md).
• For Steam markup conversion and formatting validation: read [references/steam-bbcode.md](references/steam-bbcode.md).
• For Steam rules, official documentation checkpoints, asset constraints, and analytics metrics: read [references/steam-compliance.md](references/steam-compliance.md).

Use [assets/store-page-source-template.yaml](assets/store-page-source-template.yaml) as the maintainable source-of-truth format when the user wants an editable draft or repeatable workflow.

Output Modes

Audit Report

Use this when the user asks whether a page works, how to improve it, why competitors are stronger, or what to do first.

Include these sections:

1. Market Position Summary
2. What You're Fighting Against
3. Short Description Analysis
4. Long Description Analysis
5. Tag Strategy Analysis
6. Capsule and Visual Direction
7. Screenshot Strategy
8. Pricing and Positioning
9. Three Things To Do First
10. Open Questions
11. Knowledge-Base Additions, when a reusable insight should be saved for future drafts

Keep the report action-oriented. For each major problem, include evidence, impact, and a concrete edit or decision.

Edited Store Page Package

Use this after an audit, or when the user asks for a draft.

Provide:

1. Positioning brief: audience, promise, hook, genre signal, differentiator, and comparable frame.
2. Short description: plain text only, no bullets, no formatting, no time-sensitive claims.
3. About This Game source: maintainable Markdown or YAML sections with headings, body copy, and optional visual notes.
4. Steam-ready BBCode: paste-ready markup for the Steam editor.
5. Tag recommendations: ordered top tags with rationale.
6. Visual shot list: capsule promise, first four screenshots, GIF/embedded-image opportunities, and trailer opening note if relevant.
7. Compliance checklist: rule risks and anything requiring manual Steamworks review.

Evaluation Principles

• Optimise for Steam shoppers who skim. Put genre, player fantasy, and differentiator early.
• Compare against actual nearby games, not a generic ideal page.
• Prefer concrete player actions, stakes, systems, moods, and outcomes over abstract praise.
• Distinguish discoverability work from conversion work:
• tags, genre signal, capsule readability, and traffic source affect discovery
• short description, screenshots, trailer, About This Game, price, reviews, and proof affect conversion
• Treat capsule art, screenshots, trailer, tags, and copy as one promise. They should not sell different games.
• Keep all recommendations editable. Avoid one-off prose that cannot be maintained by the developer later.

Quality Bar

Do not:

• invent review counts, prices, Steam tags, competitor claims, asset requirements, or Steam policy
• overfit to AAA store pages when the game is indie, niche, experimental, or early
• make the page sound more impressive by making it less specific
• bury the strongest hook below the first paragraph
• use marketing claims that Steam would reject or that the current build cannot support
• output BBCode without also preserving a cleaner editable source when the user is building a page

Do:

• name missing data explicitly
• prioritise the first three actions when the user needs momentum
• keep short descriptions tight and genre-legible
• make long descriptions skimmable with strong section headers
• check that tags, screenshots, and copy tell the same story
• recommend official Steamworks review for final compliance, pricing, and asset decisions

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: AlexStormwood
• Source: AlexStormwood/agentic-skills
• License: MIT
• Homepage: https://www.skills.sh/alexstormwood/agentic-skills

Install and usage instructions live in the source repository linked above.