boot-flash-recovery
Skill28 starsChanged 30 days agoMITView on GitHub
Diagnose embedded boot, flash layout, image validation and reset loops with a non-destructive recovery path. Use when requests involve bootloader/application offsets, vector tables, partitions, bad firmware or a device that no longer starts.
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
- bus-debuggingSkill
- circuit-debuggerSkill
- code-review-facilitatorSkill
- datasheet-interpreterSkill
- embedded-build-workflowSkill
- embedded-project-loopSkill
- enclosure-designerSkill
- error-message-explainerSkill
- fault-forensicsSkill
- field-power-and-connectivity-triagerSkill
- 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
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
Read the shared embedded contract and keep source/build, device and physical evidence separate.
- Distinctive: line 12
Read recovery decision path.
- Very specific: line 20
Check supply/reset/boot straps and host port/probe ownership separately.
- Very specific: line 28
Use probe-debugging for target access, usb-debugging for enumeration and ota-deployment-guardian for update-slot/persistent-schema …
≈ “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
Boot and Flash Recovery
Read the shared embedded contract and keep source/build, device and physical evidence separate.
Read recovery decision path. Preserve original boot/reset logs and identify board/chip, boot chain, image format, flash map, security state and intended firmware before proposing a write. Readout may be restricted; an empty or denied read is not proof the flash is erased.
Inspect available ELF/bin/hex/UF2 metadata offline. Compare partition/linker addresses, vector-table placement, slot limits and image headers against the exact target. File extension and binary length do not establish a load address. Check supply/reset/boot straps and host port/probe ownership separately.
Choose the least destructive recovery supported by that exact board. Protect calibration, provisioning, user files and security keys. Mass erase, unprotect, factory reset, fuse changes and bootloader replacement have distinct effects; never use them as an automatic first repair. A failed upload does not authorize removing protection or bypassing signature/anti-rollback checks.
Use probe-debugging for target access, usb-debugging for enumeration and
ota-deployment-guardian for update-slot/persistent-schema compatibility.
Deliver the preservation plan, exact artifact/target/address, authorized write
steps if any, and separate verification after reset.
See platform coverage for the exact tested combination. A source procedure is not a claim that every target was tested.
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.