claude

embedded

Skills for embedded, IoT and hardware-adjacent software: safe firmware updates and fleet rollouts, provisioning and device trust, device clocks and telemetry, field-failure triage, firmware code review, hard faults, RTOS concurrency and watchdogs, brick recovery, power and sleep bugs, memory and flash budgets, and bus, radio and MQTT debugging.

0 on GitHubby Serhii ZolotovMITupdated 2 days agodevelopment
/

Plugin embedded from marketplace greenblacked-ai in greenblacked/AI. Commands read from the repo's manifest — 2 days ago.

What it installs

Skills (20)

  • ble-connection-debug

    Fix Bluetooth Low Energy peripherals that drop, stall or refuse to reconnect. Capture on air (nRF Sniffer into Wireshark) beside the phone's log before reading code. Check connection interval, peripheral latency and supervision timeout against their own constraint (timeout must exceed twice the inte

  • brick-recovery

    Revive an unresponsive board without destroying what cannot be replaced, and make the next one recoverable: classify what is alive first (supply current on a bench supply, clock, ROM-bootloader banner on UART, SWD or JTAG answering), climb from least to most destructive (recovery button combination,

  • device-clock-handling

    Get time right on devices whose clocks drift or wrap: keep two clocks, a monotonic tick since boot that drives every timeout and interval and wall-clock UTC used only for timestamps; stamp records with boot id plus monotonic time and backfill wall time once synced; compare ticks with unsigned subtra

  • device-telemetry-design

    Decide what a device reports so field problems stay diagnosable inside a data and battery budget: fix bytes per day per device from plan cost and radio energy, then spend it on a minimum (reset reason and count, uptime, build id, fault record with PC, LR and CFSR, update state, heap and stack waterm

  • device-trust-anchors

    Plan certificate lifetimes, trust roots and clocks for devices that will live a decade: size lifetimes by field life plus shelf life, ship at least two trust anchors (the current one and an offline-held spare) so rotation is a configuration push, pin to a private intermediate rather than a public le

  • field-failure-triage

    Work out why deployed units are failing, going silent or coming back, and decide containment: read flash, faults and battery state of a returned unit before reflashing; scope a silent cohort by last-seen (a step at one timestamp points at cloud, certificate, DNS or release, so check broker and auth

  • fieldbus-debug

    Debug CAN, RS-485 and Modbus links on machines and sites. CAN: with power off measure CANH to CANL (about 60 ohms means two terminators), match bit rate and sample point on every node, read the transmit and receive error counters, recover from bus-off with backoff, and decode traffic with the DBC fi

  • firmware-code-review

    Review a change to C or C++ firmware for the defects that kill devices in the field, ordered by lethality: everything an ISR touches (volatile is not atomic, multi-byte reads tear on narrow cores, no blocking, allocation or printf), every hardware wait with a timeout and an exit, tick arithmetic tha

  • flash-storage-durability

    Make settings and logs kept in flash or EEPROM survive power cuts and wear: classify each datum by write rate and tolerable loss, compute a wear budget (endurance times erasable units over writes per day times erases per write, at least three times product life), never update in place (two slots wit

  • fleet-provisioning

    Give every manufactured device its own factory identity and an auditable record. Generate the key pair inside the secure element or crypto block and export only a CSR; never flash a shared key or keep a private key on the line PC. Run a fixed station flow (firmware, reversible readout protection, ke

  • hard-fault-triage

    Decode a Cortex-M HardFault or field crash into a source line: archive the ELF and map of every release keyed by build id, capture the stacked R0-R3, R12, LR, PC and xPSR in a handler that picks MSP or PSP from the EXC_RETURN bit, read CFSR, HFSR and MMFAR/BFAR only when their valid bits are set, cl

  • memory-footprint-budget

    Keep firmware inside flash and RAM with headroom for the next update: treat the linker map as the source of truth, diff per-section and per-module sizes against main on every pull request and fail at a budget of about 85 to 90 per cent, derive worst-case stack depth per task from -fstack-usage and t

  • mqtt-session-debug

    Diagnose MQTT devices that flap, miss messages or stampede the broker. Check in order: duplicate client ids (two units sharing one id take each other's session over in a loop), keepalive against the shortest NAT or cellular idle timeout (set near half), clean versus persistent session and expiry, Qo

  • ota-fleet-rollout

    Run a staged firmware campaign across devices that check in rarely and cannot be recalled: rings sized as device counts across every hardware revision, carrier and region (lab, staff, 0.1 per cent, 1, 10, 50, 100), bake time counted in check-in intervals of the slowest cohort, halt signals written f

  • ota-update-safety

    Design or audit the device-side firmware update so a power cut or a bad image never bricks a unit: list every flash write in the update path and cut power at each with a relay harness before shipping, write to the inactive slot, verify hash and signature over the whole image after the last write, fl

  • rtos-concurrency-hunt

    Find the cause of corruption, deadlock, starvation or lost events in RTOS firmware. Map the symptom to a class: unprotected shared data, a non-ISR-safe call from an interrupt or a stack overflow for corruption; a lock-order cycle, a mutex held across a queue wait or priority inversion through a bina

  • serial-bus-debug

    Bring up a UART, I2C or SPI link that returns garbage, NACKs or reads all 0xFF: check electrical before logical (power, common ground, logic levels, RS-232 versus TTL), put a logic analyser with a protocol decoder on the wires before changing code, compute UART baud error from the clock divider, sco

  • sleep-current-hunt

    Find why a battery device draws milliamps asleep or dies in months instead of years, and estimate battery life from a measured trace: measure with a current-ranging power profiler or a shunt and scope, never a bench multimeter, integrate charge over a full cycle, rank slices by charge rather than pe

  • sleep-wake-bug-hunt

    Fix devices that miss wakeups, hang on wake, or lose state after deep sleep: classify first as a lost wakeup (event lands between the flag check and sleep; check with interrupts masked and sleep on WFI), a wake-source fault (wrong edge or level, flag not cleared, instant re-wake loop) or a retention

  • watchdog-design

    Design or fix a watchdog so it recovers real hangs without masking them: feed it from exactly one place, only after every monitored task has checked in with a progress token inside the window, never from an ISR or a lone idle hook, set the timeout from measured worst-case loop time with a 2x to 3x m

Subagents (1)

  • linker-map-reader

    Read a firmware build's linker map, per-object -fstack-usage files and bloaty or size reports, and return flash and RAM use by region against budget, the per-module growth against the base revision, and the worst-case stack per task, so the map itself never enters the caller's context. Use when a fi

View source on GitHub

More from greenblacked/AI

All 29 plugins →

gamedev

claude

Skills for making games: build a playable prototype and take it to a finished game, hold a frame budget on the hardware you are shipping to, choose a multiplayer authority model and make it survive latency, tune numbers against telemetry instead of taste, and keep an asset pipeline from eating the build.

39 skills · 2 commands · 2 agents

0

security

claude

Skills for the defensive side of shipping software: review a change for the vulnerability classes that actually get exploited, reduce who can do what toward least privilege without breaking production, rotate or contain a credential, harden a container image and keep checking it, read a Terraform plan for what it destroys, preserve evidence and build an intrusion timeline after a compromise, respond to credential stuffing, write and test detection rules, prove tenant isolation, handle vulnerability reports from outside researchers, and reverse engineer the binaries, managed CIL assemblies, APK packages, packaged apps, firmware and WebAssembly you are authorised to examine — including de-bloating a smart-TV or streaming device you own.

31 skills · 2 commands · 5 agents

0

coding

claude

Skills for the daily loop of changing code: review a diff for the defects that actually break production, debug a failure down to a proven cause, decide what to test before writing tests, restructure code without changing behaviour, orient yourself in an unfamiliar codebase, review a regex for catastrophic backtracking, write documentation that stays true, scaffold new production-ready code, design an API you can still evolve, land a dependency upgrade, build a website, and author a skill that fires when it should.

29 skills · 1 command · 5 agents

0

Skills for keeping a running system alive: triage a red pipeline to its real cause, get a broken Kubernetes workload back before diagnosing it, design alerts where every page is actionable, instrument a service so the next incident is answerable, write the runbook a stranger can follow at 3am, rehearse failure on purpose, plan for load before it arrives, and find out why the bill grew.

19 skills · 2 commands · 7 agents

0

manager

claude

Skills for engineering leadership: take over a team and audit what you inherited, record decisions, write status updates, run postmortems and incident comms, read delivery health, review on-call load, design the team cadence, a reorganisation and goals, make the case for headcount or for paying down tech debt, map team skills and single points of knowledge, plan onboarding, hire, benchmark pay, evaluate vendors, handle retention, growth reviews, improvement plans and difficult conversations, and assess how a team uses AI. Also ships two subagents, for reading contracts and synthesising feedback, and two commands.

22 skills · 2 commands · 2 agents

0

Skills for code that runs on a user's browser or phone: field performance, hydration, memory, version skew, service workers, CSP and Safari bugs, dates and locales, crashes, hangs, startup, battery, bad networks, on-device migrations, deep links, pushes and app size.

22 skills · 1 agent

0

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.

5 commands

HKUDS/CLI-Anything 58,665

Automates browser interactions for web testing, form filling, screenshots, and data extraction

12 skills

vercel-labs/agent-browser 50,373

Use Alibaba Open Code Review from local Codex.

2 skills

alibaba/open-code-review 50,068

slidev

claude

Claude Code skill for creating and presenting Slidev slidedecks

1 skill

slidevjs/slidev 49,452

Maintain embedded?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins29 plugins