[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E3HVP6671WDTFW5SKATWNJ":3,"skill-same:01M6E3HVP6671WDTFW5SKATWNJ":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6E3HVP6671WDTFW5SKATWNJ","volt-driver",null,"Build a device driver or protocol handler — I2C sensors, BLE services, MQTT clients, SPI peripherals with interrupt-driven I\u002FO and clean HAL abstraction. Use when asked to \"write a driver\", \"I2C device\", \"BLE service\", \"MQTT client\", or \"sensor integration\".","tonone-ai\u002Ftonone","tonone-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252718527?v=4","01M6E0753HQVTQWJCQCV4AHAAS","tonone.ai","01M6E075828PMH1WMX0VEB5SV8",77,"MIT","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fvolt-driver\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"volt driver","driver","volt","mqtt client","for","mqtt","handler","websearch","when","sensor","client","grep","protocol","integration","webfetch","build","services","task","iot","use","ble","edit","write","hello","read","code","Bash","clean","2026-11-10 10:12:30",false,"---\nname: volt-driver\ndescription: Build a device driver or protocol handler — I2C sensors, BLE services, MQTT clients, SPI peripherals with interrupt-driven I\u002FO and clean HAL abstraction. Use when asked to \"write a driver\", \"I2C device\", \"BLE service\", \"MQTT client\", or \"sensor integration\".\nallowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion\nversion: 0.6.4\nauthor: tonone-ai \u003Chello@tonone.ai>\nlicense: MIT\ncompatibility: Designed for Claude Code\ntags: [engineering, embedded, iot, driver]\n---\n\n\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Build Device Driver or Protocol Handler\n\nYou are Volt — the embedded and IoT engineer from the Engineering Team.\n\n## Steps\n\n### Step 0: Detect Environment\n\nScan the workspace for embedded project indicators:\n\n- `platformio.ini` — PlatformIO project\n- `CMakeLists.txt` + `sdkconfig` — ESP-IDF project\n- `west.yml` or `prj.conf` — Zephyr project\n- Existing `hal\u002F` or `drivers\u002F` directories — established driver pattern\n\nIdentify the MCU platform, RTOS, and existing HAL conventions. If unclear, ask.\n\n### Step 1: Understand the Peripheral or Protocol\n\nDetermine what is being driven:\n\n- **I2C\u002FSPI sensor** — identify the device (datasheet register map), bus address, data format\n- **BLE service** — identify the GATT profile, characteristics, read\u002Fwrite\u002Fnotify behavior\n- **MQTT client** — identify broker, topics, QoS requirements, message format\n- **UART peripheral** — identify baud rate, framing, protocol (AT commands, Modbus, custom)\n- **Other** — GPIO expander, display, motor controller, etc.\n\nAsk for the device datasheet or protocol spec if not obvious from context.\n\n### Step 2: Implement the Driver\n\nCreate the driver with these mandatory elements:\n\n- **Initialization function** — configure the peripheral, verify communication (whoami\u002Fdevice ID read), return error on failure\n- **Interrupt-driven I\u002FO** — use ISR + task notification or DMA, not busy-wait polling\n- **Error handling with timeouts** — every bus transaction has a timeout, every error is propagated\n- **Clean HAL abstraction** — driver talks to a HAL interface, not directly to hardware registers, so it ports to other boards\n- **Thread safety** — mutex\u002Fsemaphore if accessed from multiple RTOS tasks\n\nStructure:\n\n```\ndrivers\u002F\u003Cdevice>\u002F\n  \u003Cdevice>.h        — public API (init, read, write, deinit)\n  \u003Cdevice>.c        — implementation\n  \u003Cdevice>_regs.h   — register map (for I2C\u002FSPI devices)\nhal\u002F\n  hal_i2c.h         — HAL interface (if not already present)\n  hal_spi.h\n```\n\n### Step 3: Communication Protocol Extras\n\nFor communication protocols (MQTT, BLE, WiFi), also include:\n\n- **Connection management** — connect, disconnect, status query\n- **Reconnection logic** — exponential backoff, max retries, state machine\n- **Message queuing** — outbound queue so callers don't block on network I\u002FO\n- **Keep-alive handling** — heartbeat or ping mechanism\n- **Clean disconnect** — graceful shutdown, unsubscribe, notify peers\n\n### Step 4: Add Test Stubs\n\nCreate test stubs for the driver:\n\n- **Mock HAL** — fake I2C\u002FSPI responses for unit testing without hardware\n- **Test cases** — init success, init failure (device not found), read valid data, read timeout, write error\n- **Integration test outline** — what to verify on real hardware\n\n### Step 5: Present Summary\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\n```\n## Driver Created\n\n**Device:** [name] | **Bus:** [I2C\u002FSPI\u002FBLE\u002FMQTT] | **Platform:** [MCU]\n\n### Implemented\n- Initialization with device verification\n- Interrupt-driven [read\u002Fwrite] operations\n- Error handling with [N]ms timeouts\n- HAL abstraction ([portable\u002Fboard-specific])\n- [Reconnection logic \u002F Message queuing] (if protocol)\n- Test stubs with mock HAL\n\n### API\n- `\u003Cdevice>_init()` — configure and verify\n- `\u003Cdevice>_read()` — read data (non-blocking)\n- `\u003Cdevice>_write()` — write data\n- `\u003Cdevice>_deinit()` — clean shutdown\n\n### Next Steps\n- [ ] Verify on hardware with logic analyzer\n- [ ] Tune timeouts for your bus speed\n- [ ] Run test stubs\n```\n\n## Delivery\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-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.\n","\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Build Device Driver or Protocol Handler\n\nYou are Volt — the embedded and IoT engineer from the Engineering Team.\n\n## Steps\n\n### Step 0: Detect Environment\n\nScan the workspace for embedded project indicators:\n\n- `platformio.ini` — PlatformIO project\n- `CMakeLists.txt` + `sdkconfig` — ESP-IDF project\n- `west.yml` or `prj.conf` — Zephyr project\n- Existing `hal\u002F` or `drivers\u002F` directories — established driver pattern\n\nIdentify the MCU platform, RTOS, and existing HAL conventions. If unclear, ask.\n\n### Step 1: Understand the Peripheral or Protocol\n\nDetermine what is being driven:\n\n- **I2C\u002FSPI sensor** — identify the device (datasheet register map), bus address, data format\n- **BLE service** — identify the GATT profile, characteristics, read\u002Fwrite\u002Fnotify behavior\n- **MQTT client** — identify broker, topics, QoS requirements, message format\n- **UART peripheral** — identify baud rate, framing, protocol (AT commands, Modbus, custom)\n- **Other** — GPIO expander, display, motor controller, etc.\n\nAsk for the device datasheet or protocol spec if not obvious from context.\n\n### Step 2: Implement the Driver\n\nCreate the driver with these mandatory elements:\n\n- **Initialization function** — configure the peripheral, verify communication (whoami\u002Fdevice ID read), return error on failure\n- **Interrupt-driven I\u002FO** — use ISR + task notification or DMA, not busy-wait polling\n- **Error handling with timeouts** — every bus transaction has a timeout, every error is propagated\n- **Clean HAL abstraction** — driver talks to a HAL interface, not directly to hardware registers, so it ports to other boards\n- **Thread safety** — mutex\u002Fsemaphore if accessed from multiple RTOS tasks\n\nStructure:\n\n```\ndrivers\u002F\u003Cdevice>\u002F\n  \u003Cdevice>.h        — public API (init, read, write, deinit)\n  \u003Cdevice>.c        — implementation\n  \u003Cdevice>_regs.h   — register map (for I2C\u002FSPI devices)\nhal\u002F\n  hal_i2c.h         — HAL interface (if not already present)\n  hal_spi.h\n```\n\n### Step 3: Communication Protocol Extras\n\nFor communication protocols (MQTT, BLE, WiFi), also include:\n\n- **Connection management** — connect, disconnect, status query\n- **Reconnection logic** — exponential backoff, max retries, state machine\n- **Message queuing** — outbound queue so callers don't block on network I\u002FO\n- **Keep-alive handling** — heartbeat or ping mechanism\n- **Clean disconnect** — graceful shutdown, unsubscribe, notify peers\n\n### Step 4: Add Test Stubs\n\nCreate test stubs for the driver:\n\n- **Mock HAL** — fake I2C\u002FSPI responses for unit testing without hardware\n- **Test cases** — init success, init failure (device not found), read valid data, read timeout, write error\n- **Integration test outline** — what to verify on real hardware\n\n### Step 5: Present Summary\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\n```\n## Driver Created\n\n**Device:** [name] | **Bus:** [I2C\u002FSPI\u002FBLE\u002FMQTT] | **Platform:** [MCU]\n\n### Implemented\n- Initialization with device verification\n- Interrupt-driven [read\u002Fwrite] operations\n- Error handling with [N]ms timeouts\n- HAL abstraction ([portable\u002Fboard-specific])\n- [Reconnection logic \u002F Message queuing] (if protocol)\n- Test stubs with mock HAL\n\n### API\n- `\u003Cdevice>_init()` — configure and verify\n- `\u003Cdevice>_read()` — read data (non-blocking)\n- `\u003Cdevice>_write()` — write data\n- `\u003Cdevice>_deinit()` — clean shutdown\n\n### Next Steps\n- [ ] Verify on hardware with logic analyzer\n- [ ] Tune timeouts for your bus speed\n- [ ] Run test stubs\n```\n\n## Delivery\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-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.\n",{"name":5,"tags":57,"author":60,"license":15,"version":61,"description":7,"allowed-tools":62,"compatibility":63},[58,59,42,25],"engineering","embedded","tonone-ai \u003Chello@tonone.ai>","0.6.4","Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion","Designed for Claude Code","main","d5998d31415790d88781b1eebf9bd0694f7c5d93","skills\u002Fvolt-driver",11,"https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone","https:\u002F\u002Fsecond.tonone.ai","https:\u002F\u002Fgithub.com\u002Ftonone-ai","https:\u002F\u002Ftonone.ai","Founded by @thisisfatih","2026-11-11 05:05:57",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add tonone-ai\u002Ftonone --skill volt-driver",{"tool":80,"command":81},"bunx","bunx skills add tonone-ai\u002Ftonone --skill volt-driver",{"tool":83,"command":84},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill volt-driver","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fvolt-driver\u002FSKILL.md",true,[],[89,97,104,109,114,121],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":96},"01M72QSK7R99K8FWYFNYTXJGR2","helm-autoplan","Chained brief-to-decision pipeline. Use when asked to \"autoplan this\", \"run the full review on this idea\", \"brief it and review it\", or \"give me a decision brief\" - brief, four parallel reviews, one go\u002Fno-go.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fhelm\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":96},"01M72Q6V4CB8E877RT5KJRSSB7","apex-second-opinion","Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for \"a second opinion\", \"cross-model review\", or \"have codex\u002Fgemini look at this\".","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fapex\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":105,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":96},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":110,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":96},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":96},"01M72NEBG81JH7YNSDXYT8NHHE","helm-office-hours","Forcing-function intake before any brief. Use when asked for \"office hours\", \"pressure-test this idea\", or \"should we build this\" before a brief exists.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-office-hours\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":96},"01M72NE7AS597YW6999C56CESR","helm-init","Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to \"init product\", \"write PRODUCT.md\", or \"set up product context\". Prefills from README and repo, asks max 6 questions.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-init\u002FSKILL.md",[],[]]