hardware-in-loop-reference SKILL.md skillA
hardware-in-loop-reference from testland/qa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testland/qa/hardware-in-loop-reference@v1.3.6Pins v1.3.6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testland/qa
- Path
plugins/qa-embedded/skills/hardware-in-loop-reference/SKILL.md- Versions recorded
- 5
- Latest version
- v1.3.6, committed Oct 11, 2026
- First version recorded
- Jun 15, 2026
- Size
- 14,152 bytes
- Repository stars
- 11
- License
- MIT
Pure-reference catalog of hardware-in-the-loop (HIL) testing for embedded systems. Defines the HIL pattern (ECU-under-test + real-time plant simulator + I/O cards emulating sensors / actuators / buses), the V-cycle progression (MIL → SIL → PIL → HIL), the canonical vendor stack (NI VeriStand + PXI / CompactRIO, dSPACE SCALEXIO / MicroAutoBox, Vector CANoe + VT System, Speedgoat real-time targets), bus emulation per protocol (CAN / CAN FD / LIN / FlexRay / Automotive Ethernet / SOME-IP)…
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
# hardware-in-loop-reference ## Overview Hardware-in-the-loop (HIL) is, per [en.wikipedia.org/wiki/Hardware-in-the-loop_simulation](https://en.wikipedia.org/wiki/Hardware-in-the-loop_simulation), "a technique that is used in the development and testing of complex real-time embedded systems" that "provides an effective testing platform by adding the complexity of the process-actuator system, known as a plant, to the test platform". In practice it means: the production ECU runs production firmware against a real-time simulator that emulates the rest of the vehicle / aircraft / machine in closed loop, with the same electrical interfaces the ECU sees in the field. This skill is a **pure reference** consumed by the per-tool skills (`googletest-embedded-arm`, `unity-test-framework-c`, `qemu-system-test-runner`) when teams need to decide what slips into HIL versus what stays in host / QEMU. ## When to use - Scoping a new HIL rig - what hardware, what protocols, what level of plant fidelity. - Reading an HIL test report from a vendor (NI / dSPACE / Vector / Speedgoat) and translating their proprietary terms. - Negotiating the V-model split (MIL / SIL / PIL / HIL) with safety …
Read the whole file at its exact version.
How to install
mdr add testland/qa/hardware-in-loop-reference@sha256:c3c6d00833fba4ffThe line at the top of this page pins the label v1.3.6, 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_34sevcvugiqafqip)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 15, 2026 and Oct 11, 2026, about one every 30 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.3.6 latest | 2026-10-11 | a1bd3f7 | 14,152 B | A | view · diff |
| git:20260724.d4db756 | 2026-07-24 | d4db756 | 14,133 B | A | view · diff |
| git:20260719.6226ac1 | 2026-07-19 | 6226ac1 | 14,405 B | A | view · diff |
| git:20260706.4e1409c | 2026-07-06 | 4e1409c | 14,411 B | A | view · diff |
| git:20260615.c62f985 | 2026-06-15 | c62f985 | 14,428 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 (14152 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
testland/qa · 11 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_34sevcvugiqafqip GET https://markdownregistry.com/api/v1/resolve?ref=testland/qa/hardware-in-loop-reference GET https://markdownregistry.com/api/v1/blob/c3c6d00833fba4ff2bf12c54f04fb830d5cbe61df2f8ead4ef856ca4d39ce8de
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.