Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
C++/CPP Code Style
v1.0.0C++/CPP代码都用这个coding style, code style, 代码风格,写代码之前阅读下面规则
⭐ 0· 16·0 current·0 all-time
by@daxiali
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's stated purpose is a C++ code style guide and formatter. The SKILL.md refers to running clang-format and editing .clang-format, but the skill metadata requires g++ and gcc. Requiring compilers (g++, gcc) is unnecessary for a style guide/formatter and does not match the actions described; conversely, clang-format (which is needed) is not listed as a required binary.
Instruction Scope
The instructions are focused on style rules and explicitly tell the agent to check and modify the project's .clang-format and to run clang-format on source files (e.g., clang-format -i src/geo/*.hpp tests/*.cpp). This is within the scope of a style/formatting skill, but it does instruct the agent to modify repository files — users should expect automatic source edits.
Install Mechanism
No install spec or code files are present; this is an instruction-only skill. No downloads or installs are requested, so there is low install risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. That is appropriate for a style guide/formatter helper.
Persistence & Privilege
The skill is not always-enabled and can be invoked by the user. It does not request persistent privileges or modify other skills or global agent settings.
What to consider before installing
This skill is primarily a local C++ style guide and formatter helper and appears safe in intent, but take these precautions before using it:
- Confirm tooling: The instructions call for clang-format, but the skill metadata lists g++/gcc instead. Make sure clang-format is installed and available (and that g++/gcc are actually needed) before running any automated formatting.
- Expect file changes: The skill tells the agent to modify .clang-format and run clang-format -i on source files. Run it on a branch or a copy, or commit your work first so you can review changes.
- Verify file paths and scope: The example formatting command targets specific paths (src/geo/*.hpp tests/*.cpp). Ensure the paths match your project or adjust them; automatic recursive edits can touch many files if misconfigured.
- Trust and provenance: The skill has no homepage and an unknown source; if the style rules or automatic edits are important for your project, prefer an internally-reviewed .clang-format and trusted tooling.
If you want to proceed: install and verify clang-format, test the formatting commands on a small sample, and run in a safe/isolated branch so you can inspect changes before merging.Like a lobster shell, security has layers — review code before you run it.
latestvk97efmgcr63b91xff5qy8e4ze184q34y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
⚡ Clawdis
OSLinux · macOS · Windows
Binsg++, gcc
