CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/hardware-in-loop-reference

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), fault-injection patterns (short-to-ground, open-circuit, signal corruption), DO-178C / ISO 26262 / IEC 61508 alignment, and the test-evidence chain HIL produces. Use as the HIL terminology + vendor + standard reference when scoping an embedded test rig or interpreting an automotive / aerospace / industrial HIL test report.

79

Quality

99%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a lean, dense reference that adds only what Claude would not already know, with concrete executable examples and well-organized navigation. It avoids explaining basic concepts and keeps every section purposeful.

DimensionReasoningScore

Conciseness

The body is dense factual reference data (vendor tables, protocol tables, fault-pattern tables, standard clauses) with almost no padding of concepts Claude already knows — every token earns its place as lookup material rather than explanation.

3 / 3

Actionability

Provides complete executable examples (a real CAPL test module and a VeriStand real-time sequence) plus concrete specifics — file formats (`.nivssdf`), exact ISO clauses, named tools — giving copy-ready, specific guidance for scoping and interpreting rigs.

3 / 3

Workflow Clarity

As a well-organized reference skill it has clear sections (When to use, HIL pattern, V-cycle progression table, Anti-patterns with why/fix, Limitations); the V-cycle table sequences the stages explicitly and the anti-patterns give concrete remediation, so the single reference action is unambiguous.

3 / 3

Progressive Disclosure

No bundle directories (references/scripts/assets) exist; the skill is a single self-contained file with clear headers and no nested references, so its flat, well-organized structure is appropriate for a pure-reference skill.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, complete on both what and when, and occupies a clearly distinct niche. It uses third-person voice throughout with no first/second-person phrasing, satisfying the voice guideline.

DimensionReasoningScore

Specificity

Enumerates many concrete catalogue elements — 'the HIL pattern (ECU-under-test + real-time plant simulator + I/O cards)', 'the V-cycle progression (MIL → SIL → PIL → HIL)', named vendor stacks, per-protocol bus emulation, and specific fault-injection patterns — matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both halves: what ('Pure-reference catalog ... Defines the HIL pattern ...') and when ('Use as the HIL terminology + vendor + standard reference when scoping an embedded test rig or interpreting an ... HIL test report'), with an explicit 'Use ... when' trigger.

3 / 3

Trigger Term Quality

Natural user-facing terms are well covered: 'hardware-in-the-loop (HIL) testing', 'embedded systems', 'automotive / aerospace / industrial HIL test report', and 'embedded test rig' — the phrases a user would naturally say when scoping or reading a HIL rig.

3 / 3

Distinctiveness Conflict Risk

The HIL-testing niche is sharply defined and clearly separated from sibling per-tool skills (googletest-embedded-arm, unity-test-framework-c, qemu-system-test-runner), with distinct triggers that make it unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents