How do I install the Cpp Core Guidelines skill?

Run npx skillmds@latest add specterops/cpp-core-guidelines in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cpp Core Guidelines safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cpp Core Guidelines?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cpp Core Guidelines free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cpp Core Guidelines?

specterops (@specterops) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cpp Core Guidelines by specterops — Agent Skill

Name: Cpp Core Guidelines
Author: specterops

Cpp Core Guidelines

Apply a condensed version of the ISO C++ Core Guidelines to C++ design, implementation, refactoring, modernization, and code review. Use for .cpp, .cc, .cxx, .h, .hpp, CMake-backed C++ projects, API design, ownership/lifetime decisions, RAII, const-correctness, templates, concurrency, error handling, performance, C interop, and standard-library usage.

specterops Updated Sep 21, 2026

File contents

C++ Core Guidelines

Overview

Use this skill to apply modern C++ guidance derived from the ISO C++ Core Guidelines. Prefer safer, clearer, statically checkable C++ without sacrificing zero-overhead design.

Workflow

Identify the task shape: new design, implementation, refactor, modernization, review, or bug fix.
Read references/core-guidelines-condensed.md when the task touches C++ behavior, APIs, ownership, templates, concurrency, performance, or code review.
Apply the guidelines pragmatically:
- Prefer explicit interfaces, strong types, invariants, RAII, standard-library facilities, and compile-time checking.
- Preserve project conventions when they conflict only cosmetically.
- Treat raw ownership, unchecked bounds, data races, invalid lifetimes, implicit global state, naked allocation, C casts, and macro-based code as high-priority risks.
When reviewing, lead with concrete bugs and maintenance risks, not style preferences. Reference the relevant Core Guidelines family, such as R for resources, F for functions, or CP for concurrency.
When changing code, keep edits scoped, add regression tests for behavior changes, and prefer mechanical/tool-enforceable improvements.

Resource

references/core-guidelines-condensed.md: condensed concept map and review checklist covering the guideline families: philosophy, interfaces, functions, classes, enums, resources, expressions/statements, performance, concurrency, errors, constants, templates, C interop, source files, standard library, architecture, profiles, GSL, and naming/layout.

---name: cpp-core-guidelinesdescription: Apply a condensed version of the ISO C++ Core Guidelines to C++ design, implementation, refactoring, modernization, and code review. Use for .cpp, .cc, .cxx, .h, .hpp, CMake-backed C++ projects, API design, ownership/lifetime decisions, RAII, const-correctness, templates, concurrency, error handling, performance, C interop, and standard-library usage.---# C++ Core Guidelines## OverviewUse this skill to apply modern C++ guidance derived from the ISO C++ Core Guidelines. Prefer safer, clearer, statically checkable C++ without sacrificing zero-overhead design.## Workflow1. Identify the task shape: new design, implementation, refactor, modernization, review, or bug fix.2. Read `references/core-guidelines-condensed.md` when the task touches C++ behavior, APIs, ownership, templates, concurrency, performance, or code review.3. Apply the guidelines pragmatically: - Prefer explicit interfaces, strong types, invariants, RAII, standard-library facilities, and compile-time checking. - Preserve project conventions when they conflict only cosmetically. - Treat raw ownership, unchecked bounds, data races, invalid lifetimes, implicit global state, naked allocation, C casts, and macro-based code as high-priority risks.4. When reviewing, lead with concrete bugs and maintenance risks, not style preferences. Reference the relevant Core Guidelines family, such as `R` for resources, `F` for functions, or `CP` for concurrency.5. When changing code, keep edits scoped, add regression tests for behavior changes, and prefer mechanical/tool-enforceable improvements.## Resource- `references/core-guidelines-condensed.md`: condensed concept map and review checklist covering the guideline families: philosophy, interfaces, functions, classes, enums, resources, expressions/statements, performance, concurrency, errors, constants, templates, C interop, source files, standard library, architecture, profiles, GSL, and naming/layout.

Frequently asked questions