CtrlK
BlogDocsLog inGet started
Tessl Logo

cpp-coding-standards

C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices.

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

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 highly actionable with comprehensive, executable C++ examples and a useful completion checklist, but it is a large monolithic body that could be tighter and split into reference files for better progressive disclosure.

Suggestions

Move the per-section rule tables and extended code examples into reference files under references/ (e.g. references/classes.md, references/concurrency.md) and keep SKILL.md as a concise overview with one-level-deep links.

Trim repeated anti-pattern bullet lists and inline comments that restate the adjacent code (e.g. '// I.2 violation') to reduce token cost without losing guidance.

Add a brief 'How to apply' workflow that ties the checklist to a review/refactor sequence with an explicit validation checkpoint (e.g. run clang-tidy / compile clean) to lift workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly efficient with no padding about basic C++ concepts, but at ~700 lines it includes repeated anti-pattern bullet lists and rule tables that could be tightened; some inline comments restate what the code already shows.

3 / 5

Actionability

Provides extensive executable, copy-paste-ready C++ examples per rule with paired DO/DON'T blocks and explicit anti-pattern lists covering the common cases across philosophy, functions, classes, resources, exceptions, and concurrency.

5 / 5

Workflow Clarity

As a reference/standards skill it has no multi-step process, but the closing 'Quick Reference Checklist' provides a clear verification loop before marking work complete; no destructive/batch validation cap applies.

4 / 5

Progressive Disclosure

No bundle files exist (references/scripts/assets are absent) and all ~700 lines are inlined in SKILL.md with good section headers, but large reference-grade content that would benefit from being split into separate files is kept inline rather than one level deep.

3 / 5

Total

15

/

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.

The description is strong: it states what the skill provides and when to use it with concrete, natural trigger phrases and a distinct C++ niche. Minor room for improvement exists in adding synonyms and file/standard markers.

DimensionReasoningScore

Specificity

Names the domain ('C++ coding standards based on the C++ Core Guidelines') and several concrete actions ('writing, reviewing, or refactoring C++ code', 'enforce modern, safe, and idiomatic practices'), with only minor coverage gaps; actions are activities rather than discrete capabilities, so it sits just below the comprehensive anchor.

4 / 5

Completeness

Clearly answers 'what' (C++ coding standards from the Core Guidelines) and explicitly answers 'when' via the concrete 'Use when writing, reviewing, or refactoring C++ code' trigger phrase.

5 / 5

Trigger Term Quality

Includes natural terms a user would say ('C++ code', 'writing, reviewing, or refactoring') but omits common synonyms and file/standard markers like '.cpp', 'C++17/20/23', or 'templates', leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to C++ with C++-specific triggers, giving it a clear niche with minimal overlap against non-C++ skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (725 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

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.