CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cli-anything-nsight-graphics

Windows-first CLI harness for Nsight Graphics capture, GPU Trace summary, and ngfx-replay analysis

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./nsight-graphics/agent-harness/cli_anything/nsight_graphics/skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, execution-focused CLI reference: fully executable command examples for every subcommand, sensible sequencing guidance in Agent Notes, and clear routing between replay analysis and GPU Trace summarization. Weaknesses are minor — an inline version-specific caveat that belongs in a compatibility/deprecated note and no explicit output-verification checkpoint after captures.

Suggestions

Move the Nsight Graphics 2026.1.0 "Invalid file header" caveat into a labeled compatibility/deprecated section so time-sensitive version details don't clutter the main notes.

Add a validation checkpoint after capture commands (e.g. check that the output directory contains the expected .ngfx-capture/.ngfx-gputrace file before proceeding to summarize or analyze).

DimensionReasoningScore

Conciseness

The body is lean — copy-paste command examples with no filler and no explanation of concepts Claude already knows — but it embeds a time-sensitive version reference ("on Nsight Graphics 2026.1.0 they may report `Invalid file header`") outside any deprecated/old-patterns section, and a few Agent Notes (the enumeration of summary contents) could be tightened.

4 / 5

Actionability

Every section provides fully executable, copy-paste-ready commands with real flags (--exe, --pid, --wait-frames, --auto-export, --summarize) and covers the common cases for each subcommand: doctor, launch, frame capture, GPU trace, replay analysis, and C++ capture.

5 / 5

Workflow Clarity

Sequencing is explicit ("Prefer `doctor info` first to discover the available compatibility mode") with clear decision routing for input types and error-recovery notes (empty-table warnings, old-worktree reinstall), but there is no explicit post-capture verification step such as confirming output files were produced.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the body is well organized (Capabilities overview, per-command sections, Agent Notes). It falls short of a 5 because it is a ~95-line multi-command skill rather than the under-50-line single-task case, and all detail lives inline with no reference structure at all.

4 / 5

Total

17

/

20

Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and highly distinctive, clearly naming the tooling niche and three concrete capabilities. Its main weakness is the complete absence of any "when to use this" trigger guidance, which both caps completeness and leaves natural trigger phrases like "frame capture" or "GPU profiling" unused.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to capture or analyze frames with NVIDIA Nsight Graphics, run a GPU Trace, profile a graphics application, or inspect .ngfx-capture files."

Broaden natural keyword coverage with synonyms users actually say: "frame capture", "GPU profiling", "frame debugger", and file extensions (.ngfx-capture, .ngfx-gputrace).

Consider mentioning one or two more capabilities (e.g. attach to a running process, compatibility diagnostics) to close the coverage gap with the body's Capabilities list.

DimensionReasoningScore

Specificity

Names the domain and three concrete actions tied to specific tools ("Nsight Graphics capture", "GPU Trace summary", "ngfx-replay analysis"), but omits several capabilities documented in the body (attach to PID, Generate C++ Capture, compatibility diagnostics), so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

The "what" is clear (a CLI harness for capture, GPU Trace summary, and replay analysis), but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes the core natural terms a user would say for this niche ("Nsight Graphics", "GPU Trace", "capture", "ngfx-replay"), but misses common variations and synonyms such as "frame capture", "GPU profiling", "frame debugger", and file extensions like .ngfx-capture.

4 / 5

Distinctiveness Conflict Risk

"Nsight Graphics", "GPU Trace", and "ngfx-replay" identify a highly specific NVIDIA tooling niche with distinct triggers, so conflict risk with other skills is minimal.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

HKUDS/CLI-Anything

Path

nsight-graphics/agent-harness/cli_anything/nsight_graphics/skills/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.