CtrlK
BlogDocsLog inGet started
Tessl Logo

cpp-core-review

Load when reviewing, refactoring, modernizing, debugging, or designing non-trivial C++ code where ownership, lifetime, RAII, concurrency, templates, interfaces, exceptions, or Core Guidelines compliance may affect correctness, safety, maintainability, or performance.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

The canonical home for this skill is cpp-core-review in zhxc372/cpp-ai-constitution

SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, well-organized, and highly actionable with clear sequenced workflows and a strong condition-based reference map. Its one real defect is progressive disclosure: four referenced files are missing from the bundle, breaking navigation for those entries.

Suggestions

Create the missing referenced files (GOTCHAS.md, templates/phase0-starter.md, PROJECT_CONSTITUTION.md, ADAPTER_POLICY.md) or remove/repoint the references so every cited path resolves to an existing bundle file.

In the 'Condition Loading' and 'Gotchas' sections, prefer the same markdown-link style used elsewhere and confirm each link target exists, so navigation is uniformly one-level-deep and resolvable.

Optionally surface the existing scripts/ (e.g. run_clang_tidy.py, validate_repo.py) from the 'Tool First' section so the tooling guidance points at executable helpers already in the bundle.

DimensionReasoningScore

Conciseness

Lean throughout with no textbook padding ('Do not mechanically replace raw pointers. Classify first:'); assumes Claude's C++ competence and lets every line earn its place, matching the level-3 anchor.

3 / 3

Actionability

Concrete, specific actionable guidance throughout (ordered review priority, a tool-discovery checklist, a 6-class ownership taxonomy, a 5-bucket severity scheme, and a concrete 'Run clang-tidy' command). As an instruction-style skill the absence of copy-paste code is not penalized because the guidance is concrete and complete, so it clears level 3 over the 'incomplete/missing key details' level 2.

3 / 3

Workflow Clarity

Multi-step processes are clearly sequenced as numbered lists (Review Priority 1-8, Tool First 1-6, Modernization Discipline 1-4) with explicit guardrail checkpoints ('Never mix safety-critical changes with style rewrites', 'Do not modernize code before preserving behavior'). This is a non-destructive review skill, so the missing validate/rebuild feedback loop does not cap it at 2.

3 / 3

Progressive Disclosure

Structure and signaling are excellent — a short root file, an explicit Condition Loading map to one-level-deep references, and a constitution rule mandating 'Heavy material goes to references/' — but four referenced paths do not exist in the bundle (GOTCHAS.md, templates/phase0-starter.md, PROJECT_CONSTITUTION.md, ADAPTER_POLICY.md), so navigation is partially broken. This fits level 2 ('some structure ... references present but navigation undermined') rather than the fully navigable level 3.

2 / 3

Total

11

/

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.

The description is strong: it uses an explicit 'Load when' trigger, names concrete actions, and scopes the skill to a distinct C++-review niche with specific concern areas. It cleanly satisfies the what/when/specificity bar.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('reviewing, refactoring, modernizing, debugging, or designing') plus the specific C++ concern areas they apply to, matching the multi-action anchor rather than the single-action level 2.

3 / 3

Completeness

Explicitly answers both what (the review/refactor/etc. actions and the concern domains) and when via the 'Load when ...' trigger clause, satisfying the level-3 'what AND when' anchor.

3 / 3

Trigger Term Quality

Natural terms a user would say ('reviewing', 'refactoring', 'modernizing', 'debugging', 'designing ... C++ code') with broad coverage; not below level 2 since common variations are present, and it exceeds level 2 by spanning several real phrasings.

3 / 3

Distinctiveness Conflict Risk

Scoped to 'non-trivial C++ code' with specific concern keywords (RAII, lifetime, Core Guidelines), giving it a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zhxc372/cpp-ai-constitution
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.