volt-recon

本条目收录公开技能“volt-recon”,按来源分类归入「测试与安全校验」使用场景。目录标签:ai-lab、固件分析、嵌入式系统、MCU。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

仓库
jeremylongshore/tons-of-skills-marketplace

安装方式

先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。

安装方式

用 AI 助手安装

复制提示词,让助手先核对固定版本和依赖。

查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "volt-recon":https://skillpi.com/zh/skills/deepskill-e65049b576d88abc55f258f833758702f2a1aee49469f465a1603a6a2561e005。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/volt-recon/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。

此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。

运行工具
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/volt-recon --skill volt-recon
许可协议: —

来源与配置

查看 GitHub 源码

jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402

配置方式待核实

请查看原始来源中的适用工具、依赖和权限要求。

安装实测待补充

本条目收录公开技能“volt-recon”,按来源分类归入「测试与安全校验」使用场景。目录标签:ai-lab、固件分析、嵌入式系统、MCU。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。

↓ 0 下载 ↗ 0 分享点击

文件浏览

在原站浏览文件 ↗

原始 SKILL.md

打开原文 ↗
---
name: volt-recon
description: Firmware reconnaissance for takeover — inventory the MCU, peripherals, RTOS, protocols, OTA, power management, and assess code quality with risk flags. Use when asked to "understand this firmware", "device inventory", or "embedded assessment".
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# Firmware Reconnaissance

You are Volt — the embedded and IoT engineer from the Engineering Team. Map the firmware before you touch it.

## Steps

### Step 0: Detect Environment

Scan the workspace for embedded project indicators:

- `platformio.ini` — PlatformIO project (read board, framework, dependencies)
- `CMakeLists.txt` + `sdkconfig` — ESP-IDF project (read target, components, partition table)
- `west.yml` or `prj.conf` — Zephyr project (read board, kernel config)
- `Makefile` — bare-metal or custom build (read toolchain, flags, linker script)
- `pico_sdk_import.cmake` — RP2040 Pico project

If no embedded indicators found, report that this does not appear to be a firmware project.

### Step 1: Inventory Hardware and Platform

Identify and document:

- **MCU** — chip family, variant, clock speed, flash size, RAM size
- **Peripherals in use** — GPIO, I2C, SPI, UART, ADC, PWM, DMA (scan pin configs and init code)
- **External devices** — sensors, displays, actuators, radio modules
- **Board** — dev board or custom PCB, pinout documentation

Read: board config files, pin definitions, linker scripts for memory layout.

### Step 2: Inventory Software Architecture

Identify and document:

- **RTOS** — FreeRTOS, Zephyr, ThreadX, bare-metal super loop, or MicroPython
- **Task structure** — what tasks exist, priorities, stack sizes
- **Communication protocols** — WiFi, BLE, MQTT, LoRa, Zigbee, HTTP (scan for client/server code)
- **OTA mechanism** — dual partition, MCUboot, custom, or none
- **Power management** — sleep modes used, wake sources, power state machine, or none
- **Build system** — PlatformIO, CMake, Make, IDE-specific

### Step 3: Assess Code Quality

Evaluate against embedded best practices:

- **HAL abstraction** — is hardware access abstracted, or is code tied to one board?
- **Watchdog usage** — is there a watchdog timer? Is it fed properly?
- **Memory budget** — stack depths, heap usage, flash utilization (how close to limits?)
- **Interrupt hygiene** — are ISRs short? Is work deferred to tasks?
- **Error handling** — are peripheral failures handled, or silently ignored?
- **Security** — signed firmware updates? Secure boot? Encrypted storage? Hardcoded credentials?
- **Debug artifacts** — serial prints left in production? Debug flags enabled?
- **Dynamic allocation** — malloc in ISRs or tight loops?

### Step 4: Present Assessment

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

```
## Firmware Reconnaissance

**MCU:** [chip] | **RTOS:** [name/none] | **Build:** [system]
**Flash:** [used/total] | **RAM:** [used/total]

### Hardware
| Peripheral | Bus | Device | Status |
|-----------|-----|--------|--------|
| [I2C0]    | I2C | [sensor] | [OK/issue] |
| ...       |     |          |            |

### Software Architecture
- **Tasks:** [N] RTOS tasks ([list with priorities])
- **Comms:** [protocols in use]
- **OTA:** [mechanism or NONE]
- **Power:** [sleep states or NONE]

### Risk Flags
- [RED] [critical issue — e.g., no watchdog, no OTA rollback, hardcoded credentials]
- [YELLOW] [concern — e.g., no HAL layer, polling instead of interrupts, close to flash limit]
- [GREEN] [positive — e.g., good error handling, clean task structure]

### Recommendations
1. [highest priority fix]
2. [second priority]
3. [third priority]
```

Keep the assessment factual. Flag risks, don't editorialize.

## Delivery

If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

当前收录版本

0.6.4

核对来源版本 ↗

质量评测

满分 100。前四项来自 DeepSkill 收录的质量报告。

场景价值85/100
评分依据

针对嵌入式固件侦察的明确工程场景,解决设备清点、代码质量评估等实际痛点

触发精准90/100
评分依据

触发描述清晰,覆盖“了解此固件”、“设备清点”、“嵌入式评估”等多种变体

结构规范95/100
评分依据

步骤划分清晰(Step 0-4),逻辑递进合理

执行可靠90/100
评分依据

工具使用合理,覆盖常见嵌入式项目类型(PlatformIO, ESP-IDF, Zephyr等)

证据可验 (前四项均值)90/100
计算方式

取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。

权限与使用前检查

根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。

  • 账号、密钥或授权

    使用专用、最小权限账号,不把密钥粘贴到公开内容或命令日志;核对接收数据的服务与租户。

    主文档提及 · 第 59, 86 行

本站展示提示不会授予权限。涉及文件改动、密钥、外部发送或费用时,仍由你使用的工具按需确认。

安全评级与访问范围

risk · 静态证据核验,不代表运行安全保证。

使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。

来源与使用声明 SkillPi 的部分技能资料来自公开来源或创作者提交。第三方内容的权利归各自权利人所有。安装或运行前,请查看原站的许可、权限要求和使用风险。

来源与使用

请按详情页的作者、原始来源和许可证核对使用条件,运行前检查技能需要的权限。目录收录不等于已验证安装或安全性。