OpenClaw Performance

v1.0.0

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

0· 55·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description claim performance analysis; included scripts/main.py implements static analysis, simple checks (N+1, string concat, unused imports, nested loops) and CLI stubs for profiling/benchmarking. No unrelated binaries, env vars, or credentials are requested — all required pieces are consistent with the stated purpose.
Instruction Scope
SKILL.md instructs running the bundled script against project files or directories and shows CI examples. The runtime instructions and the code only read and parse Python source files and present profiling/benchmark guidance. The analyzer reads files under user-specified --file/--dir; this is expected for a code analysis tool. There are no instructions to access unrelated system files, secrets, or external endpoints.
Install Mechanism
No install spec is provided (instruction-only with a bundled script). Nothing is downloaded or extracted; the single included Python script is self-contained and uses only stdlib modules, which is proportionate and low risk.
Credentials
The skill declares no required environment variables or credentials. The code also does not read environment variables or require secrets. This is appropriate for a static profiler/analyzer.
Persistence & Privilege
Skill is not always-enabled and requests no elevated persistence. It does not modify other skills or global agent configuration. Autonomous invocation (platform default) would let the agent run the analyzer, which is reasonable but should be controlled by the user.
Assessment
This skill appears to be what it says: a local Python performance analyzer. Before installing or running it, consider: (1) review the included scripts locally (you already have them) and run them in a sandbox or on a copy of your repository to avoid accidental scans of sensitive directories; (2) the tool reads your source files — do not point it at folders containing secrets or credentials; (3) profiling recommendations (cProfile, timeit) will execute your code if you follow them — only run user code you trust. No credentials or network access are requested, so the primary risk is accidental analysis or execution of untrusted code rather than data exfiltration.

Like a lobster shell, security has layers — review code before you run it.

latestvk978xyhrxzsjskraxjv40kf9fn841d69

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments