CtrlK
BlogDocsLog inGet started
Tessl Logo

cpp-testing

Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

The content is actionable and well-structured with executable examples across the core testing workflow, coverage, and sanitizers. It is concise and clearly sequenced, with only minor gaps in explicit validation checkpoints and inline-everything organization.

Suggestions

Add explicit validation/retry feedback loops (e.g., 're-run the single failing test; if still red, re-run with sanitizers; only expand to the full suite once green') to the Debugging Failures workflow.

Consider splitting the lengthy Coverage and Sanitizers CMake/bash recipes into a references file to reduce SKILL.md size and improve progressive disclosure.

Trim the opening 'Agent-focused testing workflow...' line and other restating sentences that repeat what the When to Use section already conveys.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's knowledge, with only minor descriptive padding such as the opening 'Agent-focused testing workflow...' line, so it is efficient but not perfectly trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready code for gtest, gmock, CMake/CTest, coverage, and sanitizers covering the common cases, with any pseudocode stubs explicitly justified.

5 / 5

Workflow Clarity

The RED→GREEN→REFACTOR loop and numbered debugging steps give a clear sequence, but validation/retry feedback loops are implicit rather than explicit checkpoints.

4 / 5

Progressive Disclosure

The single ~326-line file is well-sectioned with clear headers and no nested references, but all content is inlined since no bundle files exist, leaving minor organization headroom.

4 / 5

Total

17

/

20

Passed

Description

83%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.

The description is specific, well-triggered, and distinct, explicitly pairing concrete actions with a 'Use only when' clause. It is close to optimal but the capability statement ('what') is woven into the trigger list rather than stated independently.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('writing/updating/fixing C++ tests', 'configuring GoogleTest/CTest', 'diagnosing failing or flaky tests', 'adding coverage/sanitizers'), matching the comprehensive-coverage anchor.

5 / 5

Completeness

An explicit 'Use only when...' clause answers 'when' with concrete triggers, and the action list conveys 'what', but the 'what' is embedded in triggers rather than a standalone capability statement, so it is not a clean 5.

4 / 5

Trigger Term Quality

Strong natural terms ('C++ tests', 'GoogleTest/CTest', 'flaky tests', 'sanitizers') but misses common synonyms like 'unit tests' or 'gmock', landing just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

A tight C++ testing niche with GoogleTest/CTest-specific triggers makes it clearly distinguishable with minimal conflict risk against other skills.

5 / 5

Total

18

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.