New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Build xTools

by x-tools-author in x-tools-author/x-tools

Builds the xTools Qt C++ desktop app, or a chosen X_APP target, with the repository's CMake and Ninja workflow on Windows, Linux or macOS and reports what was built.

LGPL-3.0Auto-check passedDevelopment

SKILL.md written in Chinese; this summary is our English description.

Install Build xTools

skills CLI
$ npx skills add x-tools-author/x-tools --skill build-xtools -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install x-tools-author/x-tools build-xtools --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/x-tools-author/x-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/build-xtools .claude/skills/build-xtools && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
build-xtools
GitHub stars
1.1k
Token cost
~572 tokens
SKILL.md length
134 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
LGPL-3.0

At a glance

Builds the xTools Qt C++ desktop app, or a chosen X_APP target, with the repository's CMake and Ninja workflow on Windows, Linux or macOS and reports what was built.

  • Works in 7 steps: 确认平台、编译器、Qt 安装路径，以及用户是否需要构建默认应用或特定 X_APP… → 优先使用仓库现有的 CMake 工作流，不要自行发明临时命令。 → Windows 上使用 Ninja + MSVC 开发环境，并通过… → …
  • Compiling xTools after changing its source code
  • SKILL.md covers 仓库构建基本信息, 执行步骤, Windows平台下Qt环境搜索 and Windows 构建流程, plus 3 more sections
  • Calls cmake

What it does

The agent first confirms the platform, compiler, Qt install path and whether the default app or a specific X_APP target is wanted, then sticks to the repository's existing CMake workflow instead of improvising commands. Windows builds use Ninja with an MSVC environment and CMAKE_PREFIX_PATH pointing at the Qt MSVC kit, Linux uses the Qt GCC path and macOS the Qt Clang path. A specific app is chosen with -DX_APP, as in xOscilloscope. Packaging targets such as xTools_zip, xTools_deb and xTools_appimage are built only after the main binary succeeds.

When the Qt path is not given on Windows, the agent searches common install folders and prefers the cmake bundled with Qt. It reports the build directory and target actually used, investigates a failed configure for missing dependencies, a wrong Qt path or compiler environment before changing anything else, and names the output artifacts on success. An existing build folder is not reused blindly, and the Windows scripts that delete it are run only when you ask for a clean build.

When your agent uses it

  • Compiling xTools after changing its source code
  • Building a specific X_APP target such as xOscilloscope
  • Producing a zip, deb or AppImage package of xTools
  • Diagnosing a failed CMake configure caused by the Qt path or compiler setup

Example prompts

  • “Build xTools on this Windows machine with Ninja and MSVC and tell me where the binary ends up.”
  • “Rebuild the xOscilloscope app after my last change.”
  • “Create the AppImage package for xTools on Linux.”

Requirements

  • CMake and Ninja
  • A Qt installation matching the compiler (MSVC, GCC or Clang)
  • Visual Studio build tools on Windows

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. 确认平台、编译器、Qt 安装路径，以及用户是否需要构建默认应用或特定 X_APP 目标。
  2. 优先使用仓库现有的 CMake 工作流，不要自行发明临时命令。
  3. Windows 上使用 Ninja + MSVC 开发环境，并通过 CMAKE_PREFIX_PATH 指定 Qt MSVC 套件路径。
  4. Linux 上使用正确的 Qt GCC 路径配置 CMake，再构建目标。
  5. MacOS 上使用正确的 Qt Clang 路径配置 CMake，再构建目标。
  6. 若只是验证编译，先构建最小范围的相关目标。
  7. 若同时需要打包，在主二进制目标构建成功后再构建打包目标。

What it can do on your machine

Read from SKILL.md and the folder at commit 6214c41. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cmake

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Build xTools loads about 572 tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 134 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~20
When it runs · the whole SKILL.md, loaded when a task matches
~572

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from x-tools-author/x-tools at commit 6214c41, republished under its LGPL-3.0 licence (© x-tools-author). 134 words, ~572 tokens.

Download SKILL.mdSave it as .claude/skills/build-xtools/SKILL.md (or your agent's skills folder).
name
build-xtools
description
使用本项目的 CMake 工作流构建 xTools 或指定的 X_APP 目标。当用户要求编译、重新构建或生成打包产物时使用此技能。
argument-hint
[目标] [Qt路径]
disable-model-invocation
true

构建 xTools

当任务是编译此仓库、代码修改后重新构建或生成打包产物时，使用此技能。

仓库构建基本信息

  • 本项目是基于 CMake 构建的 Qt C++ 桌面应用程序。
  • 主构建入口为 CMakeLists.txt。
  • 为WindowsXP及更新操作系统构建参考脚本见 ci-build-windows-xp.bat。
  • 为Windows7及更新操作系统构建参考脚本见 ci-build-windows-7.bat。
  • 为其它系统构建，按后续步骤说明配置 CMake 和构建命令。

执行步骤

  1. 确认平台、编译器、Qt 安装路径，以及用户是否需要构建默认应用或特定 X_APP 目标。
  2. 优先使用仓库现有的 CMake 工作流，不要自行发明临时命令。
  3. Windows 上使用 Ninja + MSVC 开发环境，并通过 CMAKE_PREFIX_PATH 指定 Qt MSVC 套件路径。
  4. Linux 上使用正确的 Qt GCC 路径配置 CMake，再构建目标。
  5. MacOS 上使用正确的 Qt Clang 路径配置 CMake，再构建目标。
  6. 若只是验证编译，先构建最小范围的相关目标。
  7. 若同时需要打包，在主二进制目标构建成功后再构建打包目标。

Windows平台下Qt环境搜索

  • 优先确认用户提供的 Qt 路径是否正确，且包含与 Visual Studio 版本匹配的.
  • 优先使用提供的Qt路径，如果用户未提供路径，尝试在常见安装位置（如 C:/Qt/、D:/Qt/Qt/、D:/512/Qt/Qt/）搜索 Qt 版本。
  • 优先使用Qt配套的cmake程序，一般位于Qt安装目录下的 Tools/CMake/bin 或 Tools/CMake 子目录中。

Windows 构建流程

  1. 加载 Visual Studio x64 构建环境。
  2. 使用 Ninja 和 Qt MSVC 路径配置 CMake。
  3. 构建 xTools。
  4. 可选：构建 xTools_zip。

参考命令：

bat
call "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat" x64
cmake -S . -B build\my-build -G Ninja -DCMAKE_PREFIX_PATH=D:/Qt/Qt/6.10.3/msvc2022_64 -DCMAKE_BUILD_TYPE=Release
cmake --build build\my-build --target xTools
cmake --build build\my-build --target xTools_zip

若用户要求构建特定 xApp，在配置时添加 -DX_APP=<名称>，例如：-DX_APP=xOscilloscope。

示例：

bat
cmake -S . -B build\xoscilloscope -G Ninja -DCMAKE_PREFIX_PATH=D:/Qt/Qt/6.10.3/msvc2022_64 -DCMAKE_BUILD_TYPE=Release -DX_APP=xOscilloscope
cmake --build build\xoscilloscope --target xOscilloscope

Linux 构建流程

参考命令：

cmake -S . -B build/linux -G Ninja -DCMAKE_PREFIX_PATH=/path/to/Qt/6.10.3/gcc_64 -DCMAKE_BUILD_TYPE=Release
cmake --build build/linux --target xTools

Linux 打包目标（环境支持时）：xTools_deb、xTools_appimage。

验证规则

  • 报告实际使用的构建目录。
  • 报告实际构建的目标名称。
  • 若配置失败，先定位缺失依赖、Qt 路径问题或编译器环境问题，再做其他修改。
  • 若构建成功，说明预期的输出产物路径或已生成的打包目标。

仓库注意事项

  • build/ 下已存在构建目录，不能直接复用，需先确认 Qt 版本和生成器是否匹配。
  • 参考 Windows 脚本在全新配置前会删除构建目录，仅当用户明确要求清理构建或目录明显不兼容时才执行此操作。
  • 代码修改后优先做小范围验证构建，再尝试打包目标。

© x-tools-author, LGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .github/skills/build-xtools of x-tools-author/x-tools.

Open the folder on GitHubat commit 6214c41

Compare with similar skills

Build xTools next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Build xTools compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Build xTools this skillx-tools-author/x-tools1.1k—~572Automated safety check: PassLGPL-3.0
YugabyteDB ASH Instrumentationyugabyte/yugabyte-db11k—~4.5kAutomated safety check: PassCustom licence
pybind11 Release Preparationpybind/pybind1118k—~1.7kAutomated safety check: PassCustom licence
Qt Cpp ReviewSerial-Studio/Serial-Studio7.2k—~4.3kAutomated safety check: PassCustom licence
Paddle Eager GraphPaddlePaddle/Paddle24k—~562Automated safety check: PassApache-2.0
ONNX Runtime Source Buildmicrosoft/onnxruntime22k—~1.4kAutomated safety check: PassMIT

Similar skills

  • YugabyteDB ASH Instrumentation

    yugabyte/yugabyte-db

    Procedure for adding or changing YugabyteDB Active Session History wait states in TServer and DocDB C++ code, including the macro to use for sync and async paths.

    11k GitHub stars~4.5k tokensUpdated today
    DevelopmentAuto-check passed

  • pybind11 Release Preparation

    pybind/pybind11

    Opens the pybind11 release-preparation pull request: picking the release base, bumping the version in common.h and integrating the changelog, following docs/release.rst.

    18k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed

  • Qt Cpp Review

    Serial-Studio/Serial-Studio

    Qt6/C++ deep code review for Serial Studio. An agent skill from Serial-Studio/Serial-Studio.

    7.2k GitHub stars~4.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Paddle Eager Graph

    PaddlePaddle/Paddle

    A skill your agent uses when navigating Paddle eager-mode (dynamic graph) source code, tracing forward/backward execution, debugging autograd issues, understanding PyLayer, or investigating…

    24k GitHub stars~562 tokensUpdated today
    DevelopmentAuto-check passed

  • ONNX Runtime Source Build

    microsoft/onnxruntime

    Official

    Builds ONNX Runtime from source with its build scripts, explaining the update, build and test phases, key flags and where the build output lands.

    22k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Esp32 Firmware Engineer

    alxv2016/folloup-sticky

    ESP32 firmware engineering for ESP-IDF projects. An agent skill from alxv2016/folloup-sticky.

    116 GitHub starsUsed in 1 repo~3.8k tokens
    DevelopmentAuto-check passed

More from x-tools-author/x-tools

All 10 skills in this repo

  • Qt C++ Code Review

    x-tools-author/x-tools

    Read-only review of Qt6 C++ code that combines a deterministic lint script with six parallel analysis agents and reports only high-confidence issues.

    1.1k GitHub starsUsed in 2 repos~4.3k tokens
    Auto-check passed

  • Qt6 QML Code Reviewer

    x-tools-author/x-tools

    Runs a 47-rule deterministic QML linter, then six parallel deep-analysis passes over bindings, layout, loaders, delegates, states, and performance.

    1.1k GitHub starsUsed in 1 repo~3.6k tokens
    Auto-check passed

  • QML Reference Documentation

    x-tools-author/x-tools

    Generates standalone Markdown reference docs for QML components and Qt Quick applications from .qml source and related C++ and build files, one file per component.

    1.1k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Qt QML Profiler

    x-tools-author/x-tools

    Finds what is making a Qt Quick interface stutter or drop frames by capturing a profiler trace and tracing the slow spots back to the QML source.

    1.1k GitHub starsUsed in 1 repo~5.2k tokens
    Auto-check passed

  • Qt C++ Reference Docs

    x-tools-author/x-tools

    Generates standalone Markdown reference docs for Qt and plain C++ source files, from Widgets and Quick classes to utility headers and main.cpp, as prose and tables.

    1.1k GitHub starsUsed in 1 repo~6.2k tokens
    Auto-check passed

  • QML Coding Best Practices

    x-tools-author/x-tools

    Applies QML best practices when writing, reviewing, refactoring or debugging QML code, with Qt 5 and Qt 6 import rules and concise, rule-silent output.

    1.1k GitHub starsUsed in 1 repo~3.4k tokens
    Auto-check passed

Works with

Categories

Questions about Build xTools

What does Build xTools do?

Builds the xTools Qt C++ desktop app, or a chosen X_APP target, with the repository's CMake and Ninja workflow on Windows, Linux or macOS and reports what was built. The agent first confirms the platform, compiler, Qt install path and whether the default app or a specific X_APP target is wanted, then sticks to the repository's existing CMake workflow instead of improvising commands. Windows builds use Ninja with an MSVC environment and CMAKE_PREFIX_PATH pointing at the Qt MSVC kit, Linux uses the Qt GCC path and macOS the Qt Clang path.

When should I use Build xTools?

Build xTools fits situations like: compiling xTools after changing its source code; building a specific X_APP target such as xOscilloscope; producing a zip, deb or AppImage package of xTools; diagnosing a failed CMake configure caused by the Qt path or compiler setup.

How do I install Build xTools in Claude Code?

Run `npx skills add x-tools-author/x-tools --skill build-xtools -a claude-code`. Or copy the skill folder (.github/skills/build-xtools in x-tools-author/x-tools) into .claude/skills/build-xtools in your project. Claude Code loads it when a task matches its description.

How do I install Build xTools in Codex?

Run `npx skills add x-tools-author/x-tools --skill build-xtools -a codex`. Or copy the skill folder (.github/skills/build-xtools in x-tools-author/x-tools) into .agents/skills/build-xtools in your project. Codex loads it when a task matches its description.

Can I use Build xTools in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add x-tools-author/x-tools --skill build-xtools -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/build-xtools, .gemini/skills/build-xtools, .github/skills/build-xtools and .opencode/skills/build-xtools in your project.

What does Build xTools need to run?

Going by SKILL.md and its folder, Build xTools needs the command-line tools its instructions call (cmake). Our summary lists: CMake and Ninja; A Qt installation matching the compiler (MSVC, GCC or Clang); Visual Studio build tools on Windows.

Does Build xTools access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Build xTools safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Build xTools use?

Build xTools is published under the LGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Build xTools use?

About 572 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Build xTools?

Skills that share tags, products or a category with Build xTools: YugabyteDB ASH Instrumentation (yugabyte/yugabyte-db, 11k stars), pybind11 Release Preparation (pybind/pybind11, 18k stars), Qt Cpp Review (Serial-Studio/Serial-Studio, 7.2k stars) and Paddle Eager Graph (PaddlePaddle/Paddle, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Build xTools?

x-tools-author (a GitHub user) maintains it in x-tools-author/x-tools, which has 1,092 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 3, 2026.

Source: x-tools-author/x-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.