菜单
Use when the user wants to view, inspect, or share Perfetto/Chrome trace files -- triggered by words like "trace", "perf", "perfetto", "profiling", "trace viewer", or when dealing with trace JSON files from training runs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Enforces explicit user approval before implementing any plan. Use when presenting a plan, receiving plan feedback, or about to delegate implementation.
CharlieBot repo structure, architecture, and development conventions. Use when modifying charlie-bot code.
How to write effective improve loop goal prompts — for the master CC agent that writes the --goal-file content.
methodology for iterative improve loop workers.
CharlieBot skill directory layout, sync rules, and CLI tool mappings. Use when creating, installing, or syncing skills across Claude Code, Codex, Gemini, OpenCode, and Antigravity.
This skill should be used when the user asks to read, create, or edit Feishu/Lark documents, search docs in their Feishu workspace, or fetch content from a Feishu wiki or docx URL.
| name | perfetto |
| description | Use when the user wants to view, inspect, or share Perfetto/Chrome trace files -- triggered by words like "trace", "perf", "perfetto", "profiling", "trace viewer", or when dealing with trace JSON files from training runs. |
| version | 1.0.0 |
Generate links to the CharlieBot built-in Perfetto trace viewer, which can merge cross-rank traces of the same time window into a single view.
All URLs use <base_url> where <base_url> is the CharlieBot URL resolved from HOST MEMORY (look for the CharlieBot URL entry).
<base_url>/perfetto?dir=<absolute-path>
Auto-discovers all *.json trace files in the directory, merges them client-side (labeling by rank), and loads into an embedded Perfetto UI.
Use ?dir= only for cross-rank merging — i.e. when every file in the directory is a different rank's trace of the same time window/step. The merger labels tracks by rank and assumes one trace per rank; mixing multiple time windows of the same rank into one ?dir= link will produce a confusing/overlapping view.
If a directory contains multiple time windows (or multiple steps) for the same rank(s), generate separate links — one per time window — each pointing at just that window's files. Use ?pattern= to scope a ?dir= link to a single window, or list the per-rank files explicitly with repeated ?trace= params.
Optional params:
&pattern=<glob> -- file pattern to match (default: *.json); use this to isolate one time window in a mixed directory&title=<text> -- custom page title<base_url>/perfetto?trace=/files/<path1>&trace=/files/<path2>
Pass one or more trace= params with /files/-prefixed absolute paths.
<base_url>/perfetto?trace=/files/<absolute-path>
| Scenario | URL |
|---|---|
| Cross-rank merge for one step | <base_url>/perfetto?dir=/path/to/traces/step100 |
Scope ?dir= to one time window | <base_url>/perfetto?dir=/path/to/traces&pattern=trace_rank*_step100.json |
| Only rank 0 | <base_url>/perfetto?trace=/files/path/to/traces/trace_rank000_step100.json |
| Two time windows of rank 0 | generate two separate links, one per window — do not combine in a single ?dir= |
ls or Glob)?dir= is for cross-rank merging only. Multiple time-window traces of the same rank must be linked separately (one URL per window), not bundled in one ?dir=?dir=, confirm the directory holds at most one trace per rank for a single time window; otherwise narrow it with &pattern= or switch to explicit ?trace= params[descriptive text](url)