Agent skill

Bus Drivers I2c Spi

by mohitmishra786 in mohitmishra786/low-level-dev-skills

I2C and SPI bus driver skill for Linux client drivers. An agent skill from mohitmishra786/low-level-dev-skills.

MITAuto-check passedDevelopment

Install Bus Drivers I2c Spi

skills CLI

$ npx skills add mohitmishra786/low-level-dev-skills --skill bus-drivers-i2c-spi -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills bus-drivers-i2c-spi --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/kernel-dev/bus-drivers-i2c-spi .claude/skills/bus-drivers-i2c-spi && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "bus-drivers-i2c-spi" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/bus-drivers-i2c-spi into .claude/skills/bus-drivers-i2c-spi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bus-drivers-i2c-spi", 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

$skill-installer install https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/bus-drivers-i2c-spi

Type 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.

skills CLI

$ npx skills add mohitmishra786/low-level-dev-skills --skill bus-drivers-i2c-spi -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills bus-drivers-i2c-spi --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/kernel-dev/bus-drivers-i2c-spi .agents/skills/bus-drivers-i2c-spi && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "bus-drivers-i2c-spi" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/bus-drivers-i2c-spi into .agents/skills/bus-drivers-i2c-spi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bus-drivers-i2c-spi", 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.

skills CLI

$ npx skills add mohitmishra786/low-level-dev-skills --skill bus-drivers-i2c-spi -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills bus-drivers-i2c-spi --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/kernel-dev/bus-drivers-i2c-spi .cursor/skills/bus-drivers-i2c-spi && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "bus-drivers-i2c-spi" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/bus-drivers-i2c-spi into .cursor/skills/bus-drivers-i2c-spi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bus-drivers-i2c-spi", 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

$ gemini skills install https://github.com/mohitmishra786/low-level-dev-skills.git --path skills/kernel-dev/bus-drivers-i2c-spi

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add mohitmishra786/low-level-dev-skills --skill bus-drivers-i2c-spi -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills bus-drivers-i2c-spi --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/kernel-dev/bus-drivers-i2c-spi .gemini/skills/bus-drivers-i2c-spi && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "bus-drivers-i2c-spi" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/bus-drivers-i2c-spi into .gemini/skills/bus-drivers-i2c-spi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bus-drivers-i2c-spi", 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.

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills bus-drivers-i2c-spi

Installs 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).

skills CLI

$ npx skills add mohitmishra786/low-level-dev-skills --skill bus-drivers-i2c-spi -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/kernel-dev/bus-drivers-i2c-spi .github/skills/bus-drivers-i2c-spi && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "bus-drivers-i2c-spi" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/bus-drivers-i2c-spi into .github/skills/bus-drivers-i2c-spi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bus-drivers-i2c-spi", 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.

skills CLI

$ npx skills add mohitmishra786/low-level-dev-skills --skill bus-drivers-i2c-spi -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install mohitmishra786/low-level-dev-skills bus-drivers-i2c-spi --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/mohitmishra786/low-level-dev-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/kernel-dev/bus-drivers-i2c-spi .opencode/skills/bus-drivers-i2c-spi && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "bus-drivers-i2c-spi" agent skill from https://github.com/mohitmishra786/low-level-dev-skills/tree/main/skills/kernel-dev/bus-drivers-i2c-spi into .opencode/skills/bus-drivers-i2c-spi/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bus-drivers-i2c-spi", 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: bus-drivers-i2c-spi
GitHub stars: 252
Token cost: ~960 tokens
SKILL.md length: 158 words
Files: 1
Skills in repo: 138
Repo updated: Jun 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

I2C and SPI bus driver skill for Linux client drivers. An agent skill from mohitmishra786/low-level-dev-skills.

Works in 6 steps: I2C client driver → Raw I2C transfer → SPI driver → …
Writing i2cdriver
SKILL.md covers Purpose, When to Use, Workflow and Common Problems, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Bus Drivers I2c Spi is an agent skill from mohitmishra786/low-level-dev-skills. I2C and SPI bus driver skill for Linux client drivers. Use when writing i2cdriver or spidriver, register access over bus, DMA SPI transfers, or ACPI/DT client binding. Activates on queries about i2cclient, spidriver, regmap I2C, SPI transfer, or Linux I2C SPI subsystem.

Its SKILL.md is about 960 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 Linux. The repository describes itself as: A curated suite of AI agent skills for systems and low-level programming with C/C++, Rust, and Zig toolchains, covering compilers, debuggers, profilers, build systems…. The licence is MIT.

When your agent uses it

Writing i2cdriver
Register access over bus
DMA SPI transfers
ACPI/DT client binding

Example prompts

“/bus-drivers-i2c-spi”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

I2C client driver
Raw I2C transfer
SPI driver
regmap (preferred for register maps)
Debug
Agent usage

What it can do on your machine

Read from SKILL.md and the folder at commit bdc5847. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are c, dts and bash).
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

Bus Drivers I2c Spi loads about 960 tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 158 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~74
When it runs · the whole SKILL.md, loaded when a task matches: ~960

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

The full file from mohitmishra786/low-level-dev-skills at commit bdc5847, republished under its MIT licence (© mohitmishra786). 158 words, ~960 tokens.

Download SKILL.mdSave it as .claude/skills/bus-drivers-i2c-spi/SKILL.md (or your agent's skills folder).

name: bus-drivers-i2c-spi
description: I2C and SPI bus driver skill for Linux client drivers. Use when writing i2c_driver or spi_driver, register access over bus, DMA SPI transfers, or ACPI/DT client binding. Activates on queries about i2c_client, spi_driver, regmap I2C, SPI transfer, or Linux I2C SPI subsystem.

Bus Drivers (I2C and SPI)

Purpose

Guide agents through Linux I2C and SPI client drivers: bus registration, i2c_transfer / spi_sync, regmap abstraction, DT compatible on bus children, and probe patterns — complementing platform MMIO drivers in skills/kernel/device-drivers.

When to Use

Sensor or PMIC on I2C/SPI bus
Converting bare-metal SPI register reads to kernel driver
Using regmap for multi-byte register access
Debugging -EREMOTEIO or missing ACK

Workflow

1. I2C client driver

#include <linux/i2c.h>
#include <linux/mod_devicetable.h>

static int my_probe(struct i2c_client *client)
{
    struct regmap *map;

    map = devm_regmap_init_i2c(client, &my_regmap_config);
    if (IS_ERR(map))
        return PTR_ERR(map);

    dev_info(&client->dev, "probed at 0x%02x\n", client->addr);
    return 0;
}

static const struct of_device_id my_of_id[] = {
    { .compatible = "vendor,sensor" },
    { }
};
MODULE_DEVICE_TABLE(of, my_of_id);

static const struct i2c_device_id my_id[] = {
    { "mysensor", 0 },
    { }
};
MODULE_DEVICE_TABLE(i2c, my_id);

static struct i2c_driver my_driver = {
    .probe    = my_probe,
    .remove   = my_remove,
    .driver   = { .name = "mysensor", .of_match_table = my_of_id },
    .id_table = my_id,
};
module_i2c_driver(my_driver);

DT child:

dts

i2c1 {
    sensor@48 {
        compatible = "vendor,sensor";
        reg = <0x48>;
    };
};

2. Raw I2C transfer

u8 reg = 0x0F, val;
struct i2c_msg msgs[] = {
    { .addr = client->addr, .flags = 0,       .len = 1, .buf = &reg },
    { .addr = client->addr, .flags = I2C_M_RD, .len = 1, .buf = &val },
};
ret = i2c_transfer(client->adapter, msgs, 2);

3. SPI driver

static int spi_probe(struct spi_device *spi)
{
    spi->mode = SPI_MODE_0;
    spi->bits_per_word = 8;
    spi_setup(spi);

    struct spi_transfer t = {
        .tx_buf = tx,
        .rx_buf = rx,
        .len    = len,
    };
    struct spi_message m;
    spi_message_init(&m);
    spi_message_add_tail(&t, &m);
    return spi_sync(spi, &m);
}

static struct spi_driver spi_drv = {
    .probe  = spi_probe,
    .driver = { .name = "my-spi", .of_match_table = my_of_match },
};
module_spi_driver(spi_drv);

4. regmap (preferred for register maps)

static const struct regmap_config my_regmap_config = {
    .reg_bits   = 8,
    .val_bits   = 8,
    .max_register = 0x7F,
};

regmap_read(map, REG_STATUS, &val);
regmap_write(map, REG_CTRL, CTRL_ENABLE);
regmap_update_bits(map, REG_CTRL, MASK, ENABLE);

5. Debug

bash

i2cdetect -y 1
i2cdump -y 1 0x48
cat /sys/bus/i2c/devices/i2c-1/1-0048/name

6. Agent usage

/bus-drivers-i2c-spi Write regmap-based driver for I2C PMIC at 0x58

Common Problems

Symptom	Cause	Fix
`-EREMOTEIO`	NACK — wrong address	`i2cdetect`; check `reg` in DT
SPI mode wrong	CPOL/CPHA mismatch	Match datasheet + `spi->mode`
Probe defer	Regulator/clock supplier	Return `-EPROBE_DEFER`
regmap -EIO	16-bit vs 8-bit reg	Set `reg_bits`, `val_bits`
DMA not used	Small `spi_sync` OK	`spi_sync_transfer` for bulk

skills/kernel/device-drivers — IRQ, DMA, PM runtime
skills/kernel-dev/device-tree — bus child nodes
skills/baremetal/spi-i2c-baremetal — register-level protocol
skills/kernel-dev/platform-device-model — driver model parallels
skills/kernel-dev/writing-char-drivers — expose sensor via char dev

Files

Just SKILL.md in skills/kernel-dev/bus-drivers-i2c-spi of mohitmishra786/low-level-dev-skills.

Open the folder on GitHubat commit bdc5847

Compare with similar skills

Bus Drivers I2c Spi 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.

Bus Drivers I2c Spi compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Bus Drivers I2c Spi this skillmohitmishra786/low-level-dev-skills	252	—	~960	Automated safety check: Pass	MIT	3 mo ago
Update .NET OS Packagesdotnet/core	22k	—	~2.3k	Automated safety check: Pass	MIT	yesterday
Cut Releasejfernandez/bpftop	2.7k	—	~2k	Automated safety check: Pass	Apache-2.0	1 mo ago
Native Feel Cross Platform Desktopyetone/native-feel-skill	1.9k	1 repos	~1.5k	Automated safety check: Pass	MIT	4 mo ago
PlotJuggler 4 Perf ProfilingPlotJuggler/PlotJuggler	6.2k	—	~1.6k	Automated safety check: Notes	MPL-2.0	9 days ago
ONNX Runtime Source Buildmicrosoft/onnxruntime	22k	—	~1.4k	Automated safety check: Pass	MIT	today

Similar skills

Update .NET OS Packages
dotnet/core
Official
Audits and updates os-packages.json files listing the Linux packages each .NET release needs per distro, then regenerates the Markdown from the JSON.
22k GitHub stars~2.3k tokensUpdated yesterday
DevelopmentAuto-check passed
Cut Release
jfernandez/bpftop
Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.
2.7k GitHub stars~2k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Native Feel Cross Platform Desktop
yetone/native-feel-skill
A skill your agent uses when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a…
1.9k GitHub starsUsed in 1 repo~1.5k tokens
DevelopmentAuto-check passed
PlotJuggler 4 Perf Profiling
PlotJuggler/PlotJuggler
Guides CPU profiling of PlotJuggler 4 on Linux with perf: count first, record cheaply with LBR, then read per-thread, flat, flamegraph or time-window views.
6.2k GitHub stars~1.6k tokensUpdated 9 days ago
DevelopmentAuto-check: notes
ONNX Runtime Source Build
microsoft/onnxruntime
Official
Builds ONNX Runtime from source with its build scripts, explaining the update, build and test phases, key flags and where the build output lands.
22k GitHub stars~1.4k tokensUpdated today
DevelopmentAuto-check passed
JS Cpp Protocol
notepadqq/notepadqq
Reference for the communication protocol between the JavaScript editor (CodeMirror or Monaco) and the C++/Qt UI layer via QWebChannel.
2.3k GitHub stars~3.2k tokensUpdated 5 days ago
DevelopmentAuto-check passed

Questions about Bus Drivers I2c Spi

What does Bus Drivers I2c Spi do?

I2C and SPI bus driver skill for Linux client drivers. An agent skill from mohitmishra786/low-level-dev-skills. Bus Drivers I2c Spi is an agent skill from mohitmishra786/low-level-dev-skills. I2C and SPI bus driver skill for Linux client drivers.

When should I use Bus Drivers I2c Spi?

Bus Drivers I2c Spi fits situations like: writing i2cdriver; register access over bus; DMA SPI transfers; ACPI/DT client binding.

How do I install Bus Drivers I2c Spi in Claude Code?

Run `npx skills add mohitmishra786/low-level-dev-skills --skill bus-drivers-i2c-spi -a claude-code`. Or copy the skill folder (skills/kernel-dev/bus-drivers-i2c-spi in mohitmishra786/low-level-dev-skills) into .claude/skills/bus-drivers-i2c-spi in your project. Claude Code loads it when a task matches its description.

How do I install Bus Drivers I2c Spi in Codex?

Run `npx skills add mohitmishra786/low-level-dev-skills --skill bus-drivers-i2c-spi -a codex`. Or copy the skill folder (skills/kernel-dev/bus-drivers-i2c-spi in mohitmishra786/low-level-dev-skills) into .agents/skills/bus-drivers-i2c-spi in your project. Codex loads it when a task matches its description.

Can I use Bus Drivers I2c Spi 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 mohitmishra786/low-level-dev-skills --skill bus-drivers-i2c-spi -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bus-drivers-i2c-spi, .gemini/skills/bus-drivers-i2c-spi, .github/skills/bus-drivers-i2c-spi and .opencode/skills/bus-drivers-i2c-spi in your project.

What does Bus Drivers I2c Spi need to run?

SKILL.md names no scripts, command-line tools or credentials: Bus Drivers I2c Spi is instructions for the agent only.

Does Bus Drivers I2c Spi 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 Bus Drivers I2c Spi 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 Bus Drivers I2c Spi use?

Bus Drivers I2c Spi is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bus Drivers I2c Spi use?

About 960 tokens (SKILL.md is roughly 3.8k 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 Bus Drivers I2c Spi?

Skills that share tags, products or a category with Bus Drivers I2c Spi: Update .NET OS Packages (dotnet/core, 22k stars), Cut Release (jfernandez/bpftop, 2.7k stars), Native Feel Cross Platform Desktop (yetone/native-feel-skill, 1.9k stars) and PlotJuggler 4 Perf Profiling (PlotJuggler/PlotJuggler, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bus Drivers I2c Spi?

mohitmishra786 (a GitHub user) maintains it in mohitmishra786/low-level-dev-skills, which has 252 GitHub stars. The repository holds 138 skills in this directory. The repository was last updated on June 27, 2026.

Source: mohitmishra786/low-level-dev-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Bus Drivers I2c Spi

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Bus Drivers (I2C and SPI)

Purpose

When to Use

Workflow

1. I2C client driver

2. Raw I2C transfer

3. SPI driver

4. regmap (preferred for register maps)

5. Debug

6. Agent usage

Common Problems

Related Skills

Files

Compare with similar skills

Similar skills

More from mohitmishra786/low-level-dev-skills

Related

Questions about Bus Drivers I2c Spi