Individual skill

ui-control

Infrastructure skill for application UI observation, scoped action, waits, and CUA trajectory recording when a typed DCC tool cannot expose the needed interface. Use this skill when the user asks for CUA, UI Control, dcc-cua, or application UI automation in a DCC. Prefer typed DCC tools first and CDP for browsers; use the standalone dcc-cua backend for native applications.

python/dcc_mcp_core/skills/ui-control/SKILL.md

Read pinned source

Source commit bcd69852790ee657b7543e83b122ea2cb965beb5

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
73
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# DCC UI Control

The Agent Host owns user authorization. Core never enables the standalone
Host's legacy native confirmation popup, including when menu invocation is
allowed. Missing authorization remains a typed refusal; do not auto-approve or
retry it through another input route. For bounded task authorization, use the
project-owned DCC-CUA task bridge and its exact target/scope checks.

Use application UI automation only when a typed DCC skill, host API, or adapter
script reports `unsupported` or `capability_missing`. Policy denial, user
interruption, authentication, and desktop unavailability are stop conditions.

## Backend order
Back to top