STOP - Read before ANY tool call
Read _shared/skill-boilerplate.md first. It holds the guardrails read, the session gate rule, the user sim rule, the one-step rule, the gate check, and the user chat language rule. The steps below are skill-specific only.
Skill: micropython-developer
Trigger
Negative signal: applies as defined in _shared/skill-boilerplate.md; the skill-specific signals are listed below.
Invoke for Python code that runs as MicroPython firmware on an identified ESP32
or ESP8266 device. A .py extension, an ESP32-family name, or a board label
alone is not enough to select this skill.
Outcome
Provide a bounded, evidence-aware firmware workflow for the selected
MicroPython runtime and target. Keep device execution, device deployment, and
host-side tooling or tests distinct. Treat ESP32 and ESP8266 as the initial
first-class target families without assuming that their ports, firmware builds,
boards, or available modules share one uniform API or deployment capability.
Lazy-load
| When |
Path |
| Shared embedded context and evidence |
{{TOOLKIT_ROOT}}/skills/_shared/embedded-guidelines/README.md, target-and-provenance.md, validation-and-reporting.md |
| Resource and constrained-runtime questions |
{{TOOLKIT_ROOT}}/skills/_shared/embedded-guidelines/resources-and-communication.md |
| Security or dependency questions |
{{TOOLKIT_ROOT}}/skills/_shared/embedded-guidelines/security-and-dependencies.md |
| ESP32 reference |
https://docs.micropython.org/en/latest/esp32/quickref.html |
| ESP8266 reference |
https://docs.micropython.org/en/latest/esp8266/quickref.html |
| MicroPython library availability |
https://docs.micropython.org/en/latest/library/index.html |
| Invocation context |
{{TOOLKIT_ROOT}}/skills/_shared/sdd-artifacts/INVOCATION-CONTEXTS.md (IC-DIRECT-ORCHESTRATED) |
| Contract provenance |
{{TOOLKIT_ROOT}}/skills/_shared/sdd-artifacts/CONTRACT-PROVENANCE.md (CP-AGREED-VS-INVENTED) |
Do not preload unrelated framework packs or the whole memory bank. Load
platform-specific references only after the runtime, port, firmware, board,
and validation boundary are identified.
Never by default: do not preload port references, firmware-specific API
guides, deployment procedures, security material, or the memory bank before
the runtime, port, firmware, board, and validation boundary are known.
Process
0. Establish and qualify the device context
Before making a target-qualified recommendation, create a context record with
all of these fields:
| Field |
Required evidence |
Boundary when missing |
| Board/module |
exact model, variant, revision, and architecture from board documentation or operator evidence |
do not choose pins, peripherals, limits, or deployment behavior |
| Port |
esp32 or esp8266, including any port-specific variant named by the firmware |
do not generalize between ESP32 and ESP8266 |
| Firmware |
MicroPython version, build/source provenance, and relevant configuration |
do not treat latest documentation as proof for the installed build |
| API/module source |
port quick reference, version-matched library reference, or project dependency metadata |
report the capability as unknown or pending confirmation |
| Hardware source |
datasheet, board specification, measured result, or named project evidence |
do not infer electrical, memory, radio, or storage facts from the family name |
| Validation boundary |
host-only, compile-only, device runtime, or HIL |
do not report a stronger result than the exercised boundary |
For every recommendation, explicitly separate three workstreams:
- Host tooling/tests: commands and tests executed by CPython on the host;
- Deployment: an operation that changes the device, only when an
authoritative procedure for the exact board/firmware is identified;
- Device execution: REPL or runtime behavior observed on the named board,
revision, and firmware.
If a missing field could change the API, module, resource, or deployment answer,
ask for it before recommending a target-dependent operation. Do not infer it
from the file extension, board family, or a nearby ESP32/ESP8266 example.
Use the narrowest state supported by evidence: confirmed, assumed,
planned, implemented, or verified. A reference page or project plan can
support a planned recommendation; it does not prove that a particular firmware
build exposes or verifies that capability.
0.1 Select authoritative references before using an API or module
Select references by the recorded port and firmware version. The initial
reference map is:
| Claim |
Required reference |
| ESP32 port API/peripherals |
MicroPython ESP32 quick reference, matched to the selected documentation/release when available |
| ESP8266 port API/peripherals |
MicroPython ESP8266 quick reference, matched to the selected documentation/release when available |
| Cross-port module availability |
MicroPython library reference, checked against the selected firmware build |
| Board pins, electrical limits, and revision differences |
the exact board/module documentation or datasheet; a port quick reference is not a board pinout |
| Deployment or recovery |
the exact firmware release/project procedure for the named board; do not substitute a generic flashing or OTA recipe |
Record the URL or document identifier and the version/date used. The latest
pages are navigation aids, not evidence that an installed older build has the
same API. If the source covers a different port, board revision, or build,
label the guidance pending confirmation and do not present it as supported.
0.2 Qualify REPL, deployment, and resource guidance
- REPL: identify the board/revision and firmware build before suggesting
introspection or runtime checks. Use only commands documented for that exact
runtime; a successful host import or a REPL transcript from another build is
not device evidence.
- Deployment: state whether the action is host preparation, a device-changing
deployment action, or post-deployment device validation. Do not invent flash,
erase, recovery, or OTA steps. If the authoritative procedure is not known,
report deployment as
pending confirmation and request the target-qualified
procedure.
- Hardware and resources: tie pins, peripherals, storage, memory, timing,
power, and radio claims to the exact board/revision and firmware source or a
measurement. A successful compile or a file-size estimate does not establish
runtime headroom, timing, electrical safety, or radio behavior.
- Validation: report host-only, compile-only, device-runtime, and HIL
results separately, including the target and scenario. Never promote a
host-only or compile-only result to flashed behavior.
1. Keep the runtime boundary explicit
MicroPython firmware is device-runtime work. CPython applications, host tools,
host tests, and general Python web work remain with python-developer, even
when they communicate with a board. Do not mix host test results with device
runtime evidence.
When runtime or target information is ambiguous, request the smallest missing
context before recommending runtime-dependent syntax, modules, APIs, or
deployment operations.
2. Scope the initial target
This skill treats ESP32 and ESP8266 MicroPython firmware as its initial
first-class coverage. Other MicroPython ports, Linux-based single-board
computers, native ESP-IDF, Arduino C/C++, and CPython-on-SBC applications are
outside that first-class boundary. They may be mentioned only to explain a
handoff or a boundary; they do not inherit this skill's assumptions.
For any target-qualified claim, name the applicable port, firmware, board, and
reference. If the source does not establish support for the selected
configuration, report the capability as unknown or pending confirmation.
3. Report narrowly
State what was inspected or exercised and the validation level. A host-only or
compile-only result does not establish flashed behavior, startup, peripherals,
memory headroom, timing, radio behavior, recovery, or hardware safety. Do not
claim a deployment method or device capability merely because another ESP32 or
ESP8266 configuration supports it.
3.1 Security and Arduino Cloud boundaries
- Treat TLS, certificate or hostname validation, OTA, secure storage, secure
boot, signed updates, rollback, and key-management behavior as
unknown or
pending confirmation until the exact port, firmware build, board, and
authoritative reference establish support. Encrypted transport alone is not
evidence of peer authentication.
- Keep credentials, tokens, private keys, and provisioning values outside
source, examples, REPL transcripts, logs, and evidence. Describe only the
approved provisioning boundary with non-sensitive placeholders.
- Arduino Cloud guidance is limited to firmware-side communication or
protocol integration on an identified ESP32 or ESP8266 port, firmware, and
board. Verify the exact MicroPython compatibility and required modules
before recommending it; dashboard, service, account, fleet, and other
administration are out of scope.
- Do not claim upload, OTA, device runtime, HIL, or hardware evidence unless
that exact target and validation boundary were actually exercised.
Must not
- Infer MicroPython from
.py, main.py, an ESP32/ESP8266 family name, or a board label alone.
- Treat CPython host code or tests as MicroPython device code, or route host work away from
python-developer.
- Present ESP32 and ESP8266 ports, firmware builds, boards, or modules as a uniform API surface.
- Treat another MicroPython port, Linux SBC, native ESP-IDF project, or Arduino C/C++ project as first-class coverage here.
- Invent flashing, OTA, TLS, storage, memory, or other deployment/security capabilities without target-qualified evidence.
- Put credentials, tokens, private keys, or device secrets in examples, logs, or evidence.
- Claim device runtime or HIL validation from host inspection or compilation alone.
- Ignore
IC-DIRECT-ORCHESTRATED or promote an invented gap to an agreed requirement; follow the cited invocation-context and contract-provenance rules.
- Auto-commit or auto-push.
Handoff
For port-, firmware-, REPL-, deployment-, resource-, or security-specific work,
continue only after loading the applicable shared and target references. For
CPython host tooling or tests, hand off to python-developer. For other
frameworks or ports, hand off to the matching workflow with the target evidence
recorded.
1---2name: micropython-developer3description: >-4 Implement or diagnose MicroPython device firmware for identified ESP32 or5 ESP8266 targets, with runtime and port evidence kept separate from CPython6 host tooling and tests.7metadata:8 source: https://skillmd.com/skills/tibursocampos/micropython-developer9---1011## STOP - Read before ANY tool call1213Read `_shared/skill-boilerplate.md` first. It holds the guardrails read, the session gate rule, the user `sim` rule, the one-step rule, the gate check, and the user chat language rule. The steps below are skill-specific only.1415---1617# Skill: micropython-developer1819## Trigger20**Negative signal:** applies as defined in `_shared/skill-boilerplate.md`; the skill-specific signals are listed below.2122Invoke for Python code that runs as MicroPython firmware on an identified ESP3223or ESP8266 device. A `.py` extension, an ESP32-family name, or a board label24alone is not enough to select this skill.2526## Outcome2728Provide a bounded, evidence-aware firmware workflow for the selected29MicroPython runtime and target. Keep device execution, device deployment, and30host-side tooling or tests distinct. Treat ESP32 and ESP8266 as the initial31first-class target families without assuming that their ports, firmware builds,32boards, or available modules share one uniform API or deployment capability.3334## Lazy-load3536| When | Path |37|------|------|38| Shared embedded context and evidence | `{{TOOLKIT_ROOT}}/skills/_shared/embedded-guidelines/README.md`, `target-and-provenance.md`, `validation-and-reporting.md` |39| Resource and constrained-runtime questions | `{{TOOLKIT_ROOT}}/skills/_shared/embedded-guidelines/resources-and-communication.md` |40| Security or dependency questions | `{{TOOLKIT_ROOT}}/skills/_shared/embedded-guidelines/security-and-dependencies.md` |41| ESP32 reference | `https://docs.micropython.org/en/latest/esp32/quickref.html` |42| ESP8266 reference | `https://docs.micropython.org/en/latest/esp8266/quickref.html` |43| MicroPython library availability | `https://docs.micropython.org/en/latest/library/index.html` |44| Invocation context | `{{TOOLKIT_ROOT}}/skills/_shared/sdd-artifacts/INVOCATION-CONTEXTS.md` (`IC-DIRECT-ORCHESTRATED`) |45| Contract provenance | `{{TOOLKIT_ROOT}}/skills/_shared/sdd-artifacts/CONTRACT-PROVENANCE.md` (`CP-AGREED-VS-INVENTED`) |4647Do not preload unrelated framework packs or the whole memory bank. Load48platform-specific references only after the runtime, port, firmware, board,49and validation boundary are identified.5051**Never by default:** do not preload port references, firmware-specific API52guides, deployment procedures, security material, or the memory bank before53the runtime, port, firmware, board, and validation boundary are known.5455## Process5657### 0. Establish and qualify the device context5859Before making a target-qualified recommendation, create a context record with60all of these fields:6162| Field | Required evidence | Boundary when missing |63|------|-------------------|-----------------------|64| Board/module | exact model, variant, revision, and architecture from board documentation or operator evidence | do not choose pins, peripherals, limits, or deployment behavior |65| Port | `esp32` or `esp8266`, including any port-specific variant named by the firmware | do not generalize between ESP32 and ESP8266 |66| Firmware | MicroPython version, build/source provenance, and relevant configuration | do not treat `latest` documentation as proof for the installed build |67| API/module source | port quick reference, version-matched library reference, or project dependency metadata | report the capability as `unknown` or `pending confirmation` |68| Hardware source | datasheet, board specification, measured result, or named project evidence | do not infer electrical, memory, radio, or storage facts from the family name |69| Validation boundary | `host-only`, `compile-only`, `device runtime`, or `HIL` | do not report a stronger result than the exercised boundary |7071For every recommendation, explicitly separate three workstreams:72731. **Host tooling/tests**: commands and tests executed by CPython on the host;742. **Deployment**: an operation that changes the device, only when an75 authoritative procedure for the exact board/firmware is identified;763. **Device execution**: REPL or runtime behavior observed on the named board,77 revision, and firmware.7879If a missing field could change the API, module, resource, or deployment answer,80ask for it before recommending a target-dependent operation. Do not infer it81from the file extension, board family, or a nearby ESP32/ESP8266 example.8283Use the narrowest state supported by evidence: `confirmed`, `assumed`,84`planned`, `implemented`, or `verified`. A reference page or project plan can85support a planned recommendation; it does not prove that a particular firmware86build exposes or verifies that capability.8788### 0.1 Select authoritative references before using an API or module8990Select references by the recorded port and firmware version. The initial91reference map is:9293| Claim | Required reference |94|------|--------------------|95| ESP32 port API/peripherals | [MicroPython ESP32 quick reference](https://docs.micropython.org/en/latest/esp32/quickref.html), matched to the selected documentation/release when available |96| ESP8266 port API/peripherals | [MicroPython ESP8266 quick reference](https://docs.micropython.org/en/latest/esp8266/quickref.html), matched to the selected documentation/release when available |97| Cross-port module availability | [MicroPython library reference](https://docs.micropython.org/en/latest/library/index.html), checked against the selected firmware build |98| Board pins, electrical limits, and revision differences | the exact board/module documentation or datasheet; a port quick reference is not a board pinout |99| Deployment or recovery | the exact firmware release/project procedure for the named board; do not substitute a generic flashing or OTA recipe |100101Record the URL or document identifier and the version/date used. The `latest`102pages are navigation aids, not evidence that an installed older build has the103same API. If the source covers a different port, board revision, or build,104label the guidance `pending confirmation` and do not present it as supported.105106### 0.2 Qualify REPL, deployment, and resource guidance107108- **REPL:** identify the board/revision and firmware build before suggesting109 introspection or runtime checks. Use only commands documented for that exact110 runtime; a successful host import or a REPL transcript from another build is111 not device evidence.112- **Deployment:** state whether the action is host preparation, a device-changing113 deployment action, or post-deployment device validation. Do not invent flash,114 erase, recovery, or OTA steps. If the authoritative procedure is not known,115 report deployment as `pending confirmation` and request the target-qualified116 procedure.117- **Hardware and resources:** tie pins, peripherals, storage, memory, timing,118 power, and radio claims to the exact board/revision and firmware source or a119 measurement. A successful compile or a file-size estimate does not establish120 runtime headroom, timing, electrical safety, or radio behavior.121- **Validation:** report host-only, compile-only, device-runtime, and HIL122 results separately, including the target and scenario. Never promote a123 host-only or compile-only result to flashed behavior.124125### 1. Keep the runtime boundary explicit126127MicroPython firmware is device-runtime work. CPython applications, host tools,128host tests, and general Python web work remain with `python-developer`, even129when they communicate with a board. Do not mix host test results with device130runtime evidence.131132When runtime or target information is ambiguous, request the smallest missing133context before recommending runtime-dependent syntax, modules, APIs, or134deployment operations.135136### 2. Scope the initial target137138This skill treats ESP32 and ESP8266 MicroPython firmware as its initial139first-class coverage. Other MicroPython ports, Linux-based single-board140computers, native ESP-IDF, Arduino C/C++, and CPython-on-SBC applications are141outside that first-class boundary. They may be mentioned only to explain a142handoff or a boundary; they do not inherit this skill's assumptions.143144For any target-qualified claim, name the applicable port, firmware, board, and145reference. If the source does not establish support for the selected146configuration, report the capability as unknown or pending confirmation.147148### 3. Report narrowly149150State what was inspected or exercised and the validation level. A host-only or151compile-only result does not establish flashed behavior, startup, peripherals,152memory headroom, timing, radio behavior, recovery, or hardware safety. Do not153claim a deployment method or device capability merely because another ESP32 or154ESP8266 configuration supports it.155156### 3.1 Security and Arduino Cloud boundaries157158- Treat TLS, certificate or hostname validation, OTA, secure storage, secure159 boot, signed updates, rollback, and key-management behavior as `unknown` or160 `pending confirmation` until the exact port, firmware build, board, and161 authoritative reference establish support. Encrypted transport alone is not162 evidence of peer authentication.163- Keep credentials, tokens, private keys, and provisioning values outside164 source, examples, REPL transcripts, logs, and evidence. Describe only the165 approved provisioning boundary with non-sensitive placeholders.166- Arduino Cloud guidance is limited to firmware-side communication or167 protocol integration on an identified ESP32 or ESP8266 port, firmware, and168 board. Verify the exact MicroPython compatibility and required modules169 before recommending it; dashboard, service, account, fleet, and other170 administration are out of scope.171- Do not claim upload, OTA, device runtime, HIL, or hardware evidence unless172 that exact target and validation boundary were actually exercised.173174## Must not175176- Infer MicroPython from `.py`, `main.py`, an ESP32/ESP8266 family name, or a board label alone.177- Treat CPython host code or tests as MicroPython device code, or route host work away from `python-developer`.178- Present ESP32 and ESP8266 ports, firmware builds, boards, or modules as a uniform API surface.179- Treat another MicroPython port, Linux SBC, native ESP-IDF project, or Arduino C/C++ project as first-class coverage here.180- Invent flashing, OTA, TLS, storage, memory, or other deployment/security capabilities without target-qualified evidence.181- Put credentials, tokens, private keys, or device secrets in examples, logs, or evidence.182- Claim device runtime or HIL validation from host inspection or compilation alone.183- Ignore `IC-DIRECT-ORCHESTRATED` or promote an `invented` gap to an agreed requirement; follow the cited invocation-context and contract-provenance rules.184- Auto-commit or auto-push.185186## Handoff187188For port-, firmware-, REPL-, deployment-, resource-, or security-specific work,189continue only after loading the applicable shared and target references. For190CPython host tooling or tests, hand off to `python-developer`. For other191frameworks or ports, hand off to the matching workflow with the target evidence192recorded.