agentleFS
Sign inStart free
real-link-techreal-link-tech/reallink-skills/skills/vt-json-html/SKILL.md

vt-json-html

Skill4 starsChanged 3 months agoMITView on GitHub

Read Unreal Engine virtual texture NDJSON reports with pool_meta and per-frame sample rows, then generate standalone HTML per-pool curve charts where green shows pool size and yellow shows visible usage matching the in-game VisiblePool HUD.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Use this skill when the user asks to read VT/virtual texture JSON or NDJSON reports like vt_report_*.ndjson and turn them into HTML curve …

    line 8
  2. Distinctive:

    If the script is run from outside the skill folder, use the absolute script path:

    line 24
  3. Very specific:

    Default chart lines are pool_meta.capacityMB for pool size and vp converted to MB for visible usage.

    line 47
  4. Very specific:

    Use --needed-metric apr when you intentionally want allocated pages instead of the in-game visible residency number.

    line 48
  5. Very specific:

    Read references/schema.md only when field meaning or parsing details are needed.

    line 50

≈ “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

VT JSON HTML

Use this skill when the user asks to read VT/virtual texture JSON or NDJSON reports like vt_report_*.ndjson and turn them into HTML curve charts.

The default output is one chart per pool:

  • Green line: pool size in MB, from pool_meta.capacityMB.
  • Yellow line: visible usage in MB, default metric vp * pool_meta.tileSizeBytes / 1024 / 1024, matching the in-game VisiblePool HUD.

Workflow

  1. Locate the input report. Prefer a user-provided path; otherwise search for vt_report_*.ndjson.
  2. Generate the chart with the bundled script:
python .\scripts\vt_json_to_html.py "path\to\vt_report.ndjson"
  1. If the script is run from outside the skill folder, use the absolute script path:
python "D:\UnrealEngine\.codex\skills\vt-json-html\scripts\vt_json_to_html.py" "path\to\vt_report.ndjson"
  1. Give the user the generated .html path. The HTML is self-contained and can be opened directly in a browser.

Useful Options

python .\scripts\vt_json_to_html.py "report.ndjson" --output "report.html"
python .\scripts\vt_json_to_html.py "report.ndjson" --needed-metric vp
python .\scripts\vt_json_to_html.py "report.ndjson" --needed-metric apr
python .\scripts\vt_json_to_html.py "report.ndjson" --title "B02 VT Pool Usage"

Data Notes

  • Input is newline-delimited JSON, one object per line.
  • {"type":"pool_meta", ...} rows describe pools.
  • {"t":"s", ...} rows are samples. id maps to pool_meta.poolId.
  • The x-axis uses elapsed seconds e when available, falling back to frame f.
  • Default chart lines are pool_meta.capacityMB for pool size and vp converted to MB for visible usage.
  • Use --needed-metric apr when you intentionally want allocated pages instead of the in-game visible residency number.

Read references/schema.md only when field meaning or parsing details are needed.

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