agentleFS
Sign inStart free
LeonardoEnnesLeonardoEnnes/ai-engineering-toolkit/.agents/skills/performance-audit/SKILL.md

performance-audit

Skill0 starsChanged 10 days agoApache-2.0View on GitHub

Identifies, profiles, and resolves deep performance bottlenecks across frontend, backend, and database layers.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use incident-response, threat-model and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    incident-response

    Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.

    Also in 4 projects that use this

  • OpenAISkill

    threat-model

    Use when Codex is already in the threat-modeling phase of a security scan, the user explicitly invokes $threat-model, or the user explicitly asks to create, update, or persist a repository threat model. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

    Also in 3 projects that use this

  • SentrySkill

    write-tests

    Write tests following project conventions. Use when adding new tests or modifying existing ones.

    Also in 3 projects that use this

  • MicrosoftSkill

    api-design

    Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.

    Also in 3 projects that use this

  • SentrySkill

    security-review

    Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    release-notes

    Author and update release notes for Azure App Configuration libraries and providers. USE FOR: write release notes, add release note entry, update release notes, draft release notes, new version release notes, format release notes. DO NOT USE FOR: generating changelogs from git history, writing internal engineering notes.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When asked to perform a performance audit, you MUST analyze the code for high-impact bottlenecks and provide concrete, production-ready …

    line 9
  2. Distinctive:

    Connection Pooling: Check transaction boundaries and connection leak potentials in connection pools (HikariCP / pg pool).

    line 24

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Performance Auditor (Deep Profiler)

<instructions> When asked to perform a performance audit, you MUST analyze the code for high-impact bottlenecks and provide concrete, production-ready optimized solutions:
  1. Frontend (React / Vite / Next.js):
    • Re-renders & State: Detect unnecessary component re-renders caused by unstable object references or monolithic state placement. Enforce React.memo, useMemo, useCallback, or state lifting/lowering strategies.
    • Bundle & Loading: Spot heavy libraries imported synchronously. Enforce code-splitting, dynamic imports (React.lazy), and bundle analyzers.
    • Memory Leaks: Identify uncleaned event listeners, uncleared setInterval/setTimeout, or subscriptions left open in useEffect cleanup hooks.
  2. Backend (Spring Boot / Node.js / Python FastAPI):
    • Concurrency & Blocking: Flag blocking I/O operations running on main threads or event loops. Enforce asynchronous patterns, non-blocking drivers, or thread pool tuning.
    • Data Processing: Identify inefficient O(n²) loops, heavy collection filtering, or missing memory pagination for large datasets (enforce Cursor/Keyset pagination over Offset pagination).
    • Parallelization: Detect independent sequential asynchronous calls that should be executed concurrently (e.g., Promise.all or parallel completable futures).
  3. Database & ORM Layer:
    • N+1 Query Resolution: Detect loops triggering individual queries. Enforce JOIN FETCH, @EntityGraph, DTO projections, or DataLoader patterns.
    • Indexing & Queries: Flag unindexed foreign keys, full table scans on high-traffic tables, and inefficient wildcard searches (LIKE '%term%').
    • Connection Pooling: Check transaction boundaries and connection leak potentials in connection pools (HikariCP / pg pool).

Mandatory Output Format:

  • Bottleneck Location: (File, layer, and snippet)
  • Root Cause Analysis: (Why this degrades under load or concurrency)
  • Optimized Code: (Production-ready refactored snippet)
</instructions>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free