Add, inspect, repair, or validate CodeDrobe Core adapters for Chromium/Electron AI desktop applications.
SkillScore95Maintained
Automatic
◆Coding pack
Last verified 8/24/2026
What it changes
Passed 20 of 21 test cases with the skill, and 11 of 21 without it.
Without skill55%
With skill95%
Checks it passed that the model alone missed
Directs the developer to read references/testing.md.
Directs the developer to read references/architecture.md.
Designates rootAny as the sole blocking landmark detector.
and 9 more in the full report
9 fixed12 passed either way1 still failing0 broke
Pass-rate lift
+41 pp
Tokens
-21%
Agent turns
0%
Response time
-57%
Model gemini-3.6-flashMeasured 8/24/2026v121 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
When setting up landmark selectors for root container, navigation panel, workspace area, and composer box, which exact landmark is designated as blocking?
What was checked, without and with the skill
Checked
Without skill
With skill
Designates rootAny as the sole blocking landmark detector.
Missed
Passed
case-19 · 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.md41 lines5 files
CodeDrobe Adapter Development
Work in the @codedrobe/core repository. Keep the adapter lightweight and prove selectors against a real installed application; never infer renderer compatibility from an app name, executable path, or screenshot alone.
Read the relevant references
Read references/architecture.md before changing ownership between Core, adapters, renderer profiles, themes, Skills, or Desktop.
Read references/adapter-contract.md before editing adapter code, exports, host settings, or types.
Read references/dom-inspection.md before collecting CDP targets or choosing selectors.
Read references/testing.md before claiming support or updating lastVerified.
Add or repair an adapter
Inspect the current Core tree, adapter registry, tests, CLI help, and working-tree changes.
Locate the actual installed app and record its app version/build. Do not overwrite unrelated local changes.
Launch the real app with loopback CDP on a configurable, unoccupied port. Do not restart or terminate it without authorization.
Inspect /json/list, select the actual renderer, and run codedrobe dom snapshot on every relevant route to collect privacy-preserving semantic DOM evidence.
Choose only cross-route landmarks for the adapter: root, sidebar/navigation, workspace/content, and composer/input. Only rootAny should block (it doubles as the boot detector); declare panels the app can hide — sidebars in popped-out or collapsed windows — as recommended, since compatibility is judged per window.
Put app- or theme-specific layout nodes in theme verification contexts, not the adapter.
Implement the adapter, registry export, types, and focused tests. Add a renderer profile or host-settings module only when the application requires that behavior.
Probe the real renderer, then apply and verify a minimal package. Validate the home and conversation contexts separately.
Restore the renderer and any transactional host settings. Confirm cleanup before finishing.
Update lastVerified only after real-app verification succeeds, including the observed version/build and date.
Compatibility failure workflow
Reproduce with codedrobe probe --app <id> --theme <package>.
Separate adapter landmark failures from theme-specific missing nodes.
Inspect the live DOM and computed layout; do not repair from stale documentation alone.
Prefer a stable alternative selector before broadening any lists.
Keep failure output concrete: requirement name plus every attempted selector.
Add a regression test before updating lastVerified.
Guardrails
Never patch application bundles, app.asar, code signatures, WindowsApps ownership, or user authentication data.
Bind CDP to 127.0.0.1 and reject occupied custom ports instead of killing unknown processes.
Avoid generated CSS-module hashes, localized text, deep child chains, and broad selectors such as body * in adapters.
Keep optional decoration out of adapter requirements.
Preserve custom installation paths and user-selected CDP ports throughout detect, launch, probe, apply, verify, watch, and restore.