hardware-security
Use for authorized hardware and embedded interface security research including UART/JTAG discovery, debug pad triage, secure boot overview, and offline firmware extraction support.
Works with
--- name: hardware-security description: Use for authorized hardware and embedded interface security research including UART/JTAG discovery, debug pad triage, secure boot overview, and offline firmware extraction support. license: MIT --- # Hardware / Embedded Interface Security ## ACTION REQUIRED（读完后立刻执行） 1. `NOW`: 确认**物理接触授权**与设备归属 2. `NOW`: ESD/电源安全；默认只读探测 3. `NEXT`: 联合 firmware-pentest 做镜像分析 4. `ACT`: 外壳与调试接口识别 → consoles → 提取 ## 适用场景 - UART / JTAG / SWD 调试口发现 - 启动日志、root shell、引导打断 - 配合拆机提取 Flash - 安全启动/加密 Flash 的可行性评估（非破坏性优先） ## 工作流 ```text □ 拆解授权设备；拍照标注测试点 □ 万用表找 GND/VCC/TX/RX；逻辑电平 1.8/3.3/5V □ USB-TTL 只读日志；记录波特率 □ JTAG：枚举 IDCODE；评估是否锁定 □ 提取镜像 → 交接 firmware-pentest / ghidra ``` ## 工具链 | 工具 | 用途 | |------|------| | USB-TTL / logic analyzer | UART | | J-Link / CMSIS-DAP | 调试 | | bus pirate / flipper（实验室） | 多协议 | | binwalk / flashrom | 提取 | ## 参考 - `references/debug-interface-triage.md` - `../firmware-pentest/` `../ot-ics/` ## 路由上下文 **上游**: MASTER R34 **MUST NOT**: 未授权拆机/损坏他人设备 ## 任务完成自检 - [ ] 是否记录接口电平与引脚图？ - [ ] 镜像是否哈希保全？ - [ ] Checklist？
More Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
