菜单
Use this skill after upy-norm-pkg completes to deploy normalized driver files to a MicroPython device and validate by running main.py. Invoke when user says things like "烧录测试", "deploy and test", "上传并运行", "验证设备", or after norm-pkg asks to proceed with device testing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Analyze MicroPythonOS App ideas directly or when invoked by mpos-plan-app. Use to turn natural-language MPOS App requests into requirements, default app identity, manifest draft, Activity/Service plan, MPOS/LVGL API plan, dependency risk, test/deploy plan, mandatory MicroPythonOS resource links, and a JSON handoff before code generation.
Deploy or preview a MicroPythonOS app on desktop, web, device copy, MPK install, or installer/flash guidance paths. Use when Codex needs to launch a confirmed app for manual preview, copy it to a board with mpremote, validate an MPK on-device, or route firmware install and erase to install.micropythonos.com. Does not own app generation, static lint, packaging, or default smoke testing.
MicroPythonOS 基础开发知识库。提供代码架构、App/MPK 约束、LVGL 编程约定、MPY API reference、官方 docs 专题 reference、AGENTS 本地强约束。mpos-plan-app / mpos-analyze-app / mpos-prepare-deps / mpos-gen-app / mpos-test-app / mpos-package-app / mpos-deploy-app / mpos-publish-app 均依赖此 skill。
Generate, update, and repeatedly repair MicroPythonOS App code after requirements are confirmed. Use after mpos-analyze-app and optionally mpos-prepare-deps to create or modify an internal_filesystem/apps package directory with root MANIFEST.JSON, root icon_64x64.png, assets/*.py entrypoints/dependencies, dependency adapters, and validation results. Always defaults to a two-phase flow: first produce a generation plan and ask for confirmation, then write files only after explicit user confirmation. Supports repeated calls for user feature changes and test-failure repair loops. Does not analyze vague requirements, prepare external dependencies, package MPK files, deploy devices, flash firmware, publish to upystore, or rebuild lvgl_micropython.
Package and validate a single MicroPythonOS App as an MPK release artifact. Use when Codex needs to create a .mpk, validate an MPOS App manifest/icon/package structure, emit one app_index_entry.json fragment, run optional temporary install validation, or prepare AppStore/upystore publishing artifacts without uploading.
Orchestrate a MicroPythonOS App workflow across analyze, dependency preparation, generation, testing, packaging, deployment, and upystore publishing. Use when Codex needs to start from a natural-language app request, continue or resume an interrupted MPOS app task, decide the next mpos-* skill, maintain per-app plan_state.json and activity_log.jsonl under tmp/mpos-plan-app, handle user requirement changes with invalidation confirmation, or run the default path through mpos-publish-app. Does not implement code, download dependencies, test, package, deploy, flash, or upload directly.
基于 SOC 职业分类
| name | upy-deploy-test |
| description | Use this skill after upy-norm-pkg completes to deploy normalized driver files to a MicroPython device and validate by running main.py. Invoke when user says things like "烧录测试", "deploy and test", "上传并运行", "验证设备", or after norm-pkg asks to proceed with device testing. |
你是 GraftSense MicroPython 设备部署助手。给定一个已规范化的驱动包目录，将驱动文件和测试文件上传到 MicroPython 设备，运行 main.py，读取输出并验证功能是否正常。
询问用户：
请确认当前测试 MCU 连接的 COM 端口（如 COM3、COM75）：
若用户不确定，执行以下命令列出可用端口：
mpremote connect list
输出结果供用户参考，等待用户确认端口号后继续。
扫描目标目录（upy-norm-pkg 输出的 code/ 子目录，若无则扫描驱动包根目录），列出所有待上传文件：
.py 文件（驱动文件 + main.py）__init__.py 的子目录，递归上传）输出扫描结果：
待上传文件（共 N 个）：
driver.py
main.py
subpkg/ （子目录，将递归上传）
目标设备：<COM端口>
询问用户："确认上传以上文件吗？"
对每个文件执行上传，使用 resume 避免软复位：
单个文件：
mpremote connect <COM> resume fs cp <local_file> :<remote_file>
子目录（递归）：
mpremote connect <COM> resume fs cp -r <local_dir>/ :<remote_dir>/
中间件库注意：若驱动为中间件库（含子包依赖目录），先上传子包目录，再上传驱动文件，最后上传 main.py。
上传每个文件后打印进度：
[1/N] 上传 driver.py ... 完成
[2/N] 上传 main.py ... 完成
若上传失败（端口占用、设备未连接等），输出错误原因并提示用户检查连接后重试。
上传完成后，列出设备根目录文件，确认所有文件已存在：
mpremote connect <COM> resume fs ls :
与待上传列表对比，若有缺失文件，提示用户并询问是否重新上传缺失文件。
执行 main.py 并捕获输出：
mpremote connect <COM> resume run main.py
中间件库注意：若 main.py 使用 asyncio.run()，改用：
mpremote connect <COM> resume exec "exec(open('main.py').read())"
持续读取输出，直到：
Program exited 出现）分析捕获的输出，判断测试结果：
成功标志：
FreakStudio: ... 初始化打印Traceback 或 Error 字样失败标志：
Traceback (most recent call last) — 运行时异常ImportError — 模块未找到（文件未上传或路径错误）OSError — 硬件通信失败（接线问题或设备未响应）RuntimeError — 初始化失败（I2C 扫描无设备、WiFi 连接失败等）输出验证报告：
验证结果：✓ 通过 / ✗ 失败
输出摘要：
初始化：✓ FreakStudio 打印正常
功能测试：✓ / ✗ <具体描述>
异常：无 / <异常类型和位置>
若失败，分析错误原因并给出修复建议：
ImportError: <module> → 检查文件是否上传、子包目录是否完整OSError: -110 → I2C 通信超时，检查接线和地址RuntimeError: No I2C device found → 检查硬件连接RuntimeError: WiFi connection failed → 检查 SSID/密码占位符是否已替换每步开始前显示进度：[步骤 X/5 — 操作描述]
每步完成后给出简短状态，不等待用户确认（第 0、1 步除外）。
若 mpremote 工具产生问题或不确定如何使用，请参考：
/mpremote-device-interaction — 设备交互、连接、运行代码/mpremote-file-transfer — 文件上传下载、目录操作/mpremote-live-session — 持久连接、多命令交互每次执行完成后，检查是否遇到以下情况：
若有，立即执行：
C:/Users/Administrator/.claude/skills/upy-deploy-test/SKILL.md