performance-engineer
PassAudited by ClawScan on May 4, 2026.
Overview
This instruction-only performance engineering skill is coherent and not suspicious, but some examples show commands that can change database or system settings if copied.
This skill appears safe to install as an instruction-only reference. Before applying any example commands, especially database changes, load tests, or Linux tuning snippets, confirm the target environment, use test systems where possible, and obtain normal operational approval.
Findings (2)
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.
Running these SQL examples on a live database could change indexes or database-wide settings and affect availability or performance.
The database optimization example includes DDL and database configuration changes. These are aligned with performance engineering, but they can affect production behavior if copied without review.
CREATE INDEX CONCURRENTLY idx_orders_user_date_total ... ALTER SYSTEM SET max_connections = 200;
Treat SQL tuning snippets as examples only; test them in staging, review query plans and rollback options, and apply them through normal database change control.
Copying and running the shell snippet could persistently change host CPU, memory, or network behavior and may require root privileges.
The Linux performance tuning example writes to kernel/sysfs/proc settings and appends persistent sysctl configuration. This is expected for system tuning guidance, but it is privileged and environment-impacting.
for cpu in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do
echo performance > $cpu
done
...
cat >> /etc/sysctl.conf << EOFRun system tuning commands only on systems you control, after backing up configuration and validating the settings in a safe environment.