Skills cpp-pro

📦

cpp-pro

Name: cpp-pro
Author: sickn33

Content revision r2 Safe 🌐 Network access⚙️ External commands

Build Modern, Reliable C++ Software

Complex C++ systems can hide ownership, concurrency, and performance problems. This skill applies modern language features, RAII, testing, and profiling practices to produce maintainable solutions.

Supports: Claude Codex Code(CC)

📊 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "cpp-pro" from https://skillstore.io/skills/sickn33-cpp-pro.md and its manifest at https://skillstore.io/api/skills/sickn33-cpp-pro/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-cpp-pro.md Signed manifest GET /api/skills/sickn33-cpp-pro/manifest Signed lockfile GET /api/skills/sickn33-cpp-pro/lockfile

Test it

Using "cpp-pro". Review a class that owns a file handle and manually closes it.

Expected outcome:

Ownership finding: cleanup depends on every exit path and is not exception safe.
Recommended design: use a move-only RAII wrapper with deterministic cleanup.
Verification: test normal destruction, moves, failed acquisition, and early returns.

Using "cpp-pro". Create a quality checklist for a new C++20 library.

Expected outcome:

Build: target-based CMake, explicit language standard, warnings, and dependency declarations.
Correctness: focused unit tests plus AddressSanitizer and UndefinedBehaviorSanitizer runs.
Maintenance: documented ownership, stable interfaces, static analysis, and continuous integration.

Using "cpp-pro". Assess a slow multithreaded queue.

Expected outcome:

First measure throughput, latency, contention, allocation frequency, and cache misses.
Check lock scope, wake-up policy, shutdown behavior, and race detector results.
Optimize only the measured bottleneck and compare against the original baseline.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

All 51 static findings are false positives in the documented context. The URL is a canonical CMake dependency example, backticks mark a file path, and the reconnaissance matches are ordinary C++ declarations or documentation.

Files scanned

2,047

Lines analyzed

Review items

False positives ignored

Risk Factors

🌐 Network access (1)

references/build-tooling.md:49

⚙️ External commands (1)

SKILL.md:24

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-cpp-pro/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-cpp-pro/security.svg)](https://skillstore.io/skills/sickn33-cpp-pro?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-cpp-pro?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-cpp-pro/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-cpp-pro.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). cpp-pro security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-cpp-pro/audits/5

BibTeX citation

@techreport{sickn33-sickn33-cpp-pro-2026,
  author = {sickn33},
  title = {cpp-pro security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/sickn33-cpp-pro/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "cpp-pro security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-cpp-pro/audits/5"
identifiers:
  - type: other
    value: "skillstore:sickn33-cpp-pro:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Modernize Legacy C++

Replace manual ownership and older idioms with RAII, standard containers, algorithms, and clear interfaces.

Improve Concurrent Performance

Select synchronization, memory ordering, data layout, and profiling techniques for measured bottlenecks.

Standardize Build Quality

Create CMake targets, tests, sanitizers, static analysis, benchmarks, and continuous integration workflows.

Try These Prompts

Explain a Modern C++ Concept

Explain [concept] for a beginner using C++20. Include its purpose, a small example, common mistakes, and a simple verification step.

Refactor Ownership

Review the provided C++ code for ownership and lifetime problems. Refactor it with RAII and smart pointers while preserving behavior.

Design a Tested Component

Design a C++20 [component] with clear interfaces, exception guarantees, CMake targets, and unit tests. State assumptions and portability constraints.

Analyze Concurrent Performance

Analyze this concurrent C++ implementation for races, deadlocks, contention, memory ordering, and cache effects. Propose measured improvements and sanitizer tests.

Best Practices

State the C++ standard, compiler versions, platform constraints, and required behavior before designing a solution.
Validate generated changes with compilation, focused tests, sanitizers, static analysis, and benchmarks where relevant.
Use measurements to justify performance changes and document ownership, lifetime, and synchronization assumptions.

Avoid

Do not introduce raw owning pointers or manual cleanup when a standard RAII type can express ownership.
Do not use lock-free algorithms or relaxed memory ordering without proving correctness and testing under contention.
Do not claim performance improvements without a representative baseline and repeatable benchmark.