CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

desktop-brand-builder

Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is an exemplary operational skill: every step is executable, validation and failure recovery are explicit, and mechanical detail is correctly delegated to the bundled script. The only weakness is mild redundancy (repeated single-use warnings and the Electron-era history note) that could be trimmed for token efficiency.

DimensionReasoningScore

Conciseness

The body is dense and operational, and its explanations are repo-specific facts Claude would not know (root install needed because build:runtime shells out to cross-env, updater pubkey semantics, QWEN_DESKTOP_TARGET arch handling). Minor trimmable redundancy remains: the single-use-script warning appears twice in Failure Handling and the Electron-era/PR 9085 history paragraph is contextual padding.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout: git clone/checkout, a complete brand.json example, npm installs, the bundled script invocation with flags, packaging and cross-compile commands with the required env var, signing key generation, and validation commands (sha256sum, hdiutil verify), plus worked derivation examples like acme-ai to Acme AI.

5 / 5

Workflow Clarity

The sequence is explicit (isolate clone, create brand.json, install, run script, package, validate) with a numbered validation checklist and a failure-handling section containing recovery loops (stop on clone failure, fresh clone when already branded, discard and restart on bad config). Validation for this risky batch operation is present, so the workflow cap does not apply.

5 / 5

Progressive Disclosure

A well-sectioned overview delegates mechanical work to the one-level-deep bundled script, whose path, usage, and enumerated behavior are given along with a do-not-hand-edit guard; the actual bundle (scripts/brand-create.mjs) matches the referenced path and usage, with no nested or buried references.

5 / 5

Total

19

/

20

Passed

Description

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

The description is strong: it explicitly covers both what the skill does and when to use it, with concrete, natural trigger terms and a clearly distinct niche. It is slightly held back by listing only a single high-level action and by missing a few common phrasings such as "branding" or "logo".

Suggestions

Add one or two more concrete actions to the description, e.g. "regenerates the icon set from the logo and packages signed/unsigned DMG, EXE, AppImage, or deb installers", to move specificity from one action verb to several.

Include the natural terms users would say such as "branding", "logo swap", or "reskin the desktop app" to round out trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain and concrete inputs ("using a minimal brandId and logo") but offers only one main action verb ("Generate a branded ... desktop package"); it does not list the several sub-actions the skill performs, matching the 1-2-concrete-actions anchor rather than the several-actions anchor.

3 / 5

Completeness

It explicitly answers both what ("Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo") and when ("Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage including synonyms ("custom, white-label, or rebranded") and artifact formats ("DMG/EXE/AppImage/deb"), but misses a few natural phrasings users would say such as "branding", "logo", or "app icon".

4 / 5

Distinctiveness Conflict Risk

A clear niche (branding the Qwen Code Tauri desktop shell, "on top of packages/desktop") with distinct triggers like white-label and DMG/EXE/AppImage/deb builds, giving minimal overlap risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

QwenLM/qwen-code

Path

packages/desktop/.agents/skills/desktop-brand-builder/SKILL.md

Reviewed

Table of Contents

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.