ClawHub

Performance Tuning

v1.0.0

Deep performance tuning workflow—goals and measurement, profiling, hotspots, caching and concurrency trade-offs, system-specific tuning (DB, GC, network), an...

⭐ 0· 103·0 current·0 all-time
by@mikeclaw007
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 and description match the provided content. The skill is an advisory workflow and requests no credentials, binaries, or config access — which is appropriate for a guidance-only performance-tuning skill.
✓
Instruction Scope
SKILL.md contains step-by-step, measurement-driven guidance and tool suggestions but does not instruct the agent to read local files, access environment variables, call external endpoints, download or execute code, or collect/transmit sensitive data. It stays within the stated advisory scope.
✓
Install Mechanism
No install spec and no code files — instruction-only. This minimizes disk writes and runtime installation risk.
✓
Credentials
No environment variables, credentials, or config paths are required or referenced. The lack of requested secrets is proportionate to an advisory workflow.
✓
Persistence & Privilege
always is false and the skill does not request persistent system presence or modifications to other skills. Autonomous invocation is allowed by default but the skill's content is advisory and does not perform privileged operations.
Assessment
This skill is a benign, high-level checklist for performance tuning and does not request credentials or install anything. Consider these practical points before enabling it: (1) it provides advice only — it will not run profilers or change systems unless paired with other skills or human-invoked actions; (2) because the source is unknown, avoid pasting sensitive production traces or secrets into prompts when seeking guidance; (3) if you later augment the skill with automation (scripts, installs, or profiling commands), re-evaluate for permissions and network/download risks; (4) test recommendations in a safe environment (staging/canary) before applying to production.

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

latestvk978drv14ckpckp2f0gt6a84ax83kerc

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments