CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cpp-pro

Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms. Handles templates, move semantics, and performance optimization. Use for C++ refactoring, memory safety, or complex C++ patterns.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/cpp-pro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 compact, well-sectioned body that names the right tools and best practices, but it is heavy on generic boilerplate and light on substance: no code examples, no executable commands, and no explicit validation workflow. It reads more as a topic checklist of things Claude already knows than as skill-specific guidance that changes behavior.

Suggestions

Delete the boilerplate 'Use this skill when', 'Do not use this skill when', and 'Instructions' sections — their content ('Working on cpp pro tasks or workflows', 'Apply relevant best practices and validate outcomes') is fully redundant with the frontmatter description and adds no information.

Add one or two executable code examples showing the skill's preferred patterns in action (e.g., a Rule-of-Zero class using unique_ptr, a std::ranges algorithm replacing a raw loop) so the guidance is concrete rather than a list of principles.

Turn the Approach list into a sequenced workflow with an explicit validation checkpoint (e.g., 'compile with -Werror -Wconversion', 'run unit tests', 'verify ASan/TSan clean before delivering'), replacing the vague 'validate outcomes' instruction.

DimensionReasoningScore

Conciseness

The file is short, but three sections are pure boilerplate — 'Working on cpp pro tasks or workflows', 'The task is unrelated to cpp pro', and 'Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes.' — and 'Focus Areas' re-lists standard C++ knowledge Claude already has. Mostly efficient but includes unnecessary filler that could be trimmed; not 2 because there is no explanatory prose padding and overall length is modest.

3 / 5

Actionability

Names concrete tools and deliverables (perf, VTune, Google Test, Catch2, Google Benchmark, ASan/TSan, CMakeLists.txt with a C++ standard) and specific rules (Rule of Zero/Three/Five, const correctness), but contains zero code examples or executable commands, and the Instructions section is vague. Some concrete guidance but incomplete — a code skill with no runnable example can't reach 4.

3 / 5

Workflow Clarity

The 'Approach' list is numbered but states priorities rather than a sequenced workflow, and validation exists only implicitly through the Output section (ASan/TSan-clean output, unit tests). Steps are listed with implicit checkpoints and no explicit verify step, matching anchor 3; not 2 because outputs do define what 'done' looks like.

3 / 5

Progressive Disclosure

The body is under 50 lines, entirely self-contained with no bundle files, and organized into clearly labeled sections (Use when, Don't use when, Instructions, Focus Areas, Approach, Output). Per the rubric's guideline for short skills with no need for external references, well-organized sections alone earn a 5.

5 / 5

Total

14

/

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.

A strong description that clearly states concrete capabilities and includes an explicit 'Use for...' trigger clause with natural keywords. Its only weaknesses are the absence of file-extension triggers and a couple of unqualified trigger terms ('memory safety', 'performance optimization') that create minor overlap risk with adjacent domains.

DimensionReasoningScore

Specificity

Lists several concrete capabilities — 'RAII, smart pointers, and STL algorithms', 'templates, move semantics, and performance optimization' — with only minor gaps. Falls short of 5 because these are topic areas under a single action verb ('Write idiomatic C++ code') rather than multiple distinct concrete actions as in the anchor-5 example.

4 / 5

Completeness

Explicitly answers both: what ('Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms. Handles templates, move semantics, and performance optimization.') and when ('Use for C++ refactoring, memory safety, or complex C++ patterns.') with concrete trigger phrases. Not 4 because the when-clause is already explicit and specific rather than merely adequate.

5 / 5

Trigger Term Quality

'Use for C++ refactoring, memory safety, or complex C++ patterns' plus terms like smart pointers, RAII, and move semantics are phrases users would naturally say. Not 5 because file extensions (.cpp, .hpp) and common synonyms (e.g., 'modernize C++') are missing; well above 3 due to varied, natural keyword coverage.

4 / 5

Distinctiveness Conflict Risk

Clear C++ niche with mostly C++-qualified triggers ('C++ refactoring', 'complex C++ patterns'), but 'memory safety' and 'performance optimization' are unqualified and could overlap with Rust or general performance skills. Matches anchor 4 (mostly distinct, minor overlap risk with closely related skills) rather than 5's minimal-conflict bar.

4 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/cpp-pro/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.