performance-engineer

AdvisoryAudited by Static analysis on May 4, 2026.

Overview

No suspicious patterns detected.

Findings (0)

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.

NoteHigh Confidence

ASI02: Tool Misuse and Exploitation

What this means

Running these SQL examples on a live database could change indexes or database-wide settings and affect availability or performance.

Why it was flagged

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.

Skill content

CREATE INDEX CONCURRENTLY idx_orders_user_date_total ... ALTER SYSTEM SET max_connections = 200;

Recommendation

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.

NoteHigh Confidence

ASI02: Tool Misuse and Exploitation

What this means

Copying and running the shell snippet could persistently change host CPU, memory, or network behavior and may require root privileges.

Why it was flagged

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.

Skill content

for cpu in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do
    echo performance > $cpu
done
...
cat >> /etc/sysctl.conf << EOF

Recommendation

Run system tuning commands only on systems you control, after backing up configuration and validating the settings in a safe environment.