CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/googletest-embedded-arm

Author and run GoogleTest 1.17+ for embedded C++ on ARM targets - TEST() / TEST_F() / TEST_P() / TYPED_TEST(), EXPECT_* vs ASSERT_* assertions, fixtures with SetUp() / TearDown(), value-parameterised tests, GoogleMock when paired, cross-compile with arm-none-eabi-g++, run on host or under QEMU via the qemu-system-test-runner skill, --gtest_filter / --gtest_output=xml:results.xml / --gtest_shuffle / --gtest_repeat command-line flags, and XML / JSON output parsing for CI. Use when the unit-under-test is C++ (modern C++17+) and the team wants the de-facto C++ test framework instead of the C-only Unity. For C use unity-test-framework-c; for pure C mocks see the CMock reference in ceedling-build-runner.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

92%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 well-structured, highly actionable skill body: executable code and commands, a clearly sequenced host-to-QEMU workflow with explicit CI gating, and clean one-level-deep progressive disclosure into two real reference files. Only minor conciseness trimming of the overview prose would improve it.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence — dense tables, executable commands, embedded-specific gotchas — but the Overview paragraph and a few Primer-quote asides could be trimmed slightly; efficient with minor instances of over-explanation.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout — minimal/fixture test code, the arm-none-eabi-g++ cross-compile command, the QEMU invocation, the CMake config, and the CI yaml — covering the common embedded cases.

5 / 5

Workflow Clarity

Clear sequenced workflows (5-step 'How to use' and an end-to-end 'Worked example' from host to QEMU) with explicit validation checkpoints ('gate the host job on the JUnit XML and the QEMU job on the semihosting exit code', 'echo $?'), complemented by the Anti-patterns table as error-recovery guidance.

5 / 5

Progressive Disclosure

Clear overview body with well-signaled one-level-deep references to real files — [references/authoring-variants.md] and [references/cross-compile-and-ci.md] — cited inline and re-listed in a References section, with advanced content appropriately split out.

5 / 5

Total

19

/

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.

A strong, dense description that concisely enumerates capabilities, includes an explicit 'Use when' trigger with concrete conditions, and clearly disambiguates from sibling C/Unity/Ceedling skills. Both what and when are explicitly covered with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'TEST() / TEST_F() / TEST_P() / TYPED_TEST()', 'EXPECT_* vs ASSERT_*', 'fixtures with SetUp() / TearDown()', 'cross-compile with arm-none-eabi-g++', '--gtest_filter / --gtest_output=xml:results.xml' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what (author and run GoogleTest with enumerated capabilities) and when ('Use when the unit-under-test is C++ ... and the team wants the de-facto C++ test framework instead of the C-only Unity'), with concrete trigger conditions.

5 / 5

Trigger Term Quality

Comprehensive natural terms including synonyms and framework names — 'GoogleTest', 'gtest', 'embedded C++ on ARM', 'de-facto C++ test framework', 'instead of the C-only Unity' — phrases a user would naturally say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

Clear niche (embedded C++ on ARM with GoogleTest) with explicit disambiguation from siblings — 'For C use unity-test-framework-c; for pure C mocks see the CMock reference in ceedling-build-runner' — minimizing wrong-skill triggering.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Reviewed

Table of Contents