skills.rest
AgentSystemLabs
AgentSystemLabsOFFICIAL
Explore all skills by this author →
GitHub

audit-perf

Audit route entry points for static performance bottleneck patterns.

121|2|Updated Apr 24, 2026
Search Tags:#bundle analysis#performance audit#database indexing#n+1 queries#static code scanning#web latency
One-click install
npx skills add https://github.com/AgentSystemLabs/core --skill audit-perf-agentsystemlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-perf
Source: https://github.com/AgentSystemLabs/core/tree/main/plugins/agentsystem-core/skills/audit-perf
Command: npx skills add https://github.com/AgentSystemLabs/core --skill audit-perf-agentsystemlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you identify likely performance bottlenecks in your route/page/module code by scanning for common, high-impact patterns (like N+1 queries, missing indexes, and unbounded fetches) and reporting them with concrete, evidence-backed fixes.

Core Features & Use Cases

  • Static performance audit: Reviews a named entry point and reads imports two layers deep to stay focused on the real hot path.
  • Pattern catalog–driven findings: Detects specific signatures (e.g., N+1 query loops, missing indexes on filtered/joined columns, SELECT * usage, sequential awaits, server-only imports leaking to client bundles).
  • Actionable, ranked reports: Produces findings grouped by impact (high/medium/low), each with an evidence line (file:line) and a specific code-level remediation.
  • Audit-only safety boundary: Never applies fixes automatically; it reports only, so you retain control of tradeoffs and reviewability.

Quick Start

Ask your agent to audit a slow entry point by saying: "audit perf for ./src/app/dashboard/page.tsx and report the top high-impact issues with file:line evidence and concrete fixes."

Frequently Asked Questions about audit-perf

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find performance bottlenecks in my application code without running a profiler?▼

Static performance audits identify bottleneck patterns like N+1 queries and missing indexes by scanning route entry points and their immediate dependencies, producing ranked findings with file:line evidence without runtime profiling.

What is the best way to detect N+1 queries and missing database indexes in my route handlers?▼

Static code scanning detects N+1 query loops and missing indexes on filtered or joined columns by analyzing data-fetch paths within your named endpoints, ranking each issue by impact with concrete remediation steps.

Can I use static analysis to find server-only imports leaking into my client bundle?▼

Yes, static performance audits detect server-only imports leaking to client bundles by reviewing the import graph two layers deep from your specified module entry points to identify web latency issues.

Does a static performance audit automatically fix unoptimized database queries and sequential awaits?▼

No, static performance audits never apply fixes automatically; they only report findings grouped by impact with evidence lines and specific code-level remediation steps so you retain control over tradeoffs.

What are the limitations of static code scanning for web latency compared to runtime profiling?▼

Static performance audits avoid runtime profiling claims and do not scan the entire repository; they target user-named endpoints and immediate dependencies to find pattern signatures without measuring actual execution time.

How do I audit a slow page entry point for high-impact performance issues?▼

Request a static performance audit for your specific file path, and the scanner will review imports two layers deep, detect high-impact patterns like sequential awaits and unbounded fetches, and report ranked fixes.

Related Skills

Explore More Software Engineering Skills→
maestria-comaestria-co

code-identifier

Locate code implementations and entry points across a codebase.

Official
Intermediate
netprtonynetprtony

vercel-react-best-practices

Apply React and Next.js performance best practices to code reviews and refactoring.

Community
Advanced
keshavraj936keshavraj936

performance-profiling

Run Lighthouse audits and analyze Core Web Vitals for web performance.

Community
Intermediate
Postpartum-genushyacinthus29Postpartum-genushyacinthus29
8

dotnet-roslynator

Configure Roslynator analyzers and CLI for C# static analysis.

Community
Advanced