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.
87
83%
Does it follow best practices?
Impact
97%
1.11xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 solid description that clearly communicates its purpose and when to use it, with good trigger terms for C++ developers. Its main weakness is a lack of specific concrete actions — it describes the domain well but doesn't enumerate the particular practices or checks it enforces (e.g., memory safety, RAII, smart pointers, type safety).
Suggestions
Add specific concrete actions to improve specificity, e.g., 'Enforces RAII, smart pointer usage, const correctness, type safety, and resource management patterns from the C++ Core Guidelines.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (C++ coding standards) and references the C++ Core Guidelines, but doesn't list specific concrete actions beyond 'writing, reviewing, or refactoring'. It doesn't enumerate what specific standards or practices are enforced (e.g., RAII, smart pointers, const correctness). | 2 / 3 |
Completeness | Clearly answers both 'what' (C++ coding standards based on C++ Core Guidelines for modern, safe, idiomatic practices) and 'when' (explicitly states 'Use when writing, reviewing, or refactoring C++ code'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'C++', 'coding standards', 'C++ Core Guidelines', 'writing', 'reviewing', 'refactoring', 'modern', 'safe', 'idiomatic'. These are terms users would naturally use when seeking help with C++ best practices. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically scoped to C++ Core Guidelines, which is a well-known, specific standard. Unlikely to conflict with general coding skills or other language-specific skills due to the explicit C++ and Core Guidelines references. | 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 thorough, well-structured C++ coding standards reference with excellent executable code examples and a useful final checklist. Its main weakness is length — it's a comprehensive reference document that could benefit from splitting detailed examples into separate files, keeping the SKILL.md as a concise overview. Some rule summary tables restate knowledge Claude already has about modern C++.
Suggestions
Extract detailed code examples (Rule of Five, RAII FileHandle, ThreadSafeQueue, etc.) into a separate EXAMPLES.md or per-topic reference files, keeping SKILL.md as a concise overview with links.
Trim the rule summary tables to only include rules that are non-obvious or frequently violated — Claude already knows many of these C++ best practices and doesn't need every rule enumerated.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive and well-organized, but quite lengthy (~500+ lines). Many of the rule tables restate what Claude already knows about C++ best practices. The DO/DON'T examples are valuable, but the sheer volume of rule summaries (which largely paraphrase the C++ Core Guidelines) adds bulk. Some sections like 'When to Use' explain obvious contexts. | 2 / 3 |
Actionability | Every section includes concrete, executable C++ code examples demonstrating both correct and incorrect patterns. The code is complete, compilable, and copy-paste ready. The checklist at the end provides specific, actionable verification steps with rule references. | 3 / 3 |
Workflow Clarity | This is primarily a coding standards/style guide rather than a multi-step workflow, so the single-task exemption applies. The content is clearly sequenced by topic area, each section has clear DO/DON'T patterns, and the final checklist serves as an explicit validation checkpoint before completing C++ work. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to external files for detailed topics. Given its length (~500+ lines), sections like the full RAII pattern, Rule of Five implementation, or concurrency examples could be split into separate reference files. The structure within the file is good with clear headers, but the sheer volume inline hurts discoverability. | 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 | |
- Repository
- affaan-m/everything-claude-code
- Commit
5df943e
- 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.