Qt AI Skills
Official Qt skills: C++ and QML review, QML and CMake best practices, Qt Quick tests, docs, profiler and Figma to QML, plus an MCP server with Qt docs
- 513 ★ on the repository
- Last commit
Extended access
Why this level
- The skills run lint scripts, qmlprofiler and qmltestrunner, and the --wire-up flag can change CMake test infrastructure
- The plugin connects a hosted Qt documentation MCP server, so queries go to Qt's side
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/qt-ai-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The skills run lint scripts, qmlprofiler and qmltestrunner, and the --wire-up flag can change CMake test infrastructure
- The plugin connects a hosted Qt documentation MCP server, so queries go to Qt's side
This is third-party code. Review the repository files before installing.
What it does
Qt AI Skills is the official skill set from Qt for building and quality-checking Qt applications. It targets Claude Code, Codex CLI and GitHub Copilot, and works with other tools after manual adaptation. The authors tested the skills on models from the Claude, Gemini and GPT families. The skills come in four kinds. Review: qt-cpp-review combines deterministic linting with six parallel deep-analysis agents (memory ownership, threads, correctness, error handling, performance), and qt-qml-review adds more than 47 QML rules. Conceptual: qt-qml corrects systematic model mistakes around bindings, scoping and modules, qt-canvas2d covers Qt Canvas2D from Qt 6.12, qt-ui-design reviews UI design for Qt/QML, web and embedded targets, and qt-cmake-project sets up Qt 6 CMake projects. Process: qt-qml-docs and qt-cpp-docs write Markdown reference, qt-qml-test creates Qt Quick Test cases, and qt-figma-token-extraction and qt-figma-component-generation carry Figma tokens and components into QML singletons and controls. Tool: qt-qml-profiler runs qmlprofiler and analyzes the trace, and qt-qml-test-run builds and runs tests with a report. The set also includes qt-documentation-mcp, an MCP server for Qt documentation lookup.
Who it is for. For Qt, C++ and QML developers, embedded UI teams and QA engineers who review and write code with an agent.
Good fit when
- Before a merge you need Qt C++ code checked for memory ownership, thread safety and error handling
- QML files are growing and you need a review of bindings, loaders, delegates and performance
- A Figma design system must become design-tokens.json and QML controls mapped to Qt Quick Controls 2
- QML components need tst_*.qml tests with TestCase and SignalSpy plus a run report
- A Qt Quick app is slow and you want a qmlprofiler trace analyzed against the source
Not a fit when
- You need Qt Quick 3D: the profiler skill does not cover it
- You need runner and CMake setup for QML tests: qt-qml-test excludes it, and only qt-qml-test-run offers it with the --wire-up flag
- The agent cannot run scripts and subagents, such as Copilot without the linter: the review is less thorough and gives static guidance only
- The project does not use Qt: the skills are written for Qt, QML and Qt Quick
Example request
Review src/mainview.cpp and MainView.qml with qt-cpp-review and qt-qml-review: linters first, then the deep analysis. Collect the findings sorted by severityLimitations
The authors warn that the skills use AI and can make mistakes, so output needs double-checking. Under Qt commercial licensing you need to accept the Qt AI Services terms. SKILL.md files declare LicenseRef-Qt-Commercial OR BSD-3-Clause.
Qt Canvas2D needs Qt 6.12 or newer, and live QML preview through MCP also works on Qt 6.12 and up. In Cursor and Windsurf a skill becomes a rule, and Windsurf uses condensed variants for qt-cpp-review, qt-qml-review, qt-qml-docs and qt-qml without scripts and subagents.
How to disable. In Claude Code remove the plugin with /plugin, or delete the symlink and skill folders from ~/.claude/skills or .claude/skills. For Codex delete the folders from ~/.codex/skills, for Gemini CLI remove the extension, for Cursor delete the rules you created.
FAQ
How do I install the Qt skills in Claude Code?
Run /plugin marketplace add TheQtCompanyRnD/agent-skills and /plugin install qt-development-skills. You can also connect single skills by hand: symlink skills/qt-qml-review into ~/.claude/skills or copy it into the project's .claude/skills.
How do I use these skills with Cursor or Windsurf?
Those tools do not read skill directories. In Cursor you copy SKILL.md into .cursor/rules as RULE.md; in Windsurf you take the condensed variant from platforms/windsurf.md. Scripts and subagents do not run there, so only static guidance applies.
What does qt-qml-review check?
Deterministic linting with more than 47 QML rules plus parallel deep-analysis agents for bindings, layout, loaders, delegates, states and performance.
Does Qt have an MCP server with documentation for agents?
Yes, qt-documentation-mcp: a hosted server for Qt documentation lookup across the latest release and active LTS branches. In Claude Code it comes with the qt-development-skills plugin, and it is also listed standalone as io.qt/qt-documentation-mcp in the official MCP registry.
How do I carry a Figma design into QML?
qt-figma-token-extraction exports tokens, text styles and variables to design-tokens.json and QML singletons. qt-figma-component-generation then generates controls for Qt Quick Controls 2 and needs the tokens from the first skill.
Discussion
No questions or reviews yet.
Related
SkillsEleven skills for Claude Code and Codex: test audit, git worktree cleanup, plan pages, screen recording transcripts and 1Password sign-in
A code review skill across many languages and frameworks: architecture, performance, security, anti-patterns and common bugs
Claude Code Skills, Chinese collection
Claude Code Skills 中文精选集
A set of 21 original Claude Code skills with Chinese output: code review, README, API tests, refactoring, profiling
A Claude Code marketplace of 19 plugins and 76 skills for frontend, backend, DevOps and security, with a skill chain command
Skills from the Dart team: tests and mocks, analysis and dart fix, CLI apps, FFI, documentation and package conflict fixes for an AI agent
14 skills that find the gaps in a task before the code: interviews, plans, assumption tests and proof that a bug fix works
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Qt AI Skills (this entry) | yes | 513 | ||
| code-review-skill | no | 2,153 | a general multi-language review skill without Qt C++ and QML linters | |
| Figma MCP Server | yes | OAuth | 2,128 | the official Figma MCP serves design data; carrying tokens and components into QML singletons and controls is done by the Qt skills |
README in short
The README explains the set: a table of 13 skills with the Review, Conceptual, Process and Tool types and a documentation MCP tool. It then covers the repository structure, the SKILL.md format and description rules, a tool-support table and installs for Claude Code, Codex, Copilot CLI, VS Code, Gemini CLI, Cursor and Windsurf. It closes with the docs site on doc.qt.io and contributor rules.
README badge
Original SKILL.md
---
name: qt-qml
description: >-
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").
license: LicenseRef-Qt-Commercial OR BSD-3-Clause
compatibility: >-
Designed for Claude Code, GitHub Copilot, and similar agents.
disable-model-invocation: false
metadata:
author: qt-ai-skills
version: "1.2"
qt-version: "6.x"
category: conceptual
---
# QML Coding Skill
## How to apply this skill
**On every invocation of this skill** — writing, editing, reviewing, or
validating QML — scan the connected MCP servers for a `run_qmlPreview` tool,
whose *purpose* is starting a QML preview or hot-reload session. Do this even
on read-only turns: a review is usually the turn *before* someone starts
changing things, and the scan reads an inventory you already have.
- **Found one — settle the Qt version first.** The server needs **Qt 6.12 or
newer** and does not report that itself; on older Qt the preview fails
silently, which is far harder to diagnose than an upfront check. Look inside
the project: `<build-dir>/CMakeCache.txt` → `Qt6_DIR` → `PACKAGE_VERSION` in
`<Qt6_DIR>/Qt6ConfigVersion.cmake`; failing that, ask the user. Don't
disqualify on `find_package(Qt6 6.x REQUIRED)` — it declares a *minimum*, so
it can confirm a project is new enough but never that it is too old. Settle
this once per session.
- **6.12 or newer** — read and follow
[references/qmlpreview.md](references/qmlpreview.md).
- **Older, or unknown** — say that live preview needs Qt 6.12 or newer, then