Wallezy/mgu-setup-skills / skills/mgu-setup
mgu-setup
VerifiedSet up and maintain an owner-authorized BMW MGU over ENET using SSH and Store tools. Use for environment checks, backup preparation, initial root, Store setup, supported distribution migration, map/HUD setup, live read-only log collection and diagnostic bundles, updates, and supported rollback or removal. Supports Chinese and English.
MGU setup and maintenance / MGU 安装与维护
Use the selected distribution's supported tools to complete the requested operation. Respond in the user's language; one task does not authorize the whole lifecycle.
Choose the edition once / 只选一次版本
- First installation: mainland China → recommend Walle CN; other regions → recommend official. Honor an explicit choice first. Use a known region from the conversation/record; do not infer it from language or IP. If unknown, offer the two-line choice in edition selection, without a separate location questionnaire.
- CN uses domestic online catalogs for Store, core components and maps; official follows upstream releases. For official downloads, try direct access, then verified same-version fallback resources according to network availability. Tell users “改用备用源 / using a backup source”; do not introduce a third edition or another source question. A backup download does not change the built-in update source. Match the installer to the edition and verify active sources after setup.
- Existing installation: preserve edition, source and settings. A region recommendation never authorizes migration; an explicit switch uses full-distribution switching.
- Use the published 正式版 / production release. Do not offer channel choices or Beta fallbacks. Only explicit Beta requests, maintenance of a recorded explicit Beta installation, or maintainer release work load release-channels.md; preserve an existing chosen channel. Publishing both channels does not authorize a vehicle trial.
用户说明保持简短:大陆推荐国内版,方便后续国内在线更新;其他地区推荐官方版,直接跟随 GitHub 上游。两者均可自行选择。 复用已选版本,不重复询问地图源、地区和发布通道。
Read only the needed route / 按需读取
| Task | Reference |
|---|---|
| First setup, Store repair, maps/HUD | 中文流程 / English workflow; CN installer/readiness in distributions |
| Existing Store/app update or resume | maintenance-update.md; skip first-root preparation |
| Change edition, including installer and installed components | store-distributions.md |
| First root, access repair, Root tool preparation | root-tool.md; healthy SSH needs no flash/enable/persist |
| Basic/app diagnostics, diagnostic bundle, ambient or map fault evidence | diagnostics.md; connect over existing verified SSH, collect bounded logs and export a redacted ZIP; offline exports also supported |
| Failure, downgrade or rollback | recovery.md |
| Uninstall Store or disable Root/SSH | removal scope and order; SSH removal is not factory firmware restoration |
| Official backup source or mirror maintenance | network-mirrors.md; not needed for ordinary CN online updates |
Historical versions and validation limits: evidence.md. Never treat a historical version as the current recommendation.
For diagnostic requests, reuse the verified ENET address, host-key record and existing key/SSH agent to collect logs directly; ask only for missing connection information. A request to diagnose the connected owner's vehicle authorizes this read-only connection. Finish with evidence coverage and limits; do not enter setup/update/recovery writes. Without a connection or compatible export, report what is missing rather than presenting an empty bundle as successful collection.
Execute and verify / 执行与验证
- Reuse private records, credentials, backups and verified packages. Freshly verify vehicle identity, access and installed versions; ask only for missing or changed prerequisites. With no car, finish local preparation.
- Choose the actual transfer path and scoped environment profile. Prefer a working Store/updater for routine updates. Official
first-install --fromcovers Store setup/repair or a compatible offline refresh, not all apps. USB and hotspots are conditional; a computer cache is not an HU USB source. - Freeze sources, versions, hashes and dependencies before writing; fetch only missing/mismatched resources. Reuse same-version code reviews; inspect changed or uncertain behavior. Do not chase releases mid-update, disable TLS checks or treat a local hash as proof of origin.
- Save readiness in a private session record. Serialize authorized writes and inspect each result. Stop the affected path on identity/hash mismatch, unsupported target, new crash loop, failed rollback or unexplained permissions. Missing prerequisites block that write, not independent preparation.
- Verify target versions, required activation/restart checks, service health and source ownership. Distinguish downloaded, installed, registered and visually observed. Restore temporary proxies and close task-only tunnels; preserve owner settings and a resumable checkpoint.
For update-only tasks, finish after these checks. Without active phone navigation, report visuals unverified; do not expand into map troubleshooting or reboot just for a picture. Record local, emulator and vehicle evidence separately; never invent a passed check.
Boundaries / 操作边界
- Read-only means verified behavior. Unknown daemon arguments can start services; ordinary deploy
statusmay repair the manager. Check vehicle-side--read-onlysupport and exclude a wrapper's repairing fallback for read-only tasks. See recovery. - Flash only for an authorized, prepared need. Establish supported HU architecture, coding recovery and stable power; explicitly select the variant. Never automatically retry flash or choose
fix-key. Flash enables access, not the Store. - Use supported operations. No owner shell edits, manual binary patches, fake network/USB state or bespoke vehicle executables. Use published artifacts and an available HU SDK donor for builds; do not redistribute the SDK.
- Backups have different scopes. Coding, access, deployment and patch originals are not full firmware backups. Check format, coverage and restoration capability; a
verifiedflag is insufficient. See capture limits. Keep vehicle identifiers, keys, firmware-derived files and logs private. - Restart and access deliberately. Use the offered normal restart; no repeated resets or
carplay.service/aapd.serviceshortcuts. Verify changed host keys over physical ENET with fresh identity and retain strict checking. A reboot disconnect is not a reason to reflash. - Report limits honestly. Apply project checks and the authorized release policy; distinguish publication from vehicle validation. Finish independent work when a physical screen/coding tool is unavailable and state the remaining action. Firmware rescue is outside this skill.
Contact / 微信:contact.md. Original content: GPL-3.0-only, LICENSE, NOTICE.md. Third-party resources retain their licenses.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |