CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/unity-test-framework-c

Use for any question or task about unit tests for pure C code on 8-bit MCUs, Cortex-M or embedded Linux, even tests for one function, including which framework fits a tiny-memory target: ThrowTheSwitch Unity (not the Unity game engine) with TEST_ASSERT families, setUp and tearDown, RUN_TEST, the test runner generator, config defines and CI via Ceedling JUnit XML.

Quality

93%

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

86%Weight 40%Scale 1-5

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

A strong, highly actionable reference skill: complete executable code for authoring, host and cross builds, output parsing, and CI, with both bundle files real, clearly signaled, and one level deep. The main weaknesses are mild redundancy (inline citations duplicated in the References section) and the absence of an explicit error-recovery loop around the build/run/parse pipeline. Anti-patterns and Limitations sections are unusually concrete and valuable.

Suggestions

Remove the duplicate link list in the References section or drop the inline citations — keeping both costs tokens without adding information.

Add a short numbered workflow (write test → generate runner → host build → run → gate on ':FAIL:' → cross-build under QEMU) so the sequence and its validation checkpoints are explicit rather than implied by section order.

Add one or two lines of error-recovery guidance (e.g., what to do when a test FAILs or the cross-build misses semihosting) to close the feedback-loop gap in workflow clarity.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence — code carries the explanations and Unity-specific semantics (UNITY_BEGIN/END, exit codes) are genuinely non-obvious, matching the level-4 anchor of minor trimmable instances. It falls short of level 5 because the Overview's linked citations are re-listed verbatim in the References section ("Cited inline. Foundational documents:"), and the game-engine distinction paragraph partially duplicates the frontmatter disambiguation.

4 / 5

Actionability

Fully executable throughout: a complete minimal test file with setUp/tearDown/RUN_TEST/main, the exact `ruby auto/generate_test_runner.rb` invocation, copy-paste host gcc and arm-none-eabi-gcc + QEMU commands, a working `grep -c ':FAIL:'` smoke gate, and a UNITY_OUTPUT_CHAR override snippet. This matches the level-5 anchor (copy-paste ready, covering the common host, cross-build, and CI cases); level 4 would imply missing key details, and none are missing.

5 / 5

Workflow Clarity

The Authoring → Building → Running → Parsing → CI section order presents a clear sequence, and checkpoints exist — the FAIL-line output format is shown for diagnosis and a `grep -c ':FAIL:'` gate plus CI `! grep -q ':FAIL:'` steps verify results, matching the level-4 anchor with most checkpoints present. It does not reach level 5 because steps are organized by topic rather than an explicit ordered workflow, and there is no feedback-loop guidance for recovering from a failed build or test run.

4 / 5

Progressive Disclosure

Verified against the actual bundle: both referenced files (references/assertion-api.md, references/ci-integration.md) exist, are referenced from the body with clear signaling ("The full assertion-family table and the build-time config defines are in [references/assertion-api.md]"; the CI pipeline "is in [references/ci-integration.md]"), and are one level deep with no nested references. The body keeps common assertions inline while pushing the full table and CI YAML out, matching the level-5 anchor of a clear overview with well-signaled one-level-deep references.

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

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

An excellent description: it states explicit trigger conditions in natural user language, enumerates concrete capabilities across the full workflow, and explicitly disambiguates the Unity test library from the Unity game engine. It is dense but every clause carries information, so it avoids padding. No actionable weaknesses identified.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — "TEST_ASSERT families, setUp and tearDown, RUN_TEST, the test runner generator, config defines and CI via Ceedling JUnit XML" — covering authoring, build configuration, and CI comprehensively for the domain. It matches the level-5 anchor (multiple specific concrete actions, comprehensive coverage) and exceeds level 4, which expects minor gaps; no meaningful capability area is missing.

5 / 5

Completeness

Both what and when are explicitly answered: the trigger clause "Use for any question or task about unit tests for pure C code..." states when, and "ThrowTheSwitch Unity ... with TEST_ASSERT families, setUp and tearDown, RUN_TEST, the test runner generator, config defines and CI via Ceedling JUnit XML" states what, with concrete trigger phrases. This mirrors the level-5 good example structure; the explicit 'Use for' clause also satisfies the judging guideline requiring explicit trigger guidance.

5 / 5

Trigger Term Quality

Natural phrases a user would say are comprehensively covered: "unit tests for pure C code", "8-bit MCUs", "Cortex-M", "embedded Linux", "tiny-memory target", "even tests for one function". This spans platform synonyms and informal phrasings (single-function tests) rather than only technical jargon, matching the level-5 anchor; level 4 would require missing natural terms, and none are apparent.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche and actively defuses the highest-risk collision: "ThrowTheSwitch Unity (not the Unity game engine)", further bounded by "pure C code" and "8-bit MCUs, Cortex-M or embedded Linux". Minimal conflict risk with other skills, matching the level-5 anchor; it is more distinct than the level-4 example, which still carries minor overlap risk.

5 / 5

Total

20

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Reviewed

On this page