Analyze Performance Traces

Analyze Performance Traces is a Frontend skill for Claude Code, published by tutti-os in tutti.

3.3K stars328 forkson tutti-os/tuttiAdded 2026/08/17+1% in starsRepository updated 2026/08/17

agent-collaborationagent-orchestrationagent-workspaceagentic-aiagentic-workflowai-agentsai-toolsai-workspaceclaude-codecodexcoding-agentdesktop-appdeveloper-toolshermes-agentlocal-firstmacos-appmcpmulti-agentshared-contextvibe-coding

Install in seconds

Install Analyze Performance Traces

Copy Analyze Performance Traces into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/tutti-os/tutti/tree/main/.codex/skills/analyze-performance-traces ~/.claude/skills/analyze-performance-traces

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/tutti-os/tutti.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: .codex/skills/analyze-performance-traces/SKILL.md in tutti-os/tutti
Installs to: ~/.claude/skills/analyze-performance-traces
Collection: One of 8 skills cataloged from this repository
Category: Frontend — 567 skills

What Analyze Performance Traces does

Analyze Performance Traces audits Chrome, Chromium, Electron, React DevTools, or Perfetto-compatible JSON traces to prove trigger-to-render chains, isolate source-level bottlenecks, classify forced layout and render fanout, and apply safe fixes. Use it for trace files, reported profiling durations, dropped frames, long tasks, jank, render storms, layout thrashing, or interaction latency.

Analyze Performance Traces is cataloged under Frontend on DirSkills. Analyze Performance Traces comes from a repository tagged agent-collaboration, agent-orchestration, agent-workspace, agentic-ai and agentic-workflow.

Documentation

README

Excerpt

Analyze Performance Traces

End with an evidence chain from trigger to exact source. Fix the earliest proven cause. Never turn an API name or an inclusive duration into a causal claim without checking execution context.

Choose the evidence mode

State which mode applies before making findings:

Trace-backed: a trace is supplied or discoverable. Durations, processes, threads, and event ordering may be reported from it.
Reported-finding audit: the user supplies durations or a chain but not the artifact. Treat those details as leads. Confirm current source paths and trigger conditions; label the durations, thread, and invalidation scope unverified.
Source-only: no trace-derived lead exists. Report hypotheses, not measured bottlenecks.

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Analyze Performance Traces

What else does tutti-os publish alongside Analyze Performance Traces?
Analyze Performance Traces is one of 8 skills that DirSkills catalogs from tutti-os/tutti, the repository it ships in. Its siblings there include Tutti Agent Session Replay, Tutti Agent Workspace App and Tutti App Release. Each one is a separate skill with its own page in this directory, installs the same way Analyze Performance Traces does, and is maintained by tutti-os in that same repository. The rest of the collection is listed on the tutti-os/tutti page.
How does Analyze Performance Traces compare to other Frontend skills?
Analyze Performance Traces ranks #183 by stars among the 567 Frontend skills in this catalog. The most-starred ones next to it are Angular Developer, Android Clean Architecture and Accessibility. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Analyze Performance Traces against them. Open each page to compare what they document and how they install.