hal-driver-development SKILL.md skillB
hal-driver-development from hyperb1iss/hypercolor is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hyperb1iss/hypercolor/hal-driver-development@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hyperb1iss/hypercolor
- Path
.agents/skills/hal-driver-development/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0.0, committed Aug 26, 2026
- First version recorded
- Apr 26, 2026
- Size
- 25,616 bytes
- Repository stars
- 31
- License
- Apache-2.0
This skill should be used when writing, porting, or debugging device drivers in hypercolor-hal. Triggers on "add a driver", "port a driver", "implement protocol", "device not working", "wire format", "encode frame", "USB HID packet", "zerocopy struct", "CommandBuffer", "device database entry", "transport type", "frame encoding", "protocol implementation", "add device support", or any work in crates/hypercolor-hal/.
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
# Hypercolor HAL Driver Development
## Architecture Boundary
`hypercolor-hal` must never depend on `hypercolor-core` — that would create a circular dependency (`core` depends on `hal`). Dependencies: `hypercolor-color`, `hypercolor-types`, `async-trait`, `thiserror`, `tracing`, `nusb`, `tokio`, `tokio-serial`, `zerocopy`, `hidapi`, `midir`, `image`, `turbojpeg`. Linux adds `alsa`, `async-hid`, `futures-util`, `i2cdev`, `nix`; Windows adds `hypercolor-windows-pawnio`.
## HAL Descriptor or Driver Module?
A HAL device descriptor is not the only way to add hardware support, and it is
the wrong way for most non-USB devices. Every driver module assembled from HAL
descriptors is granted exactly one capability (`database.rs`):
```rust
DriverCapabilitySet {
protocol_catalog: true,
config: false,
discovery: false,
pairing: false,
output_backend: false,
runtime_cache: false,
credentials: false,
presentation: false,
controls: false,
}
```
So a HAL descriptor buys wire-format encoding on the shared USB output backend
and nothing else. If the device needs driver-scoped config, a pairing or
…Read the whole file at its exact version.
How to install
mdr add hyperb1iss/hypercolor/hal-driver-development@sha256:af9d1a5fe7519b2eThe line at the top of this page pins the label v1.0.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_dmf6qbfftxu7ddbk)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 26, 2026 and Aug 26, 2026, about one every 31 days. Its first recorded version is graded A and its latest B.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-08-26 | 05acaca | 25,616 B | B | view · diff |
| v1.0.0 | 2026-08-20 | ab88d1c | 12,880 B | B | view · diff |
| v1.0.0 | 2026-05-23 | 671b857 | 12,818 B | B | view · diff |
| v1.0.0 | 2026-05-22 | 8e210a3 | 12,364 B | B | view · diff |
| v1.0.0 | 2026-04-26 | 4fd7a93 | 11,184 B | A | view |
Audit of the latest version
- fail: No link to a raw IP address (matched: http://127.0.0.1:9420)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (25616 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 script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
hyperb1iss/hypercolor · 31 stars · license Apache-2.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dmf6qbfftxu7ddbk GET https://markdownregistry.com/api/v1/resolve?ref=hyperb1iss/hypercolor/hal-driver-development GET https://markdownregistry.com/api/v1/blob/af9d1a5fe7519b2e47421e3dad3e388a20c4fc37230e491be9da07160754a2a4
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.