RuView Hardware Setup
ruvnet/RuView
Brings a RuView CSI sensing node online by building ESP32-S3 or ESP32-C6 firmware, flashing the board, provisioning WiFi and checking the serial output.
Build a device driver or protocol handler — I2C sensors, BLE services, MQTT clients, SPI peripherals with interrupt-driven I/O and clean HAL abstraction.
Install Volt Driver
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill volt-driver -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace volt-driver --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/volt-driver .claude/skills/volt-driver && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "volt-driver" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/volt-driver into .claude/skills/volt-driver/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "volt-driver", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/volt-driverType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill volt-driver -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace volt-driver --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/volt-driver .agents/skills/volt-driver && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "volt-driver" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/volt-driver into .agents/skills/volt-driver/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "volt-driver", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill volt-driver -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace volt-driver --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/volt-driver .cursor/skills/volt-driver && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "volt-driver" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/volt-driver into .cursor/skills/volt-driver/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "volt-driver", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path plugins/ai-agency/tonone/skills/volt-driver--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill volt-driver -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace volt-driver --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/volt-driver .gemini/skills/volt-driver && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "volt-driver" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/volt-driver into .gemini/skills/volt-driver/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "volt-driver", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace volt-driverInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill volt-driver -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/volt-driver .github/skills/volt-driver && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "volt-driver" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/volt-driver into .github/skills/volt-driver/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "volt-driver", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill volt-driver -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace volt-driver --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/volt-driver .opencode/skills/volt-driver && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "volt-driver" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/volt-driver into .opencode/skills/volt-driver/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "volt-driver", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
volt-driver- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 374 words
- Files
- 2
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a device driver or protocol handler — I2C sensors, BLE services, MQTT clients, SPI peripherals with interrupt-driven I/O and clean HAL abstraction.
- Works in 6 steps: Detect Environment → Understand the Peripheral or Protocol → Implement the Driver → …
- Asked to write a driver
- SKILL.md covers Steps and Delivery
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Volt Driver is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).
It sits in Development. It works with ESP32. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- Asked to write a driver
- Sensor integration
Example prompts
- “write a driver”
- “I2C device”
- “BLE service”
- “/volt-driver”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBashGlobGrepWebFetchWebSearchTaskTodoWrite
…and 1 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Volt Driver loads about 1.1k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 374 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 374 words, ~1,066 tokens.
Download SKILL.mdSave it as
.claude/skills/volt-driver/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- 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 projectCMakeLists.txt+sdkconfig— ESP-IDF projectwest.ymlorprj.conf— Zephyr project- Existing
hal/ordrivers/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.hShow full SKILL.md (158 more words)Show less
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 stubsDelivery
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.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in plugins/ai-agency/tonone/skills/volt-driver of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- .claude-plugin/plugin.json
Open the folder on GitHubat commit cfae287
Compare with similar skills
Volt Driver next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Volt Driver this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Notes | MIT | |
| RuView Hardware Setupruvnet/RuView | 97k | — | ~1.8k | Automated safety check: Notes | MIT | |
| Esp32 Firmware Engineeralxv2016/folloup-sticky | 117 | 1 repos | ~3.8k | Automated safety check: Pass | GPL-3.0 | |
| RuView mmWave Radar Setupruvnet/RuView | 97k | — | ~907 | Automated safety check: Notes | MIT | |
| Embedded DebugFastLED/FastLED | 7.5k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Auto EmbeddedDunCanYounG-1/MICU-auto-embedded | 253 | — | ~1.6k | Automated safety check: Pass | CC-BY-NC-4.0 |
Similar skills
Esp32 Firmware Engineer
alxv2016/folloup-sticky
ESP32 firmware engineering for ESP-IDF projects. An agent skill from alxv2016/folloup-sticky.
RuView mmWave Radar Setup
ruvnet/RuView
Sets up and runs 60 GHz and 24 GHz mmWave radar sensing on ESP32 boards in RuView, alone or fused with WiFi CSI.
Embedded Debug
FastLED/FastLED
Firmware crash analysis, stack trace decoder, and register dump interpreter for ESP32/ARM/AVR platforms.
Auto Embedded
DunCanYounG-1/MICU-auto-embedded
全平台嵌入式 AI 开发框架（对标 Trellis）：把 RIPER-5 五阶段协议 + 四文件记忆 + 分层架构门禁 + Scout/Builder/Verifier 多 Agent + 24 个工具调用技能（build/flash/debug/serial/can/modbus/visa/static/memory/rtos/scons），做成『装进工程、项目级 hook…
Embedded Cpp14 Misra
BlueAndi/Pixelix
A skill your agent uses when writing, reviewing, or refactoring C/C++ firmware code in this repository (src/, lib/, test/) — creating or editing .h/.hpp/.cpp files, applying MISRA-oriented and…
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Works with
Categories
Questions about Volt Driver
What does Volt Driver do?
Build a device driver or protocol handler — I2C sensors, BLE services, MQTT clients, SPI peripherals with interrupt-driven I/O and clean HAL abstraction. Volt Driver is an agent skill from jeremylongshore/tons-of-skills-marketplace. Build a device driver or protocol handler — I2C sensors, BLE services, MQTT clients, SPI peripherals with interrupt-driven I/O and clean HAL abstraction.
When should I use Volt Driver?
Volt Driver fits situations like: asked to write a driver; sensor integration.
How do I install Volt Driver in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill volt-driver -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/volt-driver in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/volt-driver in your project. Claude Code loads it when a task matches its description.
How do I install Volt Driver in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill volt-driver -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/volt-driver in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/volt-driver in your project. Codex loads it when a task matches its description.
Can I use Volt Driver in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill volt-driver -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/volt-driver, .gemini/skills/volt-driver, .github/skills/volt-driver and .opencode/skills/volt-driver in your project.
What does Volt Driver need to run?
SKILL.md names no scripts, command-line tools or credentials: Volt Driver is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion.
Does Volt Driver access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Volt Driver safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Volt Driver use?
Volt Driver is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Volt Driver use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Volt Driver?
Skills that share tags, products or a category with Volt Driver: RuView Hardware Setup (ruvnet/RuView, 97k stars), Esp32 Firmware Engineer (alxv2016/folloup-sticky, 117 stars), RuView mmWave Radar Setup (ruvnet/RuView, 97k stars) and Embedded Debug (FastLED/FastLED, 7.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Volt Driver?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.