About this skill

Problem

Uploading WeChat Mini Program or Mini Game experience builds often fails on repository setup: project.config.json may have inconsistent appid, compileType, or miniprogramRoot, miniprogram-ci may be missing, or the upload private key path is absent. Handwritten commands can mix Mini Programs, Mini Games, and cloud function deployment, producing plausible-looking parameters but failed uploads.

How It Works

The skill centers on scripts/upload_experience.js and follows three steps:

Doctor checks: reads repository config and verifies the upload key, robot number, miniprogram-ci, and external configuration.
Dry-run validation: resolves project type, upload path, version, and description, then shows the upload plan without calling WeChat CI.
Real upload: after doctor passes, calls ci.upload(...) to submit the experience build and reports appid, version, robot number, and result summary.

Configuration precedence is CLI arguments, environment variables, repository-external config, and built-in defaults, keeping machine-specific paths out of source control.

Boundaries

It targets experience-build uploads and does not replace cloud function deployment. If the repo contains cloudfunction/, code upload and cloud function deployment remain separate operations. compileType: "game" is treated as a Mini Game by default. Private key files and local config should not be committed; the skill asks only for a file path, not key contents.

Screenshots

Use Cases

When asked to upload a WeChat Miniapp experience build, verify appid, compileType, and the upload private key first.
Before submitting a Mini Game version, use dry-run to confirm miniGame type, version, and robot number.
When CI upload fails, run doctor to separate missing key, missing miniprogram-ci, and IP whitelist issues.
When cloudfunction/ exists, remind developers that code upload and cloud function deployment are separate tasks.

Best For

Miniapp frontend engineers: need to verify repo config and miniprogram-ci before each experience build.
Mini Game maintainers: need to detect project type via compileType and upload to a specified robot.
CI operations engineers: need to classify upload failures by config errors, missing keys, and IP whitelists.
Security reviewers: need to keep upload private keys and local config out of repositories.