CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/cmock-reference

Pure-reference catalog of CMock and Ceedling mocking semantics for C. Defines what CMock generates from a C header (the full Expect / ExpectAndReturn / ExpectAnyArgs / ExpectWithArray / Ignore / IgnoreAndReturn / IgnoreArg_{param} / ReturnThruPtr_{param} / AddCallback / Stub / ExpectAndThrow naming family), the cmock.yml :plugins list (ignore, ignore_stateless, ignore_arg, expect_any_args, array, callback, cexception, return_thru_ptr) and what each enables, mock-suffix and mock-prefix conventions, how Unity teardown validates expectations, the resetTest mid-test verification, strict vs ignore argument-matching modes, and the trade-offs between mock / stub / spy / fake. Use as the CMock semantics reference when authoring Ceedling tests with mocks or when reading an unfamiliar mock-driven test suite.

74

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

85%

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

An authoritative, well-structured CMock reference: the generated API surface and plugin model are exhaustively documented with executable signatures and a complete worked example, and the lifecycle, matching modes, anti-patterns, and limitations give clear guardrails. Its only weakness is mild verbosity in the overview framing.

Suggestions

Tighten the Overview by paraphrasing the CMock/Ceedling taglines instead of quoting them verbatim, dropping ~30 tokens of filler.

Trim the Meszaros xUnit Test Patterns introduction in the Mock/Stub/Spy/Fake table to a single inline parenthetical; the taxonomy already speaks for itself.

Consider moving the lengthy generated-API block per function to a references file to keep SKILL.md as an overview, though the current single-file structure is acceptable.

DimensionReasoningScore

Conciseness

The body is mostly dense high-signal reference material (generated API signatures, plugin tables) that Claude would not reliably know, but it includes mild padding such as verbatim CMock/Ceedling tagline quotes in the Overview and an introductory Meszaros taxonomy framing that could be trimmed.

2 / 3

Actionability

Provides concrete, copy-paste-ready material: full generated mock API signatures for parse_message, a minimal cmock.yml, mock-naming tables, and a complete worked test_consumer.c example exercising ExpectAndReturn, IgnoreArg, and ReturnThruPtr.

3 / 3

Workflow Clarity

As a reference catalog rather than a destructive/batch workflow, it is cleanly organized with a sequenced setUp/tearDown/resetTest lifecycle table and explicit anti-pattern and limitation guardrails; the scoring notes allow a well-organized single-purpose reference to score 3.

3 / 3

Progressive Disclosure

No bundle files exist; the skill is self-contained with well-organized sections, and the only references are external links (CMock Summary, README) plus named sibling skills, all one level deep and clearly signaled.

3 / 3

Total

11

/

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, complete, and well-triggered: it lists the concrete generated-API family, plugin model, and lifecycle hooks, and gives explicit 'when to use' guidance for both authoring and reading mock-driven suites. It is long but every clause names something concrete rather than padding with fluff.

DimensionReasoningScore

Specificity

Names many concrete actions: 'Defines what CMock generates from a C header (the full Expect / ExpectAndReturn / ExpectAnyArgs / ExpectWithArray / Ignore / IgnoreAndReturn / IgnoreArg_{param} / ReturnThruPtr_{param} / AddCallback / Stub / ExpectAndThrow naming family)' plus plugins, naming conventions, teardown validation, and resetTest.

3 / 3

Completeness

Explicitly answers what ('Pure-reference catalog of CMock and Ceedling mocking semantics...') and when ('Use as the CMock semantics reference when authoring Ceedling tests with mocks or when reading an unfamiliar mock-driven test suite').

3 / 3

Trigger Term Quality

Natural terms a user would say are present: 'CMock', 'Ceedling', 'mocks', 'C', 'embedded' plus the trigger 'when authoring Ceedling tests with mocks or when reading an unfamiliar mock-driven test suite'; proper-noun density is justified by the domain.

3 / 3

Distinctiveness Conflict Risk

A sharply narrow niche (CMock/Ceedling mocking for C) with distinct triggers and explicitly named sibling skills, making 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