qt-qml

Applies QML best practices when producing or working with QML source code. Use whenever QML code is the primary subject: writing, reviewing, fixing, refactoring, optimizing, or debugging QML files, components, or bindings. Do NOT trigger for purely conversational QML questions where no code is produced or examined (e.g. "explain how anchors work").

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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 lean, well-organized rules reference that is highly token-efficient and actionable, with a clear three-mode workflow and validation checklist. Its main weakness is progressive disclosure: a large single-file skill with no bundle files splits nothing out.

Suggestions

Split the dense rule tables (e.g. Performance and rendering, Layouts) into reference files under references/ and link to them from SKILL.md so the body stays a concise overview.

Add a few complete, copy-paste QML code snippets for the most common patterns (e.g. a Loader + required-property delegate) to lift actionability from rule statements to executable examples.

Surface a one-line '.qml' trigger and a pointer to any reference files in the description so file-extension-based invocation and deeper material are discoverable.

Dimension	Reasoning	Score
Conciseness	Dense, table-driven rules with terse detail columns and no padding; it never explains basics Claude already knows and folds Qt 5 vs Qt 6 version notes inline with justification.	5 / 5
Actionability	Concrete QML identifiers and patterns throughout (e.g. 'PropertyChanges { someId.width: 100 }', 'Loader.active: false'), but guidance is mostly rule statements rather than full copy-paste executable code blocks.	4 / 5
Workflow Clarity	Three clearly sequenced modes (writing new, existing project, reviewing) plus a pre-output checklist as a validation checkpoint; not a fragile batch/destructive process, so checkpoints are adequate with minor gaps.	4 / 5
Progressive Disclosure	No bundle files exist; all reference-style rule tables are inlined into a single ~190-line SKILL.md with good section headers, but content that could be split into separate files is not.	3 / 5
	Total	16 / 20 Passed

Description

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

A strong, third-person description that explicitly covers what the skill does, when to trigger it, and when not to. Its only minor weakness is the absence of the '.qml' file extension among the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'writing, reviewing, fixing, refactoring, optimizing, or debugging QML files, components, or bindings' — giving comprehensive coverage of the QML workflow.	5 / 5
Completeness	Explicitly answers both 'what' ('Applies QML best practices when producing or working with QML source code') and 'when' ('Use whenever QML code is the primary subject') with concrete trigger phrases, plus a negative trigger boundary.	5 / 5
Trigger Term Quality	Strong natural action verbs users would say (writing, reviewing, fixing, refactoring, optimizing, debugging) plus synonyms (files, components, bindings); minor gap is the missing '.qml' file extension.	4 / 5
Distinctiveness Conflict Risk	Clear QML niche with distinct triggers and an explicit negative boundary ('Do NOT trigger for purely conversational QML questions'), minimizing conflict with adjacent skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: x-tools-author/x-tools
Path: .github/skills/qt-qml/SKILL.md
Commit: 6214c41

Reviewed: 4 hours ago

Table of Contents

Discovery Implementation Validation

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.