Skip to content
TrustedSkillsbeta
Back to all skills

Qt Compatibility Build

Checked
re2zero·vlatest·other·MIT

Automates Qt application builds across diverse platforms, ensuring compatibility and reducing development overhead.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add re2zero/deepin-skills --skill qt-compatibility-build -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

re2zero

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned re2zero/deepin-skills at 0095fec1c6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
0095fec1c6
Manifest
qt-compatibility-build/SKILL.md
Scanned
1 file, 211 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automates builds for Qt applications, specifically designed to handle projects requiring support for both Deepin V25 (Qt6) and V20 (Qt5) versions simultaneously. It simplifies CMake configuration by automatically detecting the active Qt version (either Qt5 or Qt6) and dynamically mapping associated DTK versions, eliminating the need for hard-coded version references within the build system. This reduces development overhead and ensures compatibility across different environments.

When to use it

  • Your project uses a CMake build system.
  • You need to support both Deepin V25 (Qt6) and V20 (Qt5) versions from the same codebase.
  • Your CMakeLists.txt files contain hard-coded references to Qt5:: or Qt6:: in target_link_libraries.
  • Your project includes hard-coded DTK:: or Dtk6:: dependencies within find_package calls or linking processes.
  • You require dynamic library linking based on the detected Qt version.

Key capabilities

  • Automatic detection of Qt versions (Qt5 or Qt6).
  • Dynamic mapping of DTK versions to the installed Qt version.
  • Simplifies CMake configuration for dual-version support (V25/V20).
  • Supports dynamic linking based on detected Qt version.
  • Automates find_package calls for both Qt and DTK.

Example prompts

  • "Build the project with Qt6."
  • "Configure CMake for V20 support."
  • "Detect the current Qt version in my build system."

Tips & gotchas

  • This skill is specifically designed for projects using a CMake build system and requiring both Qt5 and Qt6 compatibility.
  • It's not suitable for projects without CMake or those that don’t use Qt.
  • The -DQT_DIR parameter in the cmake command is optional; CMake can auto-detect if it isn't provided.