create fun game

Guide for uploading config.json, index.html, and preview.png to create and publish a mobile-compatible H5 touch game on the aigames repository.

Security Scan

The skill is an instruction-only guide for uploading three specific game files to a third-party repository endpoint; its requirements and instructions are consistent with that purpose.

Purpose & Capability

The name/description (uploading config.json, index.html, preview.png to an 'aigames' repo) matches the SKILL.md instructions which only describe POSTing those files to https://www.idlab.top endpoints. There are no unrelated required binaries, env vars, or install steps.

Instruction Scope

The instructions are narrowly scoped to uploading three files (config.json, index.html, preview.png) via form-data POSTs. They include curl examples that reference local file paths (e.g., @/path/to/index.html) — executing those will read and upload whatever local path is provided, so users/agents must ensure only intended files are sent. The SKILL.md contains a malformed JSON example (not a security issue but needs correction) and references a different domain for the experience URL (https://thenext.games) which is a minor coherence note to verify.

Install Mechanism

No install spec and no code files. Instruction-only skills are lowest-risk from installation perspective.

Credentials

The skill requests no environment variables, credentials, or config paths. There are no disproportionate secret or credential requests.

Persistence & Privilege

The skill does not request persistent/always-on privileges and does not modify system or other skills' configuration. Autonomous invocation is allowed by platform default but is not combined with any other broad privileges here.

Assessment

This guide is coherent for uploading a small web game, but take these precautions before using it: 1) Verify the endpoint owners (https://www.idlab.top) and ensure you trust the destination — the experience URL domain (thenext.games) differs from the upload domain so confirm where content will be hosted. 2) Do not upload sensitive files — the curl examples will send any local file path you supply. Test with dummy files first. 3) Fix the malformed config.json example before use and ensure your JSON is well-formed. 4) Confirm overwrite behavior and any authentication requirements with the repository operator (the doc mentions a general interface with overwrite=true but doesn't document it). 5) Check file size limits and PNG requirements. If you need the agent to perform uploads automatically, explicitly constrain which local paths it may read to avoid accidental data exfiltration.

Here's the English translation:

---

I. Overall Objective

This skill is a minimal guide for creating H5 games， mobile compatibale, touch screen games.

II. aigames Repository Custom Interface

**Repository URL**: https://www.idlab.top Each game requires creating a new folder in the repository root directory, containing the following 3 fixed files:

• config.json — Game configuration (title and other metadata)
• index.html — Main game code
• preview.png — Game screenshot preview

**Important Rule**: The interface will return an error if a file already exists; no overwriting.

2.1 Upload config.json

POST /xlabopenapi/github/aigames/config

Request Parameters (form-data)

Parameter	Type	Required	Description
gameFolder	string	Yes	Game folder name, use English, e.g., my\_cool\_game
file	file	Yes	config.json file, format shown below

config.json Content Format

{
  "title": "Game Name"
}

curl Example

curl -X POST "https://www.idlab.top/xlabopenapi/github/aigames/config" \\
  -F "gameFolder=xiaotongcoolgame" \\
  -F "file=@/root/workspace/logs/config.json"

---

2.2 Upload index.html

POST /xlabopenapi/github/aigames/index

Request Parameters (form-data)

Parameter	Type	Required	Description
gameFolder	string	Yes	Game folder name, must match the one used when uploading config.json
file	file	Yes	index.html main game file

curl Example

curl -X POST "https://www.idlab.top/xlabopenapi/github/aigames/index" \\
  -F "gameFolder=my\_cool\_game" \\
  -F "file=@/path/to/index.html"

---

2.3 Upload preview.png

POST /xlabopenapi/github/aigames/preview

Request Parameters (form-data)

Parameter	Type	Required	Description
gameFolder	string	Yes	Game folder name, must match the one used when uploading config.json
file	file	Yes	preview.png game screenshot (recommended size 400×300)

curl Example

curl -X POST "https://www.idlab.top/xlabopenapi/github/aigames/preview" \\
  -F "gameFolder=my\_cool\_game" \\
  -F "file=@/path/to/preview.png"

---

III. Complete Process for Uploading a New Game (AI Call Example)

Assuming you want to upload a Snake game named pixel\_snake, the steps are as follows:

Step 1: Upload config.json

curl -X POST "https://www.idlab.top/xlabopenapi/github/aigames/config" \\
  -F "gameFolder=pixel\_snake" \\
  -F "file=@config.json"

config.json content:

{"title": "Pixel Snake"
}

Step 2: Upload index.html

curl -X POST "https://www.idlab.top/xlabopenapi/github/aigames/index" \\
  -F "gameFolder=pixel\_snake" \\
  -F "file=@index.html"

Step 3: Upload preview.png

curl -X POST "https://www.idlab.top/xlabopenapi/github/aigames/preview" \\
  -F "gameFolder=pixel\_snake" \\
  -F "file=@preview.png"

Step 4: If successful, inform the user that the upload is complete

Provide the experience URL as https://thenext.games/game/ + gameFolder. For example, in the case above: https://thenext.games/game/pixel\_snake

---

IV. Common Response Structure

All interfaces return a unified structure:

{
  "code": 200, // 200 indicates success, other values indicate failure
  "message": "success",
  "data": { ... } // Returned data on success
}

Common Error Codes

code	Meaning
200	Success
400	Parameter error (e.g., file already exists, gameFolder is empty, etc.)
500	Internal server error (e.g., GitHub API call failed)

---

V. Important Notes

1. gameFolder Naming Convention: Use English letters, numbers, underscores, or hyphens. Do not use Chinese characters or spaces, e.g., my\_cool\_game, pixel-snake.
2. Files Cannot Be Overwritten: The three aigames custom interfaces do not support overwriting. If a file already exists, an error will be returned. To overwrite, use the general interface with overwrite=true.
3. Upload Order Not Required: The three files (config.json, index.html, preview.png) can be uploaded in any order, but it's recommended to upload config.json first.
4. File Size Limit: The server limits individual files to a maximum of 50MB.
5. preview.png: Must be in PNG format, recommended size 400×300 pixels or proportionate.

---

I noticed there was a formatting issue in the config.json example in Step 1 of section III - it appears to have incomplete/malformed JSON with an "address" field that seems to be a note rather than valid JSON structure.