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.

90

1.11x
Quality

Does it follow best practices?

Impact

97%

1.11x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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++ standards reference with strong code examples and a closing validation checklist, but it is a long monolithic SKILL.md that largely restates guidelines Claude already knows and would benefit from splitting detailed sections into reference files. The main gaps are token efficiency and file-level progressive disclosure.

Suggestions

Split the per-section rule catalogs (e.g. Concurrency, Templates, Resource Management) into separate files under references/ and keep SKILL.md as a concise overview with one-level-deep links, improving progressive disclosure and reducing inline tokens.

Trim or collapse the inline rule-summary tables to only the rules and rationale Claude would not reliably already know; lean on the linked C++ Core Guidelines for exhaustive coverage to improve conciseness.

Add a short 'How to apply' workflow at the top (locate the relevant section by concern -> apply DO/DON'T patterns -> verify against the checklist) so the application sequence is explicit before the reference material begins.

DimensionReasoningScore

Conciseness

The body is largely dense rule tables and code rather than fluff, but at ~720 lines it re-enumerates a near-comprehensive set of C++ Core Guidelines that Claude largely already knows inline, so it could be tightened and trimmed for token efficiency. It is not the score-3 'lean and efficient; every token earns its place' case, but it avoids the score-1 verbose-concept-explanation pattern.

2 / 3

Actionability

Abundant concrete, executable C++ examples (Rule of Zero/Five, RAII FileHandle, smart-pointer usage, scoped_lock, concepts) plus DO/DON'T contrasts and copy-paste-ready snippets, matching the score-3 'fully executable code; copy-paste ready' anchor.

3 / 3

Workflow Clarity

Though a reference rather than a fragile multi-step pipeline, it closes with an explicit 'Quick Reference Checklist' gated as 'Before marking C++ work complete' — a validation checkpoint for a complex process, fitting the score-3 anchor and the simple-skill scoring note.

3 / 3

Progressive Disclosure

Internally well-organized into themed sections, but it is a monolithic single-file document with no bundle files and no one-level-deep references; the detailed per-section reference content that should live in separate files is all inline in SKILL.md. This matches the score-2 anchor ('content that should be separate is inline') rather than score 1 (poorly organized) or score 3 (well-signaled split references).

2 / 3

Total

10

/

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 strong, third-person description that cleanly states what the skill does and when to use it with explicit, natural trigger terms and a distinct C++-only niche. No material weaknesses; the description earns full marks across all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'writing, reviewing, or refactoring C++ code' — paired with the concrete goal of enforcing 'modern, safe, and idiomatic practices', matching the score-3 anchor of several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('C++ coding standards based on the C++ Core Guidelines ... to enforce modern, safe, and idiomatic practices') and when (explicit 'Use when writing, reviewing, or refactoring C++ code' trigger clause), satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

Natural user-facing terms are well covered ('writing, reviewing, refactoring C++ code', 'C++ coding standards'), all phrases a user would plausibly say when needing the skill; uses third-person voice with no first/second-person phrasing to penalize.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to C++ and names a specific source (C++ Core Guidelines / isocpp.github.io), giving it a clear niche unlikely to fire for non-C++ skills.

3 / 3

Total

12

/

12

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.