Agent skill

Optimizing Performance

by CloudAI-X in CloudAI-X/claude-workflow-v2

Analyzes and optimizes application performance across frontend, backend, and database layers.

MITAuto-check passedFrontend & Design

Install Optimizing Performance

skills CLI
$ npx skills add CloudAI-X/claude-workflow-v2 --skill optimizing-performance -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install CloudAI-X/claude-workflow-v2 optimizing-performance --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/optimizing-performance .claude/skills/optimizing-performance && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
optimizing-performance
GitHub stars
1.4k
Used in
1 other repo
Token cost
~1.5k tokens
SKILL.md length
186 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Analyzes and optimizes application performance across frontend, backend, and database layers.

  • Works in 4 steps: Measure Baseline → Identify Bottlenecks → Apply Optimizations → …
  • Diagnosing slowness
  • SKILL.md covers Performance Optimization…, Step 1: Measure Baseline, Step 2: Identify Bottlenecks and Step 3: Apply Optimizations, plus 3 more sections
  • Calls node, python and lighthouse

What it does

Optimizing Performance is an agent skill from CloudAI-X/claude-workflow-v2. Analyzes and optimizes application performance across frontend, backend, and database layers. Use when diagnosing slowness, improving load times, optimizing queries, reducing bundle size, or when asked about performance issues.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Web performance and Performance optimization. The repository describes itself as: Universal Claude Code workflow plugin with agents, skills, hooks, and commands. The licence is MIT.

When your agent uses it

  • Diagnosing slowness
  • Improving load times
  • Optimizing queries
  • Reducing bundle size

Example prompts

  • “Use the optimizing-performance skill to analyz and optimizes application performance across frontend, backend, and database layers”
  • “/optimizing-performance”

Requirements

  • Python 3
  • Node.js

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Measure Baseline
  2. Identify Bottlenecks
  3. Apply Optimizations
  4. Measure Again

What it can do on your machine

Read from SKILL.md and the folder at commit 3b5a89e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node
    • python
    • lighthouse

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Optimizing Performance loads about 1.5k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 186 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from CloudAI-X/claude-workflow-v2 at commit 3b5a89e, republished under its MIT licence (© CloudAI-X). 186 words, ~1,456 tokens.

Download SKILL.mdSave it as .claude/skills/optimizing-performance/SKILL.md (or your agent's skills folder).
name
optimizing-performance
description
Analyzes and optimizes application performance across frontend, backend, and database layers. Use when diagnosing slowness, improving load times, optimizing queries, reducing bundle size, or when asked about performance issues.

Optimizing Performance

When to Load
  • Trigger: Diagnosing slowness, profiling, caching strategies, reducing load times, bundle size optimization
  • Skip: Correctness-focused work where performance is not a concern

Performance Optimization Workflow

Copy this checklist and track progress:

Performance Optimization Progress:
- [ ] Step 1: Measure baseline performance
- [ ] Step 2: Identify bottlenecks
- [ ] Step 3: Apply targeted optimizations
- [ ] Step 4: Measure again and compare
- [ ] Step 5: Repeat if targets not met

Critical Rule: Never optimize without data. Always profile before and after changes.

Step 1: Measure Baseline

Profiling Commands
bash
# Node.js profiling
node --prof app.js
node --prof-process isolate*.log > profile.txt

# Python profiling
python -m cProfile -o profile.stats app.py
python -m pstats profile.stats

# Web performance
lighthouse https://example.com --output=json

Step 2: Identify Bottlenecks

Common Bottleneck Categories
CategorySymptomsTools
CPUHigh CPU usage, slow computationProfiler, flame graphs
MemoryHigh RAM, GC pauses, OOMHeap snapshots, memory profiler
I/OSlow disk/network, waitingstrace, network inspector
DatabaseSlow queries, lock contentionQuery analyzer, EXPLAIN

Step 3: Apply Optimizations

Frontend Optimizations

Bundle Size:

javascript
// ❌ Import entire library
import _ from "lodash";

// ✅ Import only needed functions
import debounce from "lodash/debounce";

// ✅ Use dynamic imports for code splitting
const HeavyComponent = lazy(() => import("./HeavyComponent"));

Rendering:

javascript
// ❌ Render on every parent update
function Child({ data }) {
  return <ExpensiveComponent data={data} />;
}

// ✅ Memoize when props don't change
const Child = memo(function Child({ data }) {
  return <ExpensiveComponent data={data} />;
});

// ✅ Use useMemo for expensive computations
const processed = useMemo(() => expensiveCalc(data), [data]);

Images:

html
<!-- ❌ Unoptimized -->
<img src="large-image.jpg" />

<!-- ✅ Optimized -->
<img
  src="image.webp"
  srcset="image-300.webp 300w, image-600.webp 600w"
  sizes="(max-width: 600px) 300px, 600px"
  width="600"
  height="400"
  alt="Description"
  loading="lazy"
  decoding="async"
/>
Backend Optimizations

Database Queries:

sql
-- ❌ N+1 Query Problem
SELECT * FROM users;
-- Then for each user:
SELECT * FROM orders WHERE user_id = ?;

-- ✅ Single query with JOIN
SELECT u.id, u.name, o.id AS order_id, o.total
FROM users u
LEFT JOIN orders o ON u.id = o.user_id;

-- ✅ Or use pagination
SELECT id, name FROM users WHERE id > :last_id ORDER BY id LIMIT 100;

Caching Strategy:

javascript
// Multi-layer caching
const getUser = async (id) => {
  // L1: In-memory cache (fastest)
  let user = memoryCache.get(`user:${id}`);
  if (user) return user;

  // L2: Redis cache (fast)
  user = await redis.get(`user:${id}`);
  if (user) {
    user = JSON.parse(user);
    memoryCache.set(`user:${id}`, user, 60);
    return user;
  }

  // L3: Database (slow)
  user = await db.users.findById(id);
  await redis.setex(`user:${id}`, 3600, JSON.stringify(user));
  memoryCache.set(`user:${id}`, user, 60);

  return user;
};

Async Processing:

javascript
// ❌ Blocking operation
app.post("/upload", async (req, res) => {
  await processVideo(req.file); // Takes 5 minutes
  res.send("Done");
});

// ✅ Queue for background processing
app.post("/upload", async (req, res) => {
  const jobId = await queue.add("processVideo", { file: req.file });
  res.status(202).send({ jobId, status: "processing" });
});
Algorithm Optimizations
javascript
// ❌ O(n²) - nested loops
function findDuplicates(arr) {
  const duplicates = [];
  for (let i = 0; i < arr.length; i++) {
    for (let j = i + 1; j < arr.length; j++) {
      if (arr[i] === arr[j]) duplicates.push(arr[i]);
    }
  }
  return duplicates;
}

// ✅ O(n) - hash map
function findDuplicates(arr) {
  const seen = new Set();
  const duplicates = new Set();
  for (const item of arr) {
    if (seen.has(item)) duplicates.add(item);
    seen.add(item);
  }
  return [...duplicates];
}

Step 4: Measure Again

After applying optimizations, re-run profiling and compare:

Comparison Checklist:
- [ ] Run same profiling tools as baseline
- [ ] Compare metrics before vs after
- [ ] Verify no regressions in other areas
- [ ] Document improvement percentages

Performance Targets

Web Vitals
MetricGoodNeeds WorkPoor
LCP< 2.5s2.5-4s> 4s
INP< 200ms200-500ms> 500ms
CLS< 0.10.1-0.25> 0.25
TTFB< 800ms800ms-1.8s> 1.8s
API Performance
MetricTarget
P50 Latency< 100ms
P95 Latency< 500ms
P99 Latency< 1s
Error Rate< 0.1%

Validation

After optimization, validate results:

Performance Validation:
- [ ] Metrics improved from baseline
- [ ] No functionality regressions
- [ ] No new errors introduced
- [ ] Changes are sustainable (not one-time fixes)
- [ ] Performance gains documented

If targets not met, return to Step 2 and identify remaining bottlenecks.

© CloudAI-X, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/optimizing-performance of CloudAI-X/claude-workflow-v2.

Open the folder on GitHubat commit 3b5a89e

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in CloudAI-X/claude-workflow-v2, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Optimizing Performance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Optimizing Performance compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Optimizing Performance this skillCloudAI-X/claude-workflow-v21.4k1 repos~1.5kAutomated safety check: PassMIT
Performancemidudev/100cosas.dev1146 repos~2.3kAutomated safety check: PassMIT
Web Performancemozilla/firefox-devtools-mcp468—~1.2kAutomated safety check: PassCustom licence
Performance Optimizationsanity-io/sanity6.4k7 repos~3.1kAutomated safety check: PassMIT
Optimize Loadtextura-agency/next16-claude-starter132—~4.6kAutomated safety check: NotesUnlicense
Performance ProfilingxenitV1/Antigravity-Workflows1307 repos~772Automated safety check: NotesMIT

Similar skills

  • Performance

    midudev/100cosas.dev

    Optimize web performance for faster loading and better user experience.

    114 GitHub starsUsed in 6 repos~2.3k tokens
    Frontend & DesignAuto-check passed
  • Web Performance

    mozilla/firefox-devtools-mcp

    Find and fix why a website is slow by capturing and analyzing a Firefox performance profile, or by analyzing a profile the user already has (a saved file or a profiler.firefox.com share link).

    468 GitHub stars~1.2k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Performance Optimization

    sanity-io/sanity

    Official

    Optimizes application performance. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 7 repos~3.1k tokens
    Frontend & DesignAuto-check passed
  • Optimize Load

    textura-agency/next16-claude-starter

    Get a page into Lighthouse's green zone on desktop and mobile, for people AND for the robot form crawlers get — build it, audit all four categories (Performance, Accessibility, Best Practices, SEO)…

    132 GitHub stars~4.6k tokensUpdated today
    Frontend & DesignAuto-check: notes
  • Performance Profiling

    xenitV1/Antigravity-Workflows

    Performance profiling principles. An agent skill from xenitV1/Antigravity-Workflows.

    130 GitHub starsUsed in 7 repos~772 tokens
    Frontend & DesignAuto-check: notes
  • React performance optimization guidelines from Vercel Engineering (vercel-labs/agent-skills).

    1.3k GitHub stars~2k tokensUpdated today
    Frontend & DesignAuto-check passed

More from CloudAI-X/claude-workflow-v2

All 13 skills in this repo
  • Analyzing Projects

    CloudAI-X/claude-workflow-v2

    Analyzes codebases to understand structure, tech stack, patterns, and conventions.

    1.4k GitHub starsUsed in 2 repos~937 tokens
    Auto-check passed
  • Designing APIs

    CloudAI-X/claude-workflow-v2

    Designs REST and GraphQL APIs including endpoints, error handling, versioning, and documentation.

    1.4k GitHub starsUsed in 2 repos~1.2k tokens
    Auto-check passed
  • Designing Architecture

    CloudAI-X/claude-workflow-v2

    Designs software architecture and selects appropriate patterns for projects.

    1.4k GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • Designing Tests

    CloudAI-X/claude-workflow-v2

    Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.

    1.4k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Managing Git

    CloudAI-X/claude-workflow-v2

    Manages Git workflows including branching, commits, and pull requests.

    1.4k GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed
  • Convex Backend

    CloudAI-X/claude-workflow-v2

    Convex backend development guidelines. An agent skill from CloudAI-X/claude-workflow-v2.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

Questions about Optimizing Performance

What does Optimizing Performance do?

Analyzes and optimizes application performance across frontend, backend, and database layers. Optimizing Performance is an agent skill from CloudAI-X/claude-workflow-v2. Analyzes and optimizes application performance across frontend, backend, and database layers.

When should I use Optimizing Performance?

Optimizing Performance fits situations like: diagnosing slowness; improving load times; optimizing queries; reducing bundle size.

How do I install Optimizing Performance in Claude Code?

Run `npx skills add CloudAI-X/claude-workflow-v2 --skill optimizing-performance -a claude-code`. Or copy the skill folder (skills/optimizing-performance in CloudAI-X/claude-workflow-v2) into .claude/skills/optimizing-performance in your project. Claude Code loads it when a task matches its description.

How do I install Optimizing Performance in Codex?

Run `npx skills add CloudAI-X/claude-workflow-v2 --skill optimizing-performance -a codex`. Or copy the skill folder (skills/optimizing-performance in CloudAI-X/claude-workflow-v2) into .agents/skills/optimizing-performance in your project. Codex loads it when a task matches its description.

Can I use Optimizing Performance in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CloudAI-X/claude-workflow-v2 --skill optimizing-performance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/optimizing-performance, .gemini/skills/optimizing-performance, .github/skills/optimizing-performance and .opencode/skills/optimizing-performance in your project.

What does Optimizing Performance need to run?

Going by SKILL.md and its folder, Optimizing Performance needs the command-line tools its instructions call (node, python and lighthouse). Our summary lists: Python 3; Node.js.

Does Optimizing Performance access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Optimizing Performance safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Optimizing Performance use?

Optimizing Performance is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Optimizing Performance use?

About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Optimizing Performance?

Skills that share tags, products or a category with Optimizing Performance: Performance (midudev/100cosas.dev, 114 stars), Web Performance (mozilla/firefox-devtools-mcp, 468 stars), Performance Optimization (sanity-io/sanity, 6.4k stars) and Optimize Load (textura-agency/next16-claude-starter, 132 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Optimizing Performance?

CloudAI-X (a GitHub user) maintains it in CloudAI-X/claude-workflow-v2, which has 1,418 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 6, 2026.

Source: CloudAI-X/claude-workflow-v2 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.