CtrlK
BlogDocsLog inGet started
Tessl Logo

qt-qml-profiler

Use when the user is investigating QML / Qt Quick performance — both vague complaints ("the UI feels laggy", "this is slow", "frames are dropping", "the app stutters") and explicit asks to profile, find hotspots, or optimize bindings, signals, or rendering. Runs qmlprofiler on a 2D QML application, parses the .qtd trace, and analyzes hotspots against the source with frame-time, memory, and pixmap-cache summaries. Does NOT cover Qt Quick 3D.

76

Quality

96%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A well-engineered, highly actionable multi-step skill with explicit validation checkpoints, real one-level-deep references, and copy-paste-ready commands. The only weakness is mild verbosity in a few report-writing passages that teach concepts Claude largely already knows.

Suggestions

Tighten the Step 6 memory summary: the QV4::Profiling::MemoryType category explanation could be condensed to the reader-friendly glosses only, moving the internal-name mapping into the parser output rather than the SKILL.md body.

The "How to read the percentiles" block (p50/p95/vsync 16.67ms) restates concepts Claude already knows; keep only the report-specific translation rule (N = round(pct × frame_count)) and drop the general percentile primer.

The Manual fallback section's numbered checklist and the Claude Code CLI aside overlap with general guidance Claude can generate; consider trimming to the essential hand-off command and one-line reason.

DimensionReasoningScore

Conciseness

Mostly efficient and purposeful — it assumes Claude knows what a profiler is and skips basic concept primers — but the ~470-line body includes teaching passages (the QV4 MemoryType category walkthrough, the "How to read the percentiles" vsync block) that could be trimmed slightly; fits the "efficient; minor instances of over-explanation" anchor rather than the lean score-5.

4 / 5

Actionability

Provides copy-paste-ready executable commands throughout — the cmake build block, the qmlprofiler invocation, the parser invocation — plus concrete OS-detection and profile tables and explicit path-quoting rules, fully covering the common cases.

5 / 5

Workflow Clarity

Seven clearly sequenced steps each carry explicit validation/sanity checks (stop on non-zero cmake exit; trace file-size + exit-code checks; parser error-key mapping) with feedback loops (rebuild, rerun, ask user), matching the score-5 anchor including for the build/run/parse batch operations.

5 / 5

Progressive Disclosure

SKILL.md is a workflow overview that points to two real one-level-deep bundle files — qml-performance-anti-patterns.md (loaded in Step 5) and parse-qmlprofiler-trace.py (invoked in Step 4) — clearly signaled inline and in a dedicated References section, with no nested-reference chains.

5 / 5

Total

19

/

20

Passed

Description

100%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.

An excellent description: concrete actions, comprehensive natural trigger terms, explicit what/when coverage, and a sharply scoped niche with an explicit exclusion. Voice is third person ("the user"), so no person-voice penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Runs qmlprofiler on a 2D QML application, parses the .qtd trace, and analyzes hotspots against the source with frame-time, memory, and pixmap-cache summaries" — covering the full pipeline comprehensively, matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers "what" (run qmlprofiler, parse trace, analyze hotspots with summaries) and "when" via a concrete "Use when the user is investigating QML / Qt Quick performance" trigger clause listing both vague and explicit asks.

5 / 5

Trigger Term Quality

Captures both natural vague-complaint phrases users actually say ("the UI feels laggy", "frames are dropping", "the app stutters") and explicit asks (profile, find hotspots, optimize bindings/signals/rendering), plus file extensions (.qtd) and domain terms (QML, Qt Quick).

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (2D QML/Qt Quick profiling) and explicitly scopes out Qt Quick 3D ("Does NOT cover Qt Quick 3D"), minimizing overlap with other skills.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 2 missing, 2 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository
x-tools-author/x-tools
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.