Dev Loop Performance Profiler

Use when the user asks to profile slow code, find a CPU or memory bottleneck, read a flame graph, use pprof, py-spy, perf or Chrome DevTools profiler, or chase a memory leak or high latency. Produces a measure-first profiling plan and targeted optimizations. Not for functional bugs (use dev-loop-debugging-strategy) or load tests (use quality-load-testing).

45 stars 6 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill dev-loop-performance-profiler
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/dev-loop/performance-profiler ~/.claude/skills/dev-loop-performance-profiler

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Performance Profiler

## Purpose
Identify, analyze, and resolve performance bottlenecks in applications — CPU profiling, memory profiling, I/O analysis, database query optimization, and frontend rendering performance — using systematic measurement and optimization.

## Agent Protocol

### Trigger
Exact user phrases: "performance profiling", "profiling", "slow application", "performance bottleneck", "CPU profiler", "memory leak", "heap dump", "database slow query", "performance optimization", "flame graph", "page speed", "LCP", "INP", "CLS".

### Input Context
- Performance symptom (slow response, high CPU, memory growth, network latency, UI jank)
- Application type (web frontend, API server, database, desktop, mobile)
- Environment (local development, staging, production, specific user)
- Scale (single user, concurrent, burst traffic, sustained load)
- Recent changes (deployment, dependency update, config change, migration)
- Available tools (built-in profiler, APM, browser DevTools, database tools)

### Output Artifact
Performance analysis report with measured metrics, bottleneck identification, and optimized code.

### Response Format
```
Symptom + baseline: {metric, value, environment}
Tool: {profiler/APM/DevTools}
Hot spots: {function/query/resource -> % time or bytes}
Root cause: {explanation}
Fix: {change}
Result: {before -> after, same workload}
```

### Completion Criteria
- [ ] Baseline performance metrics established
- [ ] Profiling tool selected and configured
Read the full skill on GitHub

Details

Skill name
dev-loop-performance-profiler
Path
skills/dev-loop/performance-profiler/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Dev Loop Performance Profiler skill do?

Use when the user asks to profile slow code, find a CPU or memory bottleneck, read a flame graph, use pprof, py-spy, perf or Chrome DevTools profiler, or chase a memory leak or high latency. Produces a measure-first profiling plan and targeted optimizations. Not for functional bugs (use dev-loop-debugging-strategy) or load tests (use quality-load-testing).

How do I install the Dev Loop Performance Profiler skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill dev-loop-performance-profiler. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Dev Loop Performance Profiler popular?

It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Fix Issue

45

j4flmao/agent-skills

Fix a GitHub issue by number. Read the issue, implement the fix, write tests, commit.

Testing & QA

Data Testing

45

j4flmao/agent-skills

Use when the user asks about dbt unit tests, data regression testing, data-diff / Datafold, Soda or GX tests in CI, or testing data pipelines before deploy. Produces a layered data test strategy with unit, contract and diff tests. Not for runtime quality monitors (use data-data-observability) or CI wiring (use data-pipeline-cicd).

Testing & QA

Frontend Testing

45

j4flmao/agent-skills

Use when the user asks about frontend testing, component tests with Testing Library, Vitest or Jest, userEvent, mocking APIs with MSW, Playwright or Cypress for critical journeys, and what to test in the UI. Produces a test strategy and component/E2E tests. Not for Storybook stories (use frontend-storybook) or cross-team E2E suites (use quality-e2e-testing).

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.