Qt C++ Code Review
x-tools-author/x-tools
Read-only review of Qt6 C++ code that combines a deterministic lint script with six parallel analysis agents and reports only high-confidence issues.
Scaffold a new Serial Studio I/O driver (a new data source under core/Devices/IO/Drivers/).
Install Ss New Driver
$ npx skills add Serial-Studio/Serial-Studio --skill ss-new-driver -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Serial-Studio/Serial-Studio ss-new-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/Serial-Studio/Serial-Studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ss-new-driver .claude/skills/ss-new-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 "ss-new-driver" agent skill from https://github.com/Serial-Studio/Serial-Studio/tree/master/.claude/skills/ss-new-driver into .claude/skills/ss-new-driver/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ss-new-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/Serial-Studio/Serial-Studio/tree/master/.claude/skills/ss-new-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 Serial-Studio/Serial-Studio --skill ss-new-driver -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Serial-Studio/Serial-Studio ss-new-driver --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Serial-Studio/Serial-Studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/ss-new-driver .agents/skills/ss-new-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 "ss-new-driver" agent skill from https://github.com/Serial-Studio/Serial-Studio/tree/master/.claude/skills/ss-new-driver into .agents/skills/ss-new-driver/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ss-new-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 Serial-Studio/Serial-Studio --skill ss-new-driver -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Serial-Studio/Serial-Studio ss-new-driver --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Serial-Studio/Serial-Studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/ss-new-driver .cursor/skills/ss-new-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 "ss-new-driver" agent skill from https://github.com/Serial-Studio/Serial-Studio/tree/master/.claude/skills/ss-new-driver into .cursor/skills/ss-new-driver/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ss-new-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/Serial-Studio/Serial-Studio.git --path .claude/skills/ss-new-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 Serial-Studio/Serial-Studio --skill ss-new-driver -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Serial-Studio/Serial-Studio ss-new-driver --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Serial-Studio/Serial-Studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/ss-new-driver .gemini/skills/ss-new-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 "ss-new-driver" agent skill from https://github.com/Serial-Studio/Serial-Studio/tree/master/.claude/skills/ss-new-driver into .gemini/skills/ss-new-driver/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ss-new-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 Serial-Studio/Serial-Studio ss-new-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 Serial-Studio/Serial-Studio --skill ss-new-driver -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Serial-Studio/Serial-Studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/ss-new-driver .github/skills/ss-new-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 "ss-new-driver" agent skill from https://github.com/Serial-Studio/Serial-Studio/tree/master/.claude/skills/ss-new-driver into .github/skills/ss-new-driver/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ss-new-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 Serial-Studio/Serial-Studio --skill ss-new-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 Serial-Studio/Serial-Studio ss-new-driver --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Serial-Studio/Serial-Studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/ss-new-driver .opencode/skills/ss-new-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 "ss-new-driver" agent skill from https://github.com/Serial-Studio/Serial-Studio/tree/master/.claude/skills/ss-new-driver into .opencode/skills/ss-new-driver/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ss-new-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
ss-new-driver- GitHub stars
- 7.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 494 words
- Files
- 1
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Scaffold a new Serial Studio I/O driver (a new data source under core/Devices/IO/Drivers/).
- Works in 10 steps: core/Devices/IO/Drivers/.h / .cpp — the… → core/Core/SerialStudio.h — add the value… → core/Devices/IO/ConnectionManager.{h,cpp}… → …
- Adding support for a new bus/transport — e.g
- SKILL.md covers Touch-points to wire (verify… and Rules
- Calls python
What it does
Ss New Driver is an agent skill from Serial-Studio/Serial-Studio. Scaffold a new Serial Studio I/O driver (a new data source under core/Devices/IO/Drivers/). Use when adding support for a new bus/transport — e.g. "add a <X driver", "support reading from <Y", "new data source". Encodes the canonical driver pattern and every registration touch-point so the new driver actually shows up in the UI, CLI, and connection manager.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with C++. The repository describes itself as: Open-source telemetry dashboard. Supports UART, BLE, MQTT, Modbus, CAN Bus and more.
When your agent uses it
- Adding support for a new bus/transport — e.g
Example prompts
- “add a <X driver”
- “support reading from <Y”
- “new data source”
- “/ss-new-driver”
Requirements
- Python 3
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- core/Devices/IO/Drivers/.h / .cpp — the driver class, SPDX header, .h ordering rules.
- core/Core/SerialStudio.h — add the value to the BusType enum (QML uses SerialStudio.BusType.*,
- core/Devices/IO/ConnectionManager.{h,cpp} — accessor (e.g. network() / uart() analogue)
- core/Devices/CMakeLists.txt — add IO/Drivers/.cpp to the source list (sources are
- QML configuration UI — the driver panes are bespoke forms (only the Project Editor renders
- core/Core/EnumLabels.cpp — add the bus to the busTypeSlug() and busTypeLabel()
- core/Ui/ProjectEditor/ProjectEditorIcons.h — add the bus to the busTypeIcon()
- Icon — add the driver SVG under app/rcc/icons/devices// (16/24/32) and register it with a
- CLI (optional) — if it should be launchable headless, add options in app/src/Misc/CLI.{h,cpp}
- tests/utils/api_client.py (optional) — add the bus to bus_map if integration tests should
What it can do on your machine
Read from SKILL.md and the folder at commit 3657d2c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python
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
Ss New Driver loads about 1.1k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 494 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 passed
The automated check found no risky patterns in SKILL.md.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 494 words (~1,149 tokens).
“Before writing anything, read core/Devices/IO/Drivers/BluetoothLE.h and BluetoothLE.cpp in full. They are the canonical reference for the driver contract — match their structure, signal/slot wiring, and driverProperties() shape rather than inventing a new layout. After the read, restate the driver contract…”
- name
- ss-new-driver
- argument-hint
- [DriverName]
Files
Just SKILL.md in .claude/skills/ss-new-driver of Serial-Studio/Serial-Studio.
Open the folder on GitHubat commit 3657d2c
Compare with similar skills
Ss New 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 |
|---|---|---|---|---|---|---|
| Ss New Driver this skillSerial-Studio/Serial-Studio | 7.2k | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Qt C++ Code Reviewx-tools-author/x-tools | 1.1k | 2 repos | ~4.3k | Automated safety check: Pass | BSD-3-Clause | |
| YugabyteDB ASH Instrumentationyugabyte/yugabyte-db | 11k | — | ~4.5k | Automated safety check: Pass | Custom licence | |
| pybind11 Release Preparationpybind/pybind11 | 18k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Paddle Eager GraphPaddlePaddle/Paddle | 24k | — | ~562 | Automated safety check: Pass | Apache-2.0 | |
| ONNX Runtime Source Buildmicrosoft/onnxruntime | 22k | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
YugabyteDB ASH Instrumentation
yugabyte/yugabyte-db
Procedure for adding or changing YugabyteDB Active Session History wait states in TServer and DocDB C++ code, including the macro to use for sync and async paths.
pybind11 Release Preparation
pybind/pybind11
Opens the pybind11 release-preparation pull request: picking the release base, bumping the version in common.h and integrating the changelog, following docs/release.rst.
Paddle Eager Graph
PaddlePaddle/Paddle
A skill your agent uses when navigating Paddle eager-mode (dynamic graph) source code, tracing forward/backward execution, debugging autograd issues, understanding PyLayer, or investigating…
- Official
ONNX Runtime Source Build
microsoft/onnxruntime
Builds ONNX Runtime from source with its build scripts, explaining the update, build and test phases, key flags and where the build output lands.
Esp32 Firmware Engineer
alxv2016/folloup-sticky
ESP32 firmware engineering for ESP-IDF projects. An agent skill from alxv2016/folloup-sticky.
More from Serial-Studio/Serial-Studio
All 15 skills in this repoQt Cpp Review
Serial-Studio/Serial-Studio
Qt6/C++ deep code review for Serial Studio. An agent skill from Serial-Studio/Serial-Studio.
Qt Qml Review
Serial-Studio/Serial-Studio
Qt6/QML deep code review for Serial Studio. An agent skill from Serial-Studio/Serial-Studio.
Ss Spec
Serial-Studio/Serial-Studio
Phase 1 of Serial Studio's spec-driven workflow: capture WHAT a feature must do and WHY, with no implementation detail.
Cpp Compiler Flags
Serial-Studio/Serial-Studio
C++ compiler/linker flag guidance for Serial Studio's build (GCC, Clang, AppleClang, MSVC cl.exe, clang-cl, MinGW, IntelLLVM).
Ss Cpp Modern
Serial-Studio/Serial-Studio
Modern C++20 authoring guidance for Serial Studio (Qt 6.11, C++20): concepts, ranges, move/RAII, std smart pointers, constexpr, lock-free SPSC atomics.
Ss Docs
Serial-Studio/Serial-Studio
Write, update, or review Serial Studio's user-facing documentation: the doc/help manual, README.md, and examples READMEs.
Related
Works with
Categories
Questions about Ss New Driver
What does Ss New Driver do?
Scaffold a new Serial Studio I/O driver (a new data source under core/Devices/IO/Drivers/). Ss New Driver is an agent skill from Serial-Studio/Serial-Studio. Scaffold a new Serial Studio I/O driver (a new data source under core/Devices/IO/Drivers/).
When should I use Ss New Driver?
Ss New Driver fits situations like: adding support for a new bus/transport — e.g.
How do I install Ss New Driver in Claude Code?
Run `npx skills add Serial-Studio/Serial-Studio --skill ss-new-driver -a claude-code`. Or copy the skill folder (.claude/skills/ss-new-driver in Serial-Studio/Serial-Studio) into .claude/skills/ss-new-driver in your project. Claude Code loads it when a task matches its description.
How do I install Ss New Driver in Codex?
Run `npx skills add Serial-Studio/Serial-Studio --skill ss-new-driver -a codex`. Or copy the skill folder (.claude/skills/ss-new-driver in Serial-Studio/Serial-Studio) into .agents/skills/ss-new-driver in your project. Codex loads it when a task matches its description.
Can I use Ss New 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 Serial-Studio/Serial-Studio --skill ss-new-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/ss-new-driver, .gemini/skills/ss-new-driver, .github/skills/ss-new-driver and .opencode/skills/ss-new-driver in your project.
What does Ss New Driver need to run?
Going by SKILL.md and its folder, Ss New Driver needs the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Ss New 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 Ss New Driver safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ss New Driver use?
Ss New Driver has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Ss New Driver use?
About 1.1k tokens (SKILL.md is roughly 4.6k 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 Ss New Driver?
Skills that share tags, products or a category with Ss New Driver: Qt C++ Code Review (x-tools-author/x-tools, 1.1k stars), YugabyteDB ASH Instrumentation (yugabyte/yugabyte-db, 11k stars), pybind11 Release Preparation (pybind/pybind11, 18k stars) and Paddle Eager Graph (PaddlePaddle/Paddle, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ss New Driver?
Serial-Studio (a GitHub organization) maintains it in Serial-Studio/Serial-Studio, which has 7,226 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.
Source: Serial-Studio/Serial-Studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.