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.
Install with Tessl CLI
npx tessl i github:affaan-m/everything-claude-code --skill cpp-coding-standards84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with explicit 'Use when...' guidance and good trigger terms for C++ developers. The main weakness is that it describes the domain and purpose rather than listing specific concrete actions the skill enables (e.g., specific guideline categories or code transformations it can perform).
Suggestions
Add 2-3 specific concrete actions the skill performs, such as 'enforce RAII patterns, apply const-correctness, detect unsafe pointer usage, recommend smart pointer alternatives'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (C++ coding standards, C++ Core Guidelines) and some actions (writing, reviewing, refactoring), but doesn't list specific concrete capabilities like 'enforce RAII patterns, detect memory leaks, apply const-correctness'. | 2 / 3 |
Completeness | Clearly answers both what ('C++ coding standards based on the C++ Core Guidelines... enforce modern, safe, and idiomatic practices') and when ('Use when writing, reviewing, or refactoring C++ code') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'C++', 'C++ code', 'reviewing', 'refactoring', 'modern', 'safe', 'idiomatic'. Also references the authoritative source (C++ Core Guidelines, isocpp.github.io) which users familiar with the standard might mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically C++ (not general coding), specifically the C++ Core Guidelines (not arbitrary style), and specific use cases. Unlikely to conflict with other language-specific or general coding skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, actionable C++ coding standards reference with excellent executable examples and clear organization. The main weakness is its length—while comprehensive, it could benefit from splitting detailed sections into separate files and trimming some redundant anti-pattern explanations. The checklist at the end is a strong validation mechanism.
Suggestions
Consider splitting into multiple files (e.g., CONCURRENCY.md, TEMPLATES.md, RESOURCE_MANAGEMENT.md) with SKILL.md as an overview linking to detailed guides
Consolidate anti-pattern sections—many repeat information already shown in DON'T examples, adding token overhead without new information
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., anti-patterns sections repeat information from DO/DON'T examples). The tables and code examples are efficient, but the overall length (~600 lines) could be trimmed by consolidating overlapping content. | 2 / 3 |
Actionability | Excellent actionability with fully executable C++ code examples throughout. Every section provides copy-paste ready code demonstrating both correct patterns and anti-patterns, with specific rule references (e.g., R.11, ES.20) for traceability. | 3 / 3 |
Workflow Clarity | For a coding standards skill, the workflow is appropriately structured: clear 'When to Use/NOT to Use' section, organized by topic with cross-cutting principles upfront, and a comprehensive checklist at the end for validation before completing work. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a logical progression, but it's monolithic—all content is inline rather than split into separate reference files. For a skill this comprehensive, linking to separate files for detailed sections (e.g., CONCURRENCY.md, TEMPLATES.md) would improve navigation. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- 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.