hardware-iot-bus
Skill16 starsChanged 8 months agoMITView on GitHub
Low-level I2C and SPI bus peripheral control for embedded Linux boards (Orange Pi, Raspberry Pi, RISC-V).
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use this skill to interface directly with physical sensors, displays, and microcontrollers on Linux Single Board Computers (SBCs).
- Very specific: line 17
Read register values: i2cget -y <bus> <chip-address> <data-address>
- Very specific: line 18
Write register values: i2cset -y <bus> <chip-address> <data-address> <value>
- Distinctive: line 24
Verify pinouts and voltage levels (3.3V vs 5V) before writing registers.
- Distinctive: line 25
Always perform address scanning before initializing sensor read loops.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
⚡ Hardware I2C & SPI Bus Skill
Use this skill to interface directly with physical sensors, displays, and microcontrollers on Linux Single Board Computers (SBCs).
Bus Protocol Features
- I2C Protocol:
- Scan active bus addresses:
i2cdetect - Read register values:
i2cget -y <bus> <chip-address> <data-address> - Write register values:
i2cset -y <bus> <chip-address> <data-address> <value>
- Scan active bus addresses:
- SPI Protocol:
- Full-duplex byte transfers to
/dev/spidevX.Y - Mode configuration (Clock polarity/phase, speed Hz)
- Full-duplex byte transfers to
Edge Safety Guidelines
- Verify pinouts and voltage levels (3.3V vs 5V) before writing registers.
- Always perform address scanning before initializing sensor read loops.
In this repository8 other files it gives its agents.
- workspace/AGENTS.mdAGENTS.md
- android-adb-controlSkill
- autonomous-dev-teamSkill
- browser-automation-cdpSkill
- gmailSkill
- guardian-self-evolutionSkill
- mcp-protocol-suiteSkill
- web-searchSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.