CtrlK
BlogDocsLog inGet started
Tessl Logo

cpp-testing

仅在创建/更新/修复 C++ 测试、配置 GoogleTest/CTest、诊断失败或不稳定的测试、以及添加覆盖率或消毒器时使用。

68

Quality

82%

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

65%

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

A thorough, highly actionable C++ testing skill with real executable examples across gtest/gmock, CMake/CTest, coverage, and sanitizers. Its main weaknesses are minor redundancy and a monolithic structure with no reference splitting or explicit validation checkpoints in the debugging flow.

Suggestions

Remove the near-duplicate '基础单元测试' Add example (or repurpose it to show a distinct scenario) and consolidate the repeated ctest invocations into one section.

Add explicit validation checkpoints to the debugging/run flow — e.g. 're-run the failing test; only expand to the full suite once it passes'.

Split the dual GCC/Clang coverage recipes, the fuzzing appendix, and the alternatives into one-level reference files (e.g. coverage.md, fuzzing.md) and link them from a leaner overview.

DimensionReasoningScore

Conciseness

Dense and mostly free of concepts Claude already knows, but the '基础单元测试' Add example near-duplicates the TDD Add example, and the '运行测试' ctest section repeats the quickstart's ctest invocation. Mostly efficient but could be tightened, matching level-2 rather than the lean level-3.

2 / 3

Actionability

Provides fully executable gtest/gmock tests, a complete CMakeLists.txt, and runnable cmake/ctest/lcov/llvm-cov commands — copy-paste ready, matching the level-3 anchor.

3 / 3

Workflow Clarity

The TDD Red→Green→Refactor cycle and the numbered debugging steps give a clear sequence, but debugging/run flows lack explicit validation checkpoints and feedback loops (e.g. 'only proceed when passing'), so it sits at level-2 rather than the checkpoint-rich level-3.

2 / 3

Progressive Disclosure

A single ~325-line monolith with good section headers but no bundle files or one-level references; the dual GCC/Clang coverage recipes, fuzzing appendix, and alternatives are inline reference material that could be split out, fitting the level-2 'content that should be separate is inline' anchor rather than the split, navigable level-3.

2 / 3

Total

9

/

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.

A concise, well-scoped description that states specific C++-testing actions and an explicit 'use only when' trigger. It avoids fluff and is clearly distinguishable from other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '编写/更新/修复 C++ 测试', '配置 GoogleTest/CTest', '诊断失败或不稳定的测试', '添加覆盖率/检测器(Sanitizers)' — matching the level-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

The '仅在...时使用' (Use only when...) clause gives an explicit 'when' trigger, and the enumerated action verbs state the 'what'; both are present, matching the level-3 anchor. Not a 2 because an explicit 'Use when' clause exists rather than being merely implied.

3 / 3

Trigger Term Quality

Uses natural terms a user would say — 'C++ 测试', 'GoogleTest/CTest', '失败或不稳定的测试', '覆盖率', 'Sanitizers' — giving good coverage rather than only jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped narrowly to C++ testing with GoogleTest/CTest, sanitizers, and coverage — a clear niche unlikely to fire for unrelated skills.

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
xu-xiang/everything-claude-code-zh
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.