Performance Profiling
PassAudited by ClawScan on May 15, 2026.
Overview
This is a reference-only performance profiling cheat sheet with no code or credential use, though some example commands could affect real systems if a user runs them.
This skill appears safe as a profiling reference. Before running any copied commands, confirm the target system, database, or URL is yours or authorized, avoid production-impacting actions without approval, and verify any third-party tools before installing them.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If copied into a production database without care, these commands could interrupt active queries or user activity.
These are database administration commands that can cancel or terminate active database work. They are relevant to performance troubleshooting, but should only be run with explicit user intent on authorized databases.
SELECT pg_cancel_backend(pid); SELECT pg_terminate_backend(pid);
Treat database-changing or session-terminating examples as manual, approval-required actions and verify the target database and PID before use.
Running these examples against a live or third-party site could cause service degradation or policy violations.
The skill documents load-testing commands that generate many HTTP requests. This fits the stated performance purpose, but load tests can disrupt systems if aimed at real services without authorization.
wrk -t4 -c100 -d30s https://example.com hey -n 1000 -c 50 https://example.com
Run load tests only against systems you own or are authorized to test, preferably in staging or with agreed limits.
Installing global tools can affect the local development environment and depends on external package provenance.
The reference suggests installing third-party profiling tools globally. This is expected for a profiling cheat sheet, but users should still verify packages before installing them.
npm install -g clinic npm install -g 0x
Verify package names and sources, consider pinned versions or isolated environments, and avoid global installs unless needed.