Infrastructure skill - application UI observation and scoped action tools for DCC-adjacent workflows. Use ui_control__snapshot, ui_control__find, ui_control__act, ui_control__wait_for, and ui_control__stop_computer_use for DCC UI Control when a host UI state is not exposed through native DCC APIs. Use ui_control__record_clip for exact-window, hash-verified gameplay capture. Use the separate, operator-granted ui_control__system_operation only for bounded Windows plug-in setup. Prefer DCC-native skills first, then use ui_control as a policy-controlled fallback.
$npx -y skills add dcc-mcp/dcc-mcp-core --skill ui-controlInstalls into the current project.
Run `npx skills use "https://github.com/dcc-mcp/dcc-mcp-core" --skill "dcc-mcp/dcc-mcp-core/ui-control"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/dcc-mcp/dcc-mcp-core" that are relevant to the current task. Run `npx skills add "https://github.com/dcc-mcp/dcc-mcp-core"` and select the relevant skills, then follow their instructions.