led-control SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.
led-control from autonomous-ai/physical-ai-operating-system is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add autonomous-ai/physical-ai-operating-system/led-control@git:20260910.44ed5b7Pins git:20260910.44ed5b7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- autonomous-ai/physical-ai-operating-system
- Path
skills/led-control/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260910.44ed5b7, committed Sep 10, 2026
- First version recorded
- Jun 12, 2026
- Size
- 6,940 bytes
- Repository stars
- 479
- License
- Apache-2.0
Control the device's RGB light when the user asks for a SPECIFIC color (e.g. "yellow", "red", "yellow", "red", "turn on color X", "enable X light"), an LED effect, or turning LEDs off. Do NOT use for ambiance/activity lighting (use Scene) or emotion expression (use Emotion).
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
# LED Control
## Quick Start
Control the device's RGB light directly. Use this skill only when the user requests a specific color, effect, or to turn LEDs off.
## Workflow
1. Determine the user's intent:
- Specific color -> `[HW:/led/solid:{"color":[R,G,B]}]`
- Two or more colors / mix / gradient -> `[HW:/led/paint:{"colors":[[R,G,B],[R,G,B]],"gradient":true}]`
- Effect -> `[HW:/led/effect:{"effect":"name","color":[R,G,B],"speed":1.0}]`
- Turn off -> `[HW:/led/off:{}]`
2. Place markers at start of reply — the device fires them in order before TTS
3. Confirm the action to the user
## Examples
Input: "Make it purple" / "turn on purple"
Output: `[HW:/led/solid:{"color":[100,50,200]}]` I've set the LEDs to purple.
Input: "Turn on yellow light" / "set yellow" / "switch to yellow" / "yellow light"
Output: `[HW:/led/solid:{"color":[255,220,0]}]` Yellow light on!
Input: "Turn on red light" / "set red" / "switch to red" / "red light"
Output: `[HW:/led/solid:{"color":[255,0,0]}]` Red light on!
Input: "Turn on white light" / "set white" / "white light"
Output: `[HW:/led/solid:{"color":[255,255,255]}]` White light on!
…Read the whole file at its exact version.
How to install
mdr add autonomous-ai/physical-ai-operating-system/led-control@sha256:df02ce1e2a41fcc3The line at the top of this page pins the label git:20260910.44ed5b7, 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_dittcjwvgdgd442a)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 12, 2026 and Sep 10, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260910.44ed5b7 latest | 2026-09-10 | 44ed5b7 | 6,940 B | A | view · diff |
| git:20260717.3fff8a4 | 2026-07-17 | 3fff8a4 | 7,073 B | A | view · diff |
| git:20260717.b152f31 | 2026-07-17 | b152f31 | 6,011 B | A | view · diff |
| git:20260617.5e71d01 | 2026-06-17 | 5e71d01 | 5,836 B | A | view · diff |
| git:20260612.f444fa9 | 2026-06-12 | f444fa9 | 5,431 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 (6940 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
autonomous-ai/physical-ai-operating-system · 479 stars · license Apache-2.0 · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dittcjwvgdgd442a GET https://markdownregistry.com/api/v1/resolve?ref=autonomous-ai/physical-ai-operating-system/led-control GET https://markdownregistry.com/api/v1/blob/df02ce1e2a41fcc37c0efed256db53869a58f0846338386fd1e2e7fae9872eb4
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.
More from autonomous-ai/physical-ai-operating-system
Every file in autonomous-ai/physical-ai-operating-system