qt-qml-docs — Claude Code skill: QML reference docs
Reads .qml sources and related project files, then writes a Markdown reference per component: properties, signals, methods, dependencies.
npx skills add TheQtCompanyRnD/agent-skills --skill qt-qml-docs -a claude-codeWhat qt-qml-docs does
This skill produces reference documentation for QML components and Qt Quick applications. The agent goes through the sources — the .qml files themselves plus C++ backends, modules, qmldir, CMakeLists.txt — and writes one <ComponentName>.md per component. The structure is fixed: component overview, its place in the project and its dependencies, type hierarchy, a properties table with Property, Type, Default, Required and Description columns, then signals and methods as separate subsections, then how the component talks to the rest of the app.
Properties always come as a table, never a bullet list. Code fences are avoided everywhere except the Usage Example section, and that section appears only for reusable components whose root type is not Window or ApplicationWindow. Each signal gets a note on what triggers it and what the connected handler should do; each method gets its parameters, return type and side effects such as restarting a timer.
Before reading any source, the skill checks whether docs already exist in a doc/ directory next to the code. If they do, the agent stops and asks whether to update the existing files, skip them, regenerate everything or cancel. That matters when you touch one component in a larger project — you avoid silently overwriting docs for its neighbours. QDoc output is out of scope; you need a different tool for that.
What it helps with
- get a reference page for a QML component without walking every property by hand
- describe signals and methods so callers know when they fire
- tie a component to its C++ backend, qmldir and CMake targets
- update existing .md files instead of regenerating the whole project
- show a new developer the minimal way to instantiate a reusable component
Example prompts for the agent
- document this QML component
- write reference docs for my Qt Quick app
- go through the project folder and document every .qml file
How to install qt-qml-docs
1Skills CLI (Vercel)
npx skills add TheQtCompanyRnD/agent-skills --skill qt-qml-docs -a claude-code2Manually: put the files in place
~/.claude/skills/qt-qml-docs/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/qt-qml-docs/
1Skills CLI (Vercel)
npx skills add TheQtCompanyRnD/agent-skills --skill qt-qml-docs -a codex2Manually: put the files in place
.agents/skills/qt-qml-docs/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add TheQtCompanyRnD/agent-skills --skill qt-qml-docs -a cursor2Manually: put the files in place
.cursor/skills/qt-qml-docs/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install TheQtCompanyRnD/agent-skills qt-qml-docs2Manually: put the files in place
.github/skills/qt-qml-docs/SKILL.md1Skills CLI (Vercel)
npx skills add TheQtCompanyRnD/agent-skills --skill qt-qml-docs -a gemini-cli2Platform CLI
gemini skills install https://github.com/TheQtCompanyRnD/agent-skills --path skills/qt-qml-docsManually: put the files in place
.devin/skills/qt-qml-docs/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add TheQtCompanyRnD/agent-skills --skill qt-qml-docs -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about qt-qml-docs
How do I install qt-qml-docs in Claude?
Run npx skills add TheQtCompanyRnD/agent-skills --skill qt-qml-docs -a claude-code. The skill then lives at ~/.claude/skills/qt-qml-docs/SKILL.md.
What does qt-qml-docs do?
It reads QML sources and related project files, then writes a Markdown reference per component: overview, dependencies, hierarchy, a properties table, signals, methods and inter-component interactions.
Does it output QDoc format?
No. The skill targets Markdown and is not meant for QDoc output.