性能 Profiler
- 作者仓库星标 1
- 作者仓库 claude-skills
Performance Profiler
Overview
Identify hot paths, bottlenecks, and likely performance wins from profiles, traces, benchmarks, and code hotspots.
Core Workflow
- Gather the smallest high-signal evidence set: failing outputs, logs, configs, recent changes, and relevant runtime context.
- Inspect the implementation and surrounding setup to isolate the narrowest plausible failure surface.
- Rank likely causes, rule out weak explanations, and identify the most actionable next fix or experiment.
- Validate the explanation with the smallest reliable check the repo or environment supports.
Deliver
- A concise diagnosis with the most likely root cause or bounded uncertainty.
- The highest-signal evidence and suspect files, configs, or systems involved.
- The smallest safe fix path or next experiment to run.
Guardrails
- Do not claim a root cause without evidence that explains the observed behavior.
- Separate symptoms from likely causes and call out uncertainty explicitly.
- Prefer the smallest reproducible scope before escalating to broad changes.
- Prefer repository evidence, command output, and nearby tests over vague intuition.
- 流狐分类
- 工程开发
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @00PrabalK00 · 未声明 license
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。Identify hot paths, bottlenecks, and likely performance wins from profiles, traces, benchmarks, and code hotspots.
Gather the smallest high-signal evidence set: failing outputs, logs, configs, recent changes, and relevant runtime context. Inspect the implementation and surrounding setup to isolate the narrowest plausible failure surface.
A concise diagnosis with the most likely root cause or bounded uncertainty. The highest-signal evidence and suspect files, configs, or systems involved. The smallest safe fix path or next experiment to run.
Do not claim a root cause without evidence that explains the observed behavior. Separate symptoms from likely causes and call out uncertainty explicitly. Prefer the smallest reproducible scope before escalating to broad changes.
# Performance Profiler
## Overview
Identify hot paths, bottlenecks, and likely performance wins from profiles, traces, benchmarks, and code hotspots.
## Core Workflow
1. Gather the smallest high-signal evidence set: failing outputs, logs, configs, recent changes, and relevant runtime context.
2. Inspect the implementation and surrounding setup to isolate the narrowest plausible failure surface.
3. Rank likely causes, rule out weak explanations, and identify the most actionable next fix or experiment.
4. Validate the explanation with the smallest reliable check the repo or environment supports.
## Deliver
- A concise diagnosis with the most likely root cause or bounded uncertainty.
- The highest-signal evidence and suspect files, configs, or systems involved.
- The smallest safe fix path or next experiment to run.
## Guardrails
- Do not claim a root cause without evidence that explains the observed behavior.
- Separate symptoms from likely causes and call out uncertainty explicitly.
- Prefer the smallest reproducible scope before escalating to broad changes.
- Prefer repository evidence, command output, and nearby tests over vague intuition.作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> Overview → Core Workflow → Deliver → Guardrails
要点 -> Identify hot paths, bottlenecks, and likely performance wins from profiles, traces, benchmarks, and code hotspots. · 1. Gather the smallest high-signal evidence set: failing outputs, logs, configs, recent changes, and relevant runtime context. · - A concise diagnosis with the most likely root cause or bounded uncertainty. · - Do not claim a root cause without evidence that explains the observed behavior.
文件/命令 -> 原文未列出明确文件或命令
内容 SHA-256 -> 30d53465ec06
方法与流程
适用与边界
原文中的明确线索