cpp-pro

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

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cpp-pro/SKILL.md

Quality

Content

65%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 concise, well-organized best-practice checklist for modern C++ with specific, actionable guidance and named tooling. Its main weaknesses are generic template boilerplate and the lack of an explicit sequenced workflow with validation checkpoints.

Suggestions

Remove the generic 'Instructions' boilerplate ('Clarify goals, constraints...', 'Apply relevant best practices and validate outcomes') and the tautological 'cpp pro' phrasing in the use/do-not-use sections; replace with C++-specific guidance.

Add one or two short executable code snippets (e.g. a unique_ptr/RAII example or a CMake minimum-standard snippet) to lift actionability toward copy-paste ready.

Restructure 'Approach' into a sequenced workflow with an explicit validation checkpoint (e.g. compile with warnings, then run ASan/TSan, then benchmark) so the steps and feedback loop are unambiguous.

Dimension	Reasoning	Score
Conciseness	Mostly lean lists, but includes generic boilerplate ('Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes.') and tautological 'cpp pro' phrasing in the use/do-not-use sections that could be tightened.	3 / 5
Actionability	Gives concrete, specific directives — 'Use smart pointers when heap allocation is necessary', 'Follow the Rule of Zero/Three/Five', 'Leverage STL algorithms over raw loops' — and names exact tools (Google Test, Google Benchmark, ASan/TSan, perf/VTune), though no executable code blocks are present.	4 / 5
Workflow Clarity	The numbered 'Approach' list gives a priority order but reads as best-practice principles rather than a sequenced workflow; validation checkpoints are only implicit ('AddressSanitizer/ThreadSanitizer clean output') rather than explicit steps.	3 / 5
Progressive Disclosure	Body is under 50 lines with no bundle files and is organized into clear, well-labeled sections (Focus Areas, Approach, Output), satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	15 / 20 Passed

Description

92%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, specific description that clearly states capabilities and explicit trigger conditions for a well-defined C++ niche. The only gap is the absence of file-extension synonyms in the trigger terms.

Suggestions

Add common file extensions and synonyms to the trigger clause, e.g. 'Use PROACTIVELY for C++ refactoring, memory safety, complex C++ patterns, or .cpp/.h/.cxx files'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'RAII, smart pointers, and STL algorithms', 'Handles templates, move semantics, and performance optimization' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both what ('Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms') and when ('Use PROACTIVELY for C++ refactoring, memory safety, or complex C++ patterns') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural triggers like 'C++ refactoring', 'memory safety', 'complex C++ patterns', but misses common synonyms and file extensions (.cpp, .h, .cxx) that users would say.	4 / 5
Distinctiveness Conflict Risk	Clearly scoped to C++ with distinct triggers (RAII, smart pointers, move semantics, templates), minimal overlap risk with non-C++ skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/cpp-pro/SKILL.md
Commit: 3eff4af

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.