From desktop-act
Computer-use primitives for the X11 desktop on this dev box. Use when a task needs to drive a GUI app, browser, or interact with anything visual that the parent Claude session needs to see and act on.
How this skill is triggered — by the user, by Claude, or both
Slash command
/desktop-act:desktop-actThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This plugin exposes computer-use primitives via the `mcp__desktop-act__*` tools
This plugin exposes computer-use primitives via the mcp__desktop-act__* tools
plus a one-shot act(goal) that runs an autonomous loop via OAuth (no API key).
act(goal) spawns a sub-session via claude-agent-sdk for hands-off
goals — but the streaming-friendly path is calling primitives directly.Connect via noVNC at: http://:6081 That bridges to Xvnc :1. Whatever the primitives do is visible there in real time.
| Task | Approach |
|---|---|
| Browser dashboard with auth (Stripe/Vercel/AWS/etc) | Prefer mcp__kapture__* (Sam's real Chrome) |
| Local app you need to click/type into | desktop-act primitives |
| Generic public site automation | mcp__playwright__* |
| Perf/console/Lighthouse | mcp__chrome-devtools__* |
| "Just do it" hands-off | mcp__desktop-act__act(goal) |
See ~/.claude/skills-library/browser-automation.md for the full decision tree.
npx claudepluginhub lifecycle-innovations-limited/desktop-actCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.