Skip to content
cccskills
FreePublished on GitHub

desktop-automation-protocol

How to use windows-computer-use-mcp effectively — tool selection, focus rules, safety, and mission design.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Desktop automation protocol (windows-computer-use-mcp)

Tool selection guide

GoalToolExample
Click a known buttonautomation_elements(click, title="Save")fast, needs exact title
Click by intentautomation_smart(click="the Save button")slower, finds across all windows
Complex multi-stepautomation_mission(run="save file as PDF")autonomous loop with retry
Record + replayautomation_macro(record) → stop → replayrepeatable sequences
Wait for eventautomation_watch(start, "window_appears", "Update")event-driven triggers
Explore desktopautomation_smart(discover)get all running apps
Extract + chainautomation_mission(workflow, actions, store_as, dollar-ref)cross-app data pipeline

Focus rules

  • After automation starts, do not Alt+Tab or touch the mouse
  • The target window must stay in foreground during click/type sequences
  • If HITL approval appears, approve it and let the target window regain focus
  • Prefer reading logs between paused steps or on a second monitor

Safety

  • Read docs/SAFETY.md before production use
  • Pair with virtualization-mcp for sandbox/VM isolation when running untrusted automation
  • Opt-in features (face, keylogger) are off by default — enable only when needed

Mission design (automation_mission)

For run operation: provide a clear, concrete goal. The server decomposes via LLM sampling. For workflow operation: provide explicit steps with tool, params, label, and optional store_as/dollar-ref for data chaining. For self-healing: set app_path on steps so the mission can re-launch crashed apps.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

See all skills by hybridlabor-api

Report a problem with this skill