field-power-and-connectivity-triager
Skill28 starsChanged 32 days agoMITView on GitHub
Use when maker projects work on USB bench power but fail on their intended supply path, especially for WiFi or sensor-heavy boards such as ESP32, including brownout, current-peak, regulator, and wiring-path diagnosis.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- wedsamuel1230/arduino-skillsword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- wedsamuel1230/arduino-skills★ 28100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository48 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/arduino-skills.mdcCursor rule
- cli-creatorSkill
- plugin-creatorSkill
- skill-creatorSkill
- arduino-cli-skillSkill
- arduino-code-generatorSkill
- arduino-project-builderSkill
- arduino-serial-monitorSkill
- arduino-workflow-routerSkill
- battery-selectorSkill
- board-selectionSkill
- board-supportSkill
- bom-generatorSkill
- boot-flash-recoverySkill
- bus-debuggingSkill
- circuit-debuggerSkill
- code-review-facilitatorSkill
- datasheet-interpreterSkill
- embedded-build-workflowSkill
- embedded-project-loopSkill
- enclosure-designerSkill
- error-message-explainerSkill
- fault-forensicsSkill
- freertos-patternsSkill
- hardware-tddSkill
- i2c-bringup-diagnosticianSkill
- library-selectionSkill
- memory-budgetingSkill
- memory-timing-debuggingSkill
- mermaid-diagram-generatorSkill
- micropython-developmentSkill
- non-blocking-patternsSkill
- ota-deployment-guardianSkill
- pico-sdk-developmentSkill
- pin-assignmentSkill
- power-budget-calculatorSkill
- probe-debuggingSkill
- readme-generatorSkill
- realtime-control-designSkill
- sensor-calibration-workbenchSkill
- sensor-signal-filteringSkill
- stm32-developmentSkill
- usb-debuggingSkill
- wireless-telemetrySkill
- wiring-safety-checkSkill
- zephyr-developmentSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill when the project works on the bench but breaks when powered the way it will be used in the real world.
- Distinctive: line 23
Use this skill when the request includes:
- Very specific: line 37
If WiFi or radio startup is involved, open references/wifi-and-peak-current.md.
- Very specific: line 41
If the target is Uno R4 WiFi, open ../../docs/board-support/uno-r4-family.md and keep the connectivity-side hardware split explicit.
- Distinctive: line 49
Treat sensor instability under field power as a possible power-integrity issue until measurements say otherwise.
- Distinctive: line 51
Do not use nominal voltage or an idle current reading as proof of peak-current safety.
- Distinctive: line 73
Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Field Power And Connectivity Triager
Use this skill when the project works on the bench but breaks when powered the way it will be used in the real world. Apply it to any board or load whose voltage/current path is uncertain; the ESP32 examples are common cases, not a claim that the same limits apply to every board.
Resources
references/power-path-triage.md- USB vs VIN vs 3V3 diagnosis workflowreferences/wifi-and-peak-current.md- WiFi startup, brownout, and current-peak behaviorreferences/measurement-checklist.md- what to measure before blaming the code../../docs/board-support/uno-r4-family.md- Uno R4 family board caveats where relevant
When to Use
Use this skill when the request includes:
- "works on USB but not on my power supply"
- WiFi connects on the bench but not in deployment
- field-only resets, brownouts, or sensor instability
- suspected regulator or wiring-path weakness
- battery, VIN, or 3V3 supply-path questions
Workflow
- Reproduce the split:
- USB works
- intended power path fails
- Open
references/power-path-triage.mdto classify the supply path. - If WiFi or radio startup is involved, open
references/wifi-and-peak-current.md. - Capture actual measurements from
references/measurement-checklist.mdbefore assuming the failure is in user code. - If the target is Uno R4 WiFi, open
../../docs/board-support/uno-r4-family.mdand keep the connectivity-side hardware split explicit.
Core Rules
- "Works on USB" is evidence about the power path, not proof the code is sound.
- WiFi startup current peaks are first-class suspects on ESP32-class boards.
- Diagnose the supply path before tuning network code blindly.
- Treat sensor instability under field power as a possible power-integrity issue until measurements say otherwise.
- Do not use nominal voltage or an idle current reading as proof of peak-current safety; compare the measured load path with the board and component limits.
Verification
- Confirm the failure reproduces only on the intended power path.
- Confirm voltage and current conditions during the failing phase, not only at idle.
- Confirm whether the failure happens at boot, during WiFi association, or later under load.
- Confirm whether the same sketch behaves consistently once the power path is corrected.
Integration
- Pair with
power-budget-calculatorwhen the issue may be under-sized source capacity. - Pair with
ota-deployment-guardianwhen OTA fails only under field power. - Pair with
circuit-debuggerwhen the board wiring itself is suspect.
Shared Output Contract
Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, known limitations, and recovery/security notes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

