platform-picker
Skill1 starsChanged 2 days agoMITView on GitHub
Recommends where to release a game first (browser game portals like CrazyGames or Poki, itch.io, Steam, mobile) and in what order, based on engine, build size, genre, session length and the creator's goal. Use when the user asks where to publish, which platform to launch on, web vs Steam vs itch, or "nên đăng game ở đâu". Produces a staged release plan, not a single answer.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- SaintChris/hermes-skillstheir own version, first seen Jun 10, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- SaintChris/hermes-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- ai-disclosureSkill
- community-launcherSkill
- game-contextSkill
- hook-finderSkill
- steam-page-wishlistSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Read .agents/game-context.md.
- Very specific: line 25
Read references/platforms.md for the facts you cite.
- Distinctive: line 65
Never promise income. Portal ad revenue is usually small (see references).
- Very specific: line 69
If a fact is not in references/platforms.md, say you are not sure and point to the official docs instead of guessing.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Platform Picker
Help a vibecoder choose where to release first and what comes next. Most AI-built games are small, web-friendly and unproven, so the default is: validate the hook cheaply on the web, then invest in Steam only if the signal is good. Override the default whenever the game's facts say otherwise.
Language
Answer in the user's language. Keep platform names and technical terms in English.
Workflow
- Read
.agents/game-context.md. If missing, run thegame-contextinterview (core questions 1–6 only) first. - Collect the 6 decision inputs (ask only for missing ones):
- Engine and whether it exports to WebGL/HTML5
- Initial download size of a web build (MB)
- Genre and session length
- Goal: players & feedback / wishlists / revenue
- Has the user got a Steam Direct fee budget and time for a store page?
- Does the game have online features, and in which countries will it be sold commercially? (local licensing flag, see below)
- Walk the decision tree below.
- Read
references/platforms.mdfor the facts you cite. Always show thelast_checkeddate and tell the user to verify terms on the official page before signing anything. - Output the plan in the format below.
Decision tree
Is a playable build < ~50 MB and does it run well in a browser?
├─ Yes → Stage 1: itch.io (free, HTML5) + one portal (CrazyGames first: open self-upload, non-exclusive)
│ Initial download < 8 MB and polished? → also consider Poki (curated, exclusive web deal — read terms)
└─ No → Stage 1: itch.io downloadable demo + make a "web slice" (one level, compressed) if feasible
Session length < 10 min, instant fun? → portals fit well (ad-revenue model, huge casual traffic)
Session long, cozy/sim/story, PC-style controls? → portals are for testing only; Steam is the real target
Goal = wishlists or revenue AND the hook test (hook-finder) got real traction?
└─ Stage 2: Steam "Coming Soon" page ASAP (wishlists need months), demo, Next Fest later
Mobile: only if controls are touch-native and the user accepts ASO + store review overhead. Rarely stage 1 for vibecoders."Real traction" is a judgment call; suggest concrete gates such as: strangers (not friends) finish the first session, comments ask "where can I get this?", a clip clearly outperforms the user's other clips.
Output format
## Recommended path for <game>
**Stage 1 (now → N weeks): <platforms>**
- Why: <2 bullets tied to the game's facts>
- To do: <3–5 concrete steps>
- Success gate to move on: <measurable signal>
**Stage 2: <platform>** — when the gate is passed
**Not now: <platform>** — <one-line reason>
⚠️ Check before you commit: <terms that need verification, with links>Rules
- Never promise income. Portal ad revenue is usually small (see references); present portals as a player and data channel first.
- Flag Poki's exclusivity clearly; recommend the user read the contract.
- For Steam, mention that wishlists take months to build and shadow-dropping (launching without a page/announcement) is the most common mistake.
- Local licensing flag: some countries require a license or government approval to publish games commercially or to run online games (for example Vietnam's Decree 147/2024/NĐ-CP, or approval for publishing in mainland China). If the game targets such a country, mention that rules exist and suggest checking with a local expert. Do not give legal advice, and don't assume rules for a country you have no source for.
- If a fact is not in
references/platforms.md, say you are not sure and point to the official docs instead of guessing.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

