@blazium-games/skills 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,98 @@
1
+ ---
2
+ name: blazium-games-store-page
3
+ description: Create or update a Blazium Games store page. Drafts the name, tagline, and description from a pitch, creates the page as a draft, updates copy, fills in the taxonomy, images, and similar titles until the listing check passes, sets a price or donations, and changes visibility. Use when the user wants to create a game page, write store copy, rename a game, price a game, accept donations, or publish a page on Blazium Games.
4
+ license: MIT
5
+ ---
6
+
7
+ # Blazium Games: Store Page
8
+
9
+ Create and edit the public page at `https://<username>.blazium.games/<vanity_name>`.
10
+
11
+ ## Invoke This Skill When
12
+
13
+ - "Create a Blazium Games page for my game", "write my store description"
14
+ - "Make my game public", "change the tagline"
15
+ - "Sell my game for $4.99", "let players donate"
16
+ - The `bootstrap_game` prompt needs a page to exist
17
+
18
+ ## Prerequisites
19
+
20
+ - The `blazium-games` MCP server is connected with write access
21
+ - Creating a page needs an account-level token (a project-bound token can only edit its own game) and developer mode on the account. `4105` means it's off: the human turns it on at https://blazium.games/settings and accepts the developer terms. Never turn it on for them
22
+ - Going public, setting a price, and uploading need the owner's email verified. Check with `get_account`; if `email_verified` is false, call `request_email_code`, ask the human for the code from their inbox, then call `verify_email`. Updates that set `visibility` to `public` fail with code `4096` until then
23
+
24
+ ## 1. Find or create
25
+
26
+ 1. Call `list_games`. If a game matches the user's project, use its `uid` and go to step 3 (Update).
27
+ 2. Otherwise draft copy. Use the `draft_game_page` prompt with a short `pitch`, or write:
28
+ - `name`
29
+ - `tagline`: one factual line. This is the share-card description on Discord, X, and Google. Do not put private contacts, keys, or unreleased URLs in it
30
+ - `description`: markdown, two short paragraphs, facts only. Its first plain line is the share description when there is no tagline
31
+ 3. Confirm the copy with the user.
32
+
33
+ ## 2. Create
34
+
35
+ Call `create_game`:
36
+
37
+ | Field | Notes |
38
+ |-------|-------|
39
+ | `name` | Required |
40
+ | `tagline` | One line |
41
+ | `description` | Markdown |
42
+ | `visibility` | Start with `draft`. Options: `draft` (owner and admins), `owner` (owner only), `invisible` (link only), `public` |
43
+ | `asset_type` | `game`, `application`, `tool`, `mod`, `plugin`, `game_asset`, or `dev_asset` |
44
+ | `vanity_name` | URL slug, lowercase with dashes |
45
+ | `parent` | Required for `tool`, `mod`, and `plugin` before they can go public: `{"game": "uid-or-vanity"}` for a listing on Blazium Games, or `{"external_name": "...", "external_url": "https://..."}` for a game that isn't. Ask the user which game it's for |
46
+ | `adult` | `true` only if the user says it has sexual content or nudity. Adult pages are hidden from search, recommendations, and search engines, and need the player's opt-in |
47
+ | `indexable` | `false` keeps the page out of search engines and AI crawlers. Default `true` |
48
+
49
+ Keep the returned `uid`.
50
+
51
+ ## 3. Update
52
+
53
+ Call `update_game` with `uid` and any of `name`, `tagline`, `description`, `visibility`, `asset_type`, `adult`, `indexable`, `parent`. An empty `parent` object clears it. To polish existing copy, run the `improve_game_copy` prompt with the current description first.
54
+
55
+ For mods and plugins, set how to install them with `set_mod_settings` (`install_path` relative to the game folder, `loader` such as `bepinex`, markdown `instructions`). For press coverage, fill the press kit with `set_press_kit`; it powers the page's `/press` page and `press.zip`. If the game is also on Steam, GOG, Epic Games Store, itch.io or another store, read the current links with `get_store_links`, then pass the full list to `set_store_links` (one https link per store, on that store's own site); they show as "Also on". Players can suggest tags; list them with `hide_community_tag` without a `tag`, and hide one only when the user asks.
56
+
57
+ Before switching to `public`, confirm with the user and make sure the owner is verified. `invisible` keeps the page reachable by link but out of listings.
58
+
59
+ ## 3b. Listing (required before public)
60
+
61
+ A page can't go public until the listing check passes (`4225` otherwise).
62
+
63
+ 1. Call `validate_listing`. It returns `errors`, `warnings`, and the allowed values.
64
+ 2. Fix the taxonomy with `update_game_taxonomy`: at least 3 `tags`; for games also `genres`, `session_bucket`, `players_min`/`players_max`, `net`, and `inputs`; for mods and assets `engines`. Only use values from the check's vocabulary (`4071` otherwise). Ask the user rather than guessing player counts, network mode, or content warnings. Ask whether to set `authorship` (`human`, `human_agent`, or `agent_heavy`) and an optional `authorship_credit`; never pick it for them. Ask which parts used generative AI and set `ai_uses` (`art`, `audio`, `code`, `text`, `voice`, `runtime`, or an empty list for none) from their answer. Tools, mods, and plugins also need a `parent`, and plugins an engine.
65
+ 3. Images: PNG, JPEG, GIF, or WebP, sniffed from the file bytes. Wide images need width/height between 1.70 and 1.85. Recommended, and the accepted range: thumbnail 1280x720 (960x540 to 1920x1080, 5 MB), cover 1024x576 (1024x576 to 2048x1152, 8 MB), screenshot 1920x1080 (1280x720 to 2048x1152, 10 MB). A public page needs a cover, a thumbnail, and 4 to 20 screenshots. Add at most 10 at a time. A game can change images 60 times an hour. The account avatar is uploaded on the settings page, not here. MCP never uploads images. Give the user the `chauffeur media` commands (`set_media` returns them), for example `chauffeur media cover art/cover.png` and `chauffeur media add shots/*.png`, run with the game's deploy key, or point them to the game's edit page on the website. See https://docs.blazium.games/docs/cli/media
66
+ 4. A clean build: ship one with `blazium-games-deploy`, then check `scan_status` until a file is `clean`. If a file is `infected` or `error`, tell the user; it was removed and must be rebuilt and uploaded again.
67
+ 5. Optionally `set_similar_games` with up to 10 public titles the user names.
68
+ 6. Call `validate_listing` again; when `ready` is true, set `visibility` to `public`.
69
+
70
+ ## 4. Price or donations (optional)
71
+
72
+ Call `set_game_price` with `uid` and:
73
+
74
+ | Field | Notes |
75
+ |-------|-------|
76
+ | `price_cents` | `0` for free, or `99` to `50000` ($0.99 to $500) |
77
+ | `donations_enabled` | Free games only. Donations are $1 to $500 |
78
+
79
+ To sell several editions (standard, deluxe, beta access, or a bundle with the user's other listings), use `upsert_sku` instead; up to 8 per listing. The listing price then follows the cheapest edition and `set_game_price` returns `4164`.
80
+
81
+ Tell the user what they will receive before setting it: each sale or donation pays the price minus $0.25 + 8% (a $10 game pays $8.95). Earnings unlock 7 days after each sale, and cash-out (8% plus Stripe's payout fee, $25 minimum) is on the website or through `cash_out`; payouts can take up to 72 business hours to reach the bank. Paid games can only be downloaded by buyers. Sales are listed by `list_game_sales`.
82
+
83
+ Details: https://docs.blazium.games/docs/payments/selling
84
+
85
+ ## 5. Verify
86
+
87
+ Call `get_game` and give the user the page URL (`page_url` from `get_deploy_info`, or `https://<owner>.blazium.games/<vanity_name>`).
88
+
89
+ Videos and changelogs are managed on the website or through builds (`blazium-games-deploy`). Image sizes: https://docs.blazium.games/docs/graphical_assets_guidelines
90
+
91
+ ## Docs
92
+
93
+ - https://docs.blazium.games/docs/listings
94
+ - https://docs.blazium.games/docs/content-rules
95
+ - https://docs.blazium.games/docs/press-kit
96
+ - https://docs.blazium.games/docs/seo-and-indexing
97
+ - https://docs.blazium.games/docs/developer-mode
98
+ - https://docs.blazium.games/docs/mcp/reference