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.

89

1.11x
Quality

86%

Does it follow best practices?

Impact

97%

1.11x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is cpp-coding-standards in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 strong, actionable standards reference with excellent code examples and clear usage framing, weakened only by its monolithic inlining of a large reference body that would benefit from being split into referenced files.

Suggestions

Move the per-section rule tables and detailed examples into one-level-deep reference files (e.g. references/interfaces.md, references/resources.md) and keep SKILL.md as a concise overview with clearly signaled links, to improve progressive_disclosure.

Trim or remove prose that restates concepts Claude already knows (e.g. general explanations of RAII, constexpr, or what a smart pointer is) to lift conciseness toward 5.

If the body remains a single file, add a compact table of contents near the top so the 700-line monolith is navigable.

DimensionReasoningScore

Conciseness

Mostly efficient lean rule tables paired with targeted DO/DON'T code and rule citations, with only minor over-explanation of concepts Claude already knows; a few prose sections could be trimmed.

4 / 5

Actionability

Provides concrete, copy-paste-ready C++ snippets across every guideline area with explicit rule citations and BAD/GOOD contrasts covering the common cases.

5 / 5

Workflow Clarity

Although not a multi-step process, the skill gives clear 'When to Use' / 'When NOT to Use' guidance plus a final completion checklist; the simple-skill exception applies and guidance is unambiguous.

5 / 5

Progressive Disclosure

Sections are well organized, but no bundle files exist and all ~700 lines of reference content are inlined monolithically rather than split into one-level-deep referenced files.

3 / 5

Total

17

/

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 clear, concrete, and explicitly pairs a 'what' with a 'when' trigger clause, hitting the good-example pattern well. Minor specificity and trigger-term gains are available by adding synonyms and file extensions.

DimensionReasoningScore

Specificity

Names the domain (C++ coding standards) and several concrete actions ('writing, reviewing, or refactoring C++ code'), but 'enforce modern, safe, and idiomatic practices' is somewhat abstract, leaving minor coverage gaps versus a fully comprehensive list.

4 / 5

Completeness

Explicitly answers both 'what' (C++ coding standards based on the Core Guidelines enforcing modern, safe, idiomatic practices) and 'when' ('Use when writing, reviewing, or refactoring C++ code') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrasings ('writing, reviewing, or refactoring C++ code') but omits common synonyms and file extensions such as .cpp, C++17/20, or 'C++ style'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (C++ Core Guidelines) with distinct triggers ('C++ code', reviewing, refactoring) and minimal overlap risk with other 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 (724 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

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.