CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/ceedling-build-runner

Author and run the Ceedling build system for C unit testing - the canonical build orchestration on top of Unity (assertions) + CMock (mocks) + CException (exceptions). Covers ceedling new project scaffolding, the project.yml schema (:project / :paths / :files / :defines / :flags / :tools / :test_runner / :cmock / :unity / :cexception / :gcov / :plugins), the task surface (ceedling test:all, ceedling test:{name}, ceedling test:pattern, ceedling test:path, ceedling release, ceedling clean / clobber, ceedling gcov:all, ceedling module:create, ceedling environment, ceedling dumpconfig), JUnit XML output via the report_tests_pretty_stdout / report_tests_junit_xml plugins, gcov plugin integration, host vs cross-build flow, and CI wiring. Use when a C project wants the standard ThrowTheSwitch trio bundled by one build command. For the Unity assertion API see unity-test-framework-c; for CMock semantics see cmock-reference.

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 body is a tight, executable guide: scaffolding, schema, running, result parsing, and CI are each concrete with copy-paste commands and a realistic compound invocation. Detail is correctly offloaded to two real, well-signaled reference files, and anti-patterns plus limitations round out the guidance without verbosity.

DimensionReasoningScore

Conciseness

Lean and token-efficient: assumes Claude knows what Ruby/Rake/C are and spends tokens only on Ceedling-specific knowledge (layout, schema, task surface, anti-patterns), with no padding about basic concepts.

3 / 3

Actionability

Fully executable, copy-paste-ready commands throughout—'gem install ceedling', 'ceedling module:create[ringbuffer]', 'ceedling clobber test:all release gcov:all', and a complete GitHub Actions workflow with concrete action versions and paths.

3 / 3

Workflow Clarity

Sequenced authoring→running→parsing→CI flow with explicit verification cues: 'test:all returns non-zero on any test failure; CI gates on the exit code', 'Always clobber before the CI run', and 'dumpconfig is the only reliable verifier'.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview that clearly signals one-level-deep references to real bundle files (references/project-yml-schema.md, references/task-reference.md), both of which exist and hold the detailed schema/task surface rather than nesting further.

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 dense, third-person, and concrete—enumerating the schema sections, task surface, and output formats while supplying an explicit 'Use when' trigger. It distinguishes itself from sibling skills via targeted cross-references, leaving little room for misinvocation.

DimensionReasoningScore

Specificity

Lists many concrete actions—scaffolding ('ceedling new project'), the project.yml schema with enumerated sections, the full task surface ('ceedling test:all', 'gcov:all', 'module:create'), JUnit XML output, and CI wiring—rather than vague language.

3 / 3

Completeness

Explicitly answers both what (build orchestration, schema, tasks, output) and when ('Use when a C project wants the standard ThrowTheSwitch trio bundled by one build command').

3 / 3

Trigger Term Quality

Good coverage of natural terms a user would say ('C unit testing', 'Unity', 'CMock', 'embedded', 'mocks', 'coverage', 'ceedling'), with keyword metadata reinforcing discovery.

3 / 3

Distinctiveness Conflict Risk

Clear niche (Ceedling for C/Unity/CMock) with explicit handoffs to sibling skills (unity-test-framework-c, cmock-reference, googletest-embedded-arm) reducing conflict risk.

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