Back to catalog
Human reviewedDevelopment

Skill dossier

cpp-pro

Source declaration

Writes, optimizes, and debugs C++ applications using modern C++20/23 features, template metaprogramming, and high-performance systems techniques. Use when building or refactoring C++ code requiring concepts, ranges, coroutines, SIMD optimization, or careful memory management — or when addressing performance bottlenecks, concurrency issues, and build system configuration with CMake.

The author's original description, preserved in English. It describes intent, not verified performance.

Writes, optimizes, and debugs C++ applications using modern C++20/23 features, template metaprogramming, and high-performance systems techniques. Use when building or refactoring C++ code requiring concepts, ranges, coroutines, SIMD optimization, or careful memory management — or when addressing performance bottlenecks, concurrency issues, and build system configuration with CMake.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

Guides modern C++20/23 development with concepts, RAII, smart pointers and CMake, requiring sanitizer runs and benchmarking before work counts as done.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Reviews the build system, compiler flags and performance requirements first.
  • Designs type-safe interfaces with C++20 concepts.
  • Applies RAII, constexpr and move semantics while avoiding raw new and delete.
  • Runs AddressSanitizer and UndefinedBehaviorSanitizer, then profiles with real workloads.

Limitations & scope

  • Needs a compiler and toolchain that supports C++20/23, sanitizers and CMake.
  • Performance targets are left to the user; the file gives no numbers.
  • SIMD, concurrency and template detail sit in separate reference files.

Relevant for

  • C++ developers modernizing existing code
  • Systems programmers needing safe resource management
  • Teams setting up CMake builds with sanitizers

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
47.8 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/cpp-pro/references/build-tooling.mdReference9.5 KB
skills/cpp-pro/references/concurrency.mdReference10.7 KB
skills/cpp-pro/references/memory-performance.mdReference8.9 KB
skills/cpp-pro/references/modern-cpp.mdReference6.4 KB
skills/cpp-pro/references/templates.mdReference7.7 KB
skills/cpp-pro/SKILL.mdInstruction4.6 KB

SKILL.md frontmatter

{
  "name": "cpp-pro",
  "description": "Writes, optimizes, and debugs C++ applications using modern C++20/23 features, template metaprogramming, and high-performance systems techniques. Use when building or refactoring C++ code requiring concepts, ranges, coroutines, SIMD optimization, or careful memory management — or when addressing performance bottlenecks, concurrency issues, and build system configuration with CMake.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "language",
    "triggers": "C++, C++20, C++23, modern C++, template metaprogramming, systems programming, performance optimization, SIMD, memory management, CMake",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "rust-engineer, embedded-systems"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Analyze architecture

    Review the build system, compiler flags and performance requirements.

  2. 02
    Action

    Design with concepts

    Create type-safe interfaces using C++20 concepts.

  3. 03
    Decision

    Gate on sanitizers

    If AddressSanitizer or UndefinedBehaviorSanitizer report issues, fix all memory and UB errors first.

  4. 04
    Output

    Deliver code and notes

    Provide headers, implementation, CMake updates, a usage test and design notes.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

293 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Note

File modification is described or implemented

287 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 287 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

6 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 6 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Review any build, sanitizer or benchmark commands it proposes, and treat memory-safety fixes as needing your own testing.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/cpp-pro # .claude/skills/cpp-pro
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/cpp-pro/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Install the skill into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Confirm cpp-pro/SKILL.md exists at the destination, then ask Claude Code to use the cpp-pro skill on a small test task.

Prerequisites

  • Needs a compiler and toolchain that supports C++20/23, sanitizers and CMake.
  • Performance targets are left to the user; the file gives no numbers.
  • SIMD, concurrency and template detail sit in separate reference files.

Example prompts

Representative task

Use the cpp-pro skill to refactor src/buffer.cpp to use RAII and C++20 concepts, update the CMakeLists.txt with warnings and sanitizers, and explain your design decisions.

Inspect before use

Read the cpp-pro skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/cpp-pro/SKILL.md and its referenced files. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Makes sanitizers and all compiler warnings mandatory.
  • Provides compact examples for concepts, RAII wrappers and smart pointers.

Considerations

  • Rules such as always using auto may not fit every codebase style.
  • Applying them to legacy code may mean large refactors.
Research conclusion

A disciplined modern C++ rule set that fits best on codebases able to adopt C++20 and sanitizers.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/cpp-pro
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.