Review code for efficiency and performance. Triggered by "/optimize" when user wants to identify bottlenecks or improve performance.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./mod/slash/lib/preset/optimize/SKILL.mdUse when:
/optimizeDo NOT use when:
/simplify)/security-review)If user provides runtime data or if profiling is straightforward:
# Examples by platform/language
/usr/bin/time -v ./script.sh # Linux
python -m cProfile -s cumtime script.py
node --prof script.jsIf no runtime data, skip to Step 2 with static analysis.
Analyze for:
Use the output format below.
## Performance Review
### Bottlenecks Found
#### 🔴 [Severity] [Category]
**File**: `path:line`
**Issue**: [Description]
**Impact**: [Quantify if possible]
**Fix**: [Recommendation]
#### 🟠 ...
### Recommendations (Priority Order)
1. [Highest impact fix]
2. [Next fix]x-cmd/x-cmd
812ace9
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.