Individual skill
performance-auditor
Looks for performance bottlenecks across frontend rendering, backend logic, database access, and network usage. Use when something is slow or before it needs to scale.
skills/development/performance-auditor/SKILL.md
Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Aug 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- ai Repository topic
- ai-agents Repository topic
- ai-coding Repository topic
- ai-skill Repository topic
- ai-skill-enhancement Repository topic
- ai-skills Repository topic
- ai-skills-analysis Repository topic
- ai-skills-fest Repository topic
- ai-skills-manager Repository topic
- data Derived category
- data-databases Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 1,306 bytesSKILL.mdcore · 2,312 bytesexamples/example.mddoc · 1,718 bytes
Read excerpt
## Purpose
Identify concrete performance bottlenecks across the stack — frontend, backend, database, network — and quantify their likely impact, rather than offering generic "make it faster" advice.
## When to Use
- Something is measurably slow and the cause isn't obvious.
- Reviewing code before it needs to handle significantly more load or data.
- The user asks for a performance review/audit specifically.
## What to Analyze
1. **Database access** — N+1 query patterns, missing indexes (see [Database Architect](../database-architect/) for schema-level depth), fetching more columns/rows than needed.
2. **Algorithmic complexity** — loops over loops on data that can grow, repeated work that could be cached or computed once.