device-driver-development SKILL.md skillA
device-driver-development from oghie/skillsets is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add oghie/skillsets/device-driver-development@v0.1.0Pins v0.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- oghie/skillsets
- Path
skills/device-driver-development/SKILL.md- Versions recorded
- 2
- Latest version
- v0.1.0, committed Jul 14, 2026
- First version recorded
- Jun 21, 2026
- Size
- 4,261 bytes
- Repository stars
- 9
- License
- MIT
Use when developing, reviewing, debugging, porting, or engineering Linux kernel device drivers, kernel modules, device tree bindings, bus clients, subsystem drivers, DMA/IRQ/memory paths, userspace interfaces, or hardware bring-up plans.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Device Driver Development ## Core Rule Treat every driver task as hardware contract engineering: identify the kernel version, hardware bus, subsystem owner, execution context, lifetime model, and userspace ABI before writing code. ## Knowledge Grounding - Use `references/knowledge-map.md` for the driver domain map and conceptual model. - Treat API details as version-sensitive; verify callback signatures, helpers, and bindings against the active kernel tree or current kernel docs. ## First Pass 1. Classify the device: char, platform, I2C, SPI, regmap, IIO, GPIO, IRQ controller, input, RTC, PWM, regulator, framebuffer, or NIC. 2. Identify interface surfaces: `/dev`, sysfs, debugfs, ioctl, mmap, netdev, IIO buffers, input events, DT binding, or kernel consumer API. 3. Choose probe/remove lifetime: prefer `devm_*`, explicit unwind only when ordering or shared state requires it. 4. Decide concurrency boundaries: process context, atomic context, IRQ top half, threaded IRQ, workqueue, timer, DMA callback. 5. Define evidence needed: datasheet registers, bus transaction examples, DT node, logs, scope/logic-analyzer traces, and test plan. ## Required Reads By Task …
Read the whole file at its exact version.
How to install
mdr add oghie/skillsets/device-driver-development@sha256:26fa3f81eb95626bThe line at the top of this page pins the label v0.1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ptz5hbkjso3yec7z)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 21, 2026 and Jul 14, 2026, about one every 22 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.1.0 latest | 2026-07-14 | 4998981 | 4,261 B | A | view · diff |
| git:20260621.8319e13 | 2026-06-21 | 8319e13 | 4,075 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4261 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
oghie/skillsets · 9 stars · license MIT · pushed 2026-10-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ptz5hbkjso3yec7z GET https://markdownregistry.com/api/v1/resolve?ref=oghie/skillsets/device-driver-development GET https://markdownregistry.com/api/v1/blob/26fa3f81eb95626b532edc4a34534b1acb1a2cc76add83362170a677fc3884a6
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.