field-power-and-connectivity-triager — Claude Code skill for power diagnosis
field-power-and-connectivity-triager is a Claude Code skill that investigates power and connectivity faults when a board works over USB but fails on its intended supply. It checks voltage drops, current peaks, regulators, and wiring.
MIT 113 installs ★ 33 updated 2026-10-15
npx skills add wedsamuel1230/embedded-engineering-skills --skill field-power-and-connectivity-triager -a claude-codeWhat field-power-and-connectivity-triager does
The skill investigates boards or sensors that run on USB but reset, lose WiFi, or behave erratically on battery, VIN, or 3V3 power. It helps distinguish a supply-path fault from a code issue and locate whether the failure happens at boot, during WiFi association, or under load.
Its workflow first checks that the failure is limited to the intended supply path. It then draws on guides for supply-path diagnosis, WiFi startup current, and measurement; Uno R4 WiFi cases also get a separate look at the connectivity hardware. Voltage and current readings should cover the failing phase, not just idle conditions. The skill can be paired with power-budget-calculator for undersized source capacity or circuit-debugger when wiring is suspect.
What it helps with
- trace failures that appear when switching from USB to battery or VIN
- check whether WiFi startup current triggers ESP32 resets
- investigate voltage drops or a weak regulator
- separate sensor instability from a code fault
- identify when resets or connectivity failures occur
Example prompts for the agent
- The board works over USB but resets on battery power. Trace the supply path.
- WiFi connects on the bench but fails after deployment. Check for voltage drops and current peaks.
- Sensors become unstable on VIN. Give me a measurement plan.
How to install field-power-and-connectivity-triager
1Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill field-power-and-connectivity-triager -a claude-code2Manually: put the files in place
~/.claude/skills/field-power-and-connectivity-triager/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/field-power-and-connectivity-triager/
1Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill field-power-and-connectivity-triager -a codex2Manually: put the files in place
.agents/skills/field-power-and-connectivity-triager/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill field-power-and-connectivity-triager -a cursor2Manually: put the files in place
.cursor/skills/field-power-and-connectivity-triager/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wedsamuel1230/embedded-engineering-skills skills/field-power-and-connectivity-triager2Manually: put the files in place
.github/skills/field-power-and-connectivity-triager/SKILL.md1Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill field-power-and-connectivity-triager -a gemini-cli2Platform CLI
gemini skills install https://github.com/wedsamuel1230/embedded-engineering-skills --path skills/field-power-and-connectivity-triagerManually: put the files in place
.devin/skills/field-power-and-connectivity-triager/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wedsamuel1230/embedded-engineering-skills --skill field-power-and-connectivity-triager -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about field-power-and-connectivity-triager
How do I install field-power-and-connectivity-triager in Claude Code?
Run npx skills add wedsamuel1230/embedded-engineering-skills --skill field-power-and-connectivity-triager -a claude-code. The skill file is placed at ~/.claude/skills/field-power-and-connectivity-triager/SKILL.md.
What does field-power-and-connectivity-triager do?
It helps diagnose power and connectivity faults that occur on the intended supply but not over USB. Its checks cover voltage, peak current, regulators, and wiring.
How does it investigate WiFi-related power failures?
It directs the diagnosis toward measurements during WiFi startup and the failing phase, rather than relying only on idle readings. On ESP32-class boards, radio startup current peaks are treated as a possible cause.
Source text
SKILL.md · MIT
---
name: field-power-and-connectivity-triager
description: 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.
metadata: {triggers: "brownout, power path, current peak, regulator, WiFi failure"}
---
# 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](../../docs/arduino-skill-contract.md):
state assumptions, required tools and versions, implementation steps,
tests/evidence by proof stage, known limitations, and recovery/security notes.
© wedsamuel1230 · MIT · wedsamuel1230/embedded-engineering-skills