agentleFS
Sign inStart free
real-link-techreal-link-tech/reallink-skills/skills/quick-analyze-gpuprofile/SKILL.md

quick-analyze-gpuprofile

Skill4 starsChanged 3 months agoMITView on GitHub

Use when the user has Unreal Engine ProfileGPU or profViz files and wants a quick standalone analysis, searchable HTML tree view, or JSON/CSV export without opening UE.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the bundled profviz_tool.exe to parse Unreal *.profViz files into:

    line 12
  2. Distinctive:

    Use this skill when the user mentions:

    line 21
  3. Distinctive:

    Do NOT use for:

    line 29
  4. Distinctive:

    When using this skill, report back:

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Quick Analyze GPUProfile

Overview

Use the bundled profviz_tool.exe to parse Unreal *.profViz files into:

  • a searchable tree-based HTML report
  • a full JSON hierarchy
  • a flat CSV export

This skill is for quick local inspection when opening Unreal Editor is unnecessary or too heavy.

Trigger

Use this skill when the user mentions:

  • profilegpu
  • profViz
  • *.profViz
  • "quick analyze GPU profile"
  • "不用开 UE 看 profilegpu"
  • "导出 GPU profile 的 html/json/csv"

Do NOT use for:

  • Razor GPU / .rzrgpu
  • PIX / .wpix
  • RenderDoc / .rdc
  • Requests that need engine instrumentation changes rather than file analysis

Bundled Tool

Bundled executable:

C:\Users\L\.claude\skills\quick-analyze-gpuprofile\scripts\profviz_tool.exe

Quick Workflow

Single file to explicit output directory:

& "C:\Users\L\.claude\skills\quick-analyze-gpuprofile\scripts\profviz_tool.exe" parse "X:\path\capture.profViz" --output-dir "X:\path\out"

Batch a directory:

& "C:\Users\L\.claude\skills\quick-analyze-gpuprofile\scripts\profviz_tool.exe" batch "X:\path\profileViz" --output-dir "X:\path\out"

Quick inspect with default sibling output directory:

& "C:\Users\L\.claude\skills\quick-analyze-gpuprofile\scripts\profviz_tool.exe" "X:\path\capture.profViz"

This writes outputs into a sibling profviz_output directory and opens the HTML report.

What to Return

When using this skill, report back:

  • the generated HTML path
  • the generated JSON/CSV paths when relevant
  • the hottest obvious events if the user asked for analysis

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free