# droid-control

droid-control is a skill for automating terminal TUIs, browsers, and desktop apps. Record demos, run tests in real environments, and capture QA proof.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 118 installs · ★ 129 repo stars
- Author: Factory-AI
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Factory-AI/factory-plugins/tree/HEAD/plugins/droid-control/skills/droid-control/SKILL.md
- Updated: 2026-10-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/droid-control

## What it does

droid-control routes commands to the right driver: tuistory for terminal sessions, browser-use for web pages and Electron apps, cua for native GUI applications. The skill handles non-deterministic behavior — network latency, variable output, LLM responses — by waiting or pausing between actions. When an action fails or feels uncertain, it observes the current state and retries without switching drivers or escalating permissions.

Each component (terminal-use, browser-use, desktop-use, capture, compose, verify) is a separate file at `${DROID_PLUGIN_ROOT}/skills/droid-control/atoms/`. The skill reads them in order: identify the target app, choose which stages to load (record, assemble, verify). Terminal sessions use `tctl`, which wraps `asciinema rec` and isolates each run with a RUN_ID and temp directory so concurrent sessions don't collide.

When building demo or QA artifacts, compose assembles video via fframes: title cards, layouts, transitions, effects. Verify checks the result against stated goals. The default is `single`-clip layout (one scene); `side-by-side` is not created automatically unless the deliverable is explicitly a comparison.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add Factory-AI/factory-plugins --skill droid-control -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/droid-control/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/droid-control/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add Factory-AI/factory-plugins --skill droid-control -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/droid-control/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add Factory-AI/factory-plugins --skill droid-control -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/droid-control/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install Factory-AI/factory-plugins plugins/droid-control/skills/droid-control
```

2. **Manually: put the files in place**
- File: `.github/skills/droid-control/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add Factory-AI/factory-plugins --skill droid-control -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/Factory-AI/factory-plugins --path plugins/droid-control/skills/droid-control
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/droid-control/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add Factory-AI/factory-plugins --skill droid-control -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/Factory-AI/factory-plugins/tree/HEAD/plugins/droid-control/skills/droid-control/SKILL.md

## When to use it
- Record terminal or browser screen with proof of feature behavior
- Automate clicks and input in a native desktop application
- Build a video demo with title cards, transitions, and visual effects
- Run tests in real environments instead of mocks
- Capture GUI application behavior for QA reporting

## Example prompts
- Record me typing in the terminal and running `npm test` on a real project
- Open a browser, navigate to the site, and click the payment button—record the screen as video
- Automate clicks in a macOS app and build a video demo with a branded title card

## Similar
- [Cognitive Browser](https://affpapa.org/en/nevibecode/mcp/cognitive-browser.md) — MCP server · 19566 installs
- [mac-control-mcp](https://affpapa.org/en/nevibecode/mcp/mac-control-mcp.md) — MCP server · ★ 19 repo stars
- [cate-cli](https://affpapa.org/en/nevibecode/skills/cate-cli.md) — skill · ★ 2248 repo stars
- [playwright-cli](https://affpapa.org/en/nevibecode/skills/playwright-cli.md) — skill · 221700 installs
- [firecrawl-qa](https://affpapa.org/en/nevibecode/skills/firecrawl-qa.md) — skill · 31700 installs
- [om-qa-buddy](https://affpapa.org/en/nevibecode/skills/om-qa-buddy.md) — skill · 1900 installs

From the same set: [factory-ai/factory-plugins](https://affpapa.org/en/nevibecode/by/factory-ai/factory-plugins.md) — 17 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
