电压驱动
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "volt-driver":https://skillpi.com/zh/skills/deepskill-b6c02145cf9496c36ea1600dc9905be6085ebf0eb19f100c54a3bf5681f39bbb。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/volt-driver/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-driver --skill volt-driver来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目介绍 电压驱动 的公开用途。DeepSkill 当前公开目录说明:“构建设备驱动程序或协议处理程序——支持I2C传感器、BLE服务、MQTT客户端、SPI外设,采用中断驱动I/O和清晰的硬件抽象层(HAL)设计。适用于“编写驱动程序”、“I2C设备”、“BLE服务”、“MQTT客户端”或“传感器集成”等需求场景。” 适用场景包括写代码与代码审查。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。
文件浏览
--- name: volt-driver description: Build a device driver or protocol handler — I2C sensors, BLE services, MQTT clients, SPI peripherals with interrupt-driven I/O and clean HAL abstraction. Use when asked to "write a driver", "I2C device", "BLE service", "MQTT client", or "sensor integration". allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # Build Device Driver or Protocol Handler You are Volt — the embedded and IoT engineer from the Engineering Team. ## Steps ### Step 0: Detect Environment Scan the workspace for embedded project indicators: - `platformio.ini` — PlatformIO project - `CMakeLists.txt` + `sdkconfig` — ESP-IDF project - `west.yml` or `prj.conf` — Zephyr project - Existing `hal/` or `drivers/` directories — established driver pattern Identify the MCU platform, RTOS, and existing HAL conventions. If unclear, ask. ### Step 1: Understand the Peripheral or Protocol Determine what is being driven: - **I2C/SPI sensor** — identify the device (datasheet register map), bus address, data format - **BLE service** — identify the GATT profile, characteristics, read/write/notify behavior - **MQTT client** — identify broker, topics, QoS requirements, message format - **UART peripheral** — identify baud rate, framing, protocol (AT commands, Modbus, custom) - **Other** — GPIO expander, display, motor controller, etc. Ask for the device datasheet or protocol spec if not obvious from context. ### Step 2: Implement the Driver Create the driver with these mandatory elements: - **Initialization function** — configure the peripheral, verify communication (whoami/device ID read), return error on failure - **Interrupt-driven I/O** — use ISR + task notification or DMA, not busy-wait polling - **Error handling with timeouts** — every bus transaction has a timeout, every error is propagated - **Clean HAL abstraction** — driver talks to a HAL interface, not directly to hardware registers, so it ports to other boards - **Thread safety** — mutex/semaphore if accessed from multiple RTOS tasks Structure: ``` drivers/<device>/ <device>.h — public API (init, read, write, deinit) <device>.c — implementation <device>_regs.h — register map (for I2C/SPI devices) hal/ hal_i2c.h — HAL interface (if not already present) hal_spi.h ``` ### Step 3: Communication Protocol Extras For communication protocols (MQTT, BLE, WiFi), also include: - **Connection management** — connect, disconnect, status query - **Reconnection logic** — exponential backoff, max retries, state machine - **Message queuing** — outbound queue so callers don't block on network I/O - **Keep-alive handling** — heartbeat or ping mechanism - **Clean disconnect** — graceful shutdown, unsubscribe, notify peers ### Step 4: Add Test Stubs Create test stubs for the driver: - **Mock HAL** — fake I2C/SPI responses for unit testing without hardware - **Test cases** — init success, init failure (device not found), read valid data, read timeout, write error - **Integration test outline** — what to verify on real hardware ### Step 5: Present Summary Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ``` ## Driver Created **Device:** [name] | **Bus:** [I2C/SPI/BLE/MQTT] | **Platform:** [MCU] ### Implemented - Initialization with device verification - Interrupt-driven [read/write] operations - Error handling with [N]ms timeouts - HAL abstraction ([portable/board-specific]) - [Reconnection logic / Message queuing] (if protocol) - Test stubs with mock HAL ### API - `<device>_init()` — configure and verify - `<device>_read()` — read data (non-blocking) - `<device>_write()` — write data - `<device>_deinit()` — clean shutdown ### Next Steps - [ ] Verify on hardware with logic analyzer - [ ] Tune timeouts for your bus speed - [ ] Run test stubs ``` ## 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 收录的质量报告。
评分依据
针对嵌入式设备驱动开发(I2C/BLE/MQTT/SPI)提供完整解决方案
评分依据
触发词完整覆盖多种设备类型和协议场景
评分依据
步骤划分清晰(Step 0-5),逻辑连贯
评分依据
覆盖主要异常处理(超时、错误传播、重连逻辑)
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。