Create, inspect, convert, apply, replace, verify, troubleshoot, update, publish, or restore reversible CodeDrobe themes for supported Chromium/Electron AI desktop apps, including OpenAI Codex, Tencent WorkBuddy, QoderWork (CN/global), and TRAE SOLO (global/CN).
SkillScore74Maintained
Automatic
◆Frontend / UI pack
Last verified 8/24/2026
What it changes
Passed 14 of 19 test cases with the skill, and 8 of 19 without it.
Without skill43%
With skill74%
Checks it passed that the model alone missed
Binds Chrome DevTools Protocol connections exclusively to loopback
Scopes application target styles under html.codedrobe-host-qoderwork
Refuses to evaluate theme JavaScript files or load external CSS resources
and 11 more in the full report
10 fixed7 passed either way3 still failing3 broke
Pass-rate lift
+30 pp
Tokens
+23%
Agent turns
0%
Response time
-50%
Model gemini-3.6-flashMeasured 8/24/2026v117 of 23 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
I'd like to install the local package `/themes/cyberpunk.codedrobe-theme` onto my desktop client. I haven't specified which client application I am running.
What was checked, without and with the skill
Checked
Without skill
With skill
Asks one concise clarification question to identify the explicit target application before executing apply commands
Missed
Passed
case-04 · gemini-3.6-flash · 8/24/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md81 lines13 files
CodeDrobe Theme
Use the published @codedrobe/core CLI as the only runtime. Keep this Skill instruction-only: do not recreate injectors, launch scripts, package parsers, or application patchers inside the Skill.
Route the request
Identify the target app explicitly. Run codedrobe apps --json when support or defaults are uncertain.
Read references/cli.md before choosing an installed, npm, or Bun command runner.
Read only the target-specific reference:
Codex: references/codex.md
WorkBuddy: references/workbuddy.md
QoderWork: references/qoderwork.md
TRAE SOLO: references/traework.md
For theme creation, images, CSS, packaging, or legacy conversion, read references/theme-authoring.md.
When the request includes an attached or local visual reference, read references/reference-image.md.
For new or repaired CSS, read references/dom-snapshot.md and references/css-templates.md.
For the complete Miku Future Beats / 初音未来 example, read references/miku-future-beats-example.md.
For probe, verification, screenshots, missing nodes, CDP failures, or app updates, read references/verification.md.
To publish or submit a theme to the CodeDrobe store, read references/publish.md.
Interpret common requests
“参考这张图片，帮我生成一个 Codex 皮肤”：inspect the supplied image, create a Codex target from a live Codex DOM snapshot, package it, and verify the native UI in Codex.
“把这个视觉风格同时做成 Codex 和 WorkBuddy 皮肤”：create one theme package with separate target CSS and shared named image assets.
“用玩偶姐姐示例改成蓝色版本”：copy the bundled example to a writable project, change its tokens/assets, refresh live selectors, and verify both requested contexts.
“这个主题更新应用后错位了”：capture fresh snapshots, repair theme CSS and theme-specific verification nodes, then repack and compare screenshots.
“帮我安装这个 .codedrobe-theme”：inspect, probe, apply, and verify the supplied package; do not recreate it unless validation fails and the user asks for repair.
“从商店装一个复古主题到 Codex”：codedrobe theme search to resolve the slug (confirm the pick when several match), codedrobe theme download (integrity-verified, lands in ~/.codedrobe/themes), then the normal inspect → probe → apply → verify flow.
“把这个主题发布到 CodeDrobe 商店”：complete the theme.catalog listing metadata, pack, confirm with the user, then codedrobe theme publish (and --submit only with separate confirmation).
Treat the named target app as explicit. If no target is named and it cannot be inferred from the supplied package or current task, ask one concise question before launching or applying anything.
Apply an existing theme
Inspect the package before applying it.
Detect the application and resolve any user-provided installation path or CDP port.
Probe the live renderer with the selected theme. Compatibility is judged per window: a window missing required adapter or theme nodes is skipped, and the apply fails only when no window qualifies. A probe run while the app is still on its loading screen reports every landmark missing — wait for the root landmark before treating that as incompatibility.
Apply the theme. Never add --restart-existing unless the user authorized closing and restarting the running application.
Verify the installed theme and capture an absolute-path screenshot when visual confirmation matters.
Inspect both the home screen and a normal conversation when the theme styles both contexts.