CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ceedling-build-runner

Use when a C project wants Unity, CMock and CException run by one build command, or CMock mocks need writing or reading: Ceedling project scaffolding, project.yml, test tasks, JUnit XML, gcov coverage, host vs cross builds and CI. The Unity assertion API is unity-test-framework-c.

Quality

89%

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

The canonical home for this skill is testland/ceedling-build-runner

SKILL.md
Quality
Evals
Security

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 well-structured, highly actionable skill body: executable commands and a complete CI recipe, with details appropriately offloaded to verified reference files. The only gaps are minor tightening opportunities and the absence of an explicit test-failure recovery loop.

Suggestions

Add a short failure-recovery step after the parsing section (e.g., on FAIL, use the reported file:line:test:reason to fix the SUT or expectation, then re-run `ceedling test:<module>` before `test:all`) to close the workflow-clarity feedback loop.

Trim editorial framing such as the long prose URL sentence in the scaffolding section and "Per the Ceedling README and the command-line reference at..." down to a bare link to reduce token overhead.

DimensionReasoningScore

Conciseness

Efficient and fact-dense throughout (e.g., "`--local` vendors Unity / CMock / CException into `vendor/ceedling/` so the build doesn't need network at compile time") with no explanation of concepts Claude already knows; minor trims are possible, such as the long prose link text in the scaffolding section.

4 / 5

Actionability

Fully executable guidance: copy-paste-ready scaffold commands, a complete minimal project.yml, module creation, the compound CI invocation "ceedling clobber test:all release gcov:all", and a complete GitHub Actions workflow with report publishing paths.

5 / 5

Workflow Clarity

Clear sequence (scaffold → project.yml → module → run → parse → CI) with an explicit checkpoint ("returns non-zero on any test failure; CI gates on the exit code") and an anti-patterns table, but there is no explicit fix-and-retry feedback loop for failure recovery.

4 / 5

Progressive Disclosure

The spine keeps essentials and defers the full schema, full task surface, and CMock API to three real, clearly signaled one-level-deep files (references/project-yml-schema.md, references/task-reference.md, references/cmock.md), each cited at the point of need.

5 / 5

Total

18

/

20

Passed

Description

87%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 description with an explicit Use-when clause, concrete tool triggers, and good boundary disambiguation against sibling skills. The what-list is specific but noun-heavy, and a couple of natural trigger synonyms ("unit test", "embedded") are absent.

DimensionReasoningScore

Specificity

Lists several specific capabilities ("Ceedling project scaffolding, project.yml, test tasks, JUnit XML, gcov coverage, host vs cross builds and CI") but they are topic labels rather than verb-phrased actions, so coverage is strong with minor gaps rather than comprehensively concrete.

4 / 5

Completeness

Explicitly answers both: "Use when a C project wants Unity, CMock and CException run by one build command, or CMock mocks need writing or reading" gives concrete when-triggers, and the colon-delimited list states what the skill covers; the trailing Unity-API sentence adds boundary clarity.

5 / 5

Trigger Term Quality

Good natural vocabulary users would say ("C project", "Unity", "CMock", "Ceedling", "project.yml", "gcov"), but common phrasings like "unit test"/"unit testing" and "embedded" are missing, keeping it just short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Ceedling orchestration of the ThrowTheSwitch stack) with distinct tool-name triggers and explicit disambiguation ("The Unity assertion API is unity-test-framework-c"), minimizing conflict with sibling skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

testland/qa

Path

plugins/qa-embedded/skills/ceedling-build-runner/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.