OpenClaw Performance

Performance analysis and optimization. Profiles code execution, identifies bottlenecks, and suggests optimizations.

This skill appears to be what it says: a local performance analysis tool that reads your source files and prints suggestions. Before installing or running it: - Review scripts/main.py (and any additional shipped modules) for hidden network calls, subprocess.exec, or file writes. The provided snippet shows only AST/static checks, but review the remainder of the file. - Be careful when following the 'profile' advice: profiling runs your code (cProfile/kernprof). Do not profile untrusted code on a sensitive machine; run in an isolated environment or CI runner. - Note a couple of code-quality issues in the included script (undefined/possibly-missing variables and reliance on a local "c-support" path). Test the tool on a small repository first to confirm behavior. - If you expect C parsing support, check the origin and contents of any c-support modules before allowing them to be imported. Given the lack of external requests, secrets, or remote installs, the skill is coherent with its purpose. However, because the included script has some incomplete/buggy-looking code and imports local libraries conditionally, run it in a sandbox and inspect the full source before use.

Type: OpenClaw Skill Name: oc-performance Version: 1.1.0 The skill bundle provides a static analysis tool for identifying performance bottlenecks in Python and C code. The implementation in `scripts/main.py` uses the `ast` module for Python and basic string/regex matching for C to detect patterns like N+1 queries, nested loops, and inefficient string operations. The tool is safe as it does not execute the analyzed code; the `profile` and `benchmark` commands merely print suggested command-line instructions for the user. While `_analyze_python_file` contains a minor bug (undefined variables), there is no evidence of malicious intent or high-risk behavior.