agentleFS
wedsamuel1230wedsamuel1230/embedded-engineering-skills/skills/field-power-and-connectivity-triager/SKILL.md

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

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
  1. Distinctive:

    Use this skill when the project works on the bench but breaks when powered the way it will be used in the real world.

    line 9
  2. Distinctive:

    Use this skill when the request includes:

    line 23
  3. Very specific:

    If WiFi or radio startup is involved, open references/wifi-and-peak-current.md.

    line 37
  4. Very specific:

    If the target is Uno R4 WiFi, open ../../docs/board-support/uno-r4-family.md and keep the connectivity-side hardware split explicit.

    line 41
  5. Distinctive:

    Treat sensor instability under field power as a possible power-integrity issue until measurements say otherwise.

    line 49
  6. Distinctive:

    Do not use nominal voltage or an idle current reading as proof of peak-current safety.

    line 51
  7. Distinctive:

    Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, …

    line 73

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 workflow
  • references/wifi-and-peak-current.md - WiFi startup, brownout, and current-peak behavior
  • references/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

  1. Reproduce the split:
    • USB works
    • intended power path fails
  2. Open references/power-path-triage.md to classify the supply path.
  3. If WiFi or radio startup is involved, open references/wifi-and-peak-current.md.
  4. Capture actual measurements from references/measurement-checklist.md before assuming the failure is in user code.
  5. If the target is Uno R4 WiFi, open ../../docs/board-support/uno-r4-family.md and 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-calculator when the issue may be under-sized source capacity.
  • Pair with ota-deployment-guardian when OTA fails only under field power.
  • Pair with circuit-debugger when 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.