Menú
Managing and querying Perfetto traces using the trace_processor MCP server.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Documentation for conditional testing in V8 using gm.py.
Guides the initial analysis and impact assessment of a V8 security report, strictly excluding implementation or fixing.
Executes and interprets V8 tests. Use when running unittests, cctest, or mjsunit, or when debugging test failures. Do not use for building.
Manages git task isolation and environment setup in V8. Use at the start of any new task or bug fix. Do not use for general C++ editing.
Workflow for issue-based debugging in V8. Use when tasked with debugging a specific issue, usually associated with a Buganizer ID or a specific reproduction script. Do not use for performance regressions.
Workflow for general debugging tasks without the overhead of issue tracking. Use when investigating crashes, hangs, or unexpected behavior where no specific issue ID is provided. Do not use when issue ID is provided.
| name | trace_processor |
| description | Managing and querying Perfetto traces using the trace_processor MCP server. |
The trace_processor extension launches a long-running FastMCP server wrapping
Perfetto's trace processor capabilities, allowing seamless interaction with
trace files (.pftrace, .perfetto-trace, .pb).
For comprehensive guidance on querying traces, utilizing standard library
modules, and schema structures, refer directly to the native Perfetto AI skills
inside third_party/perfetto/ai/skills:
slice,
thread, process, sched_slice, and track.slices.with_context by starting queries with INCLUDE PERFETTO MODULE.