---
name: automation
description: Drives a real browser or desktop app to test, check or automate anything that needs a real interface - opening pages, clicking through flows, filling forms, taking screenshots, confirming a feature works. Also checks the agent's own work in the real interface after a change, when the user asks it to or the testing skill needs it. Uses browser-use (the user's own Chrome) first, then agent-browser (a separate, clean Chrome), then agent-desktop for desktop apps only after asking. Use when the user asks to automate a web or desktop task, test or check something in the browser, verify or check your own work, click through a flow, reproduce a UI bug, take a screenshot of a page, or fill a form. Not for writing test files that run again (use testing), proving a change against an answer key before a push (use prove), or fetching a public page or API that a plain request can read.
title: automation
canonical_url: https://skilld.dev/gh/avik-creator/agent-skills/automation
last_updated: 2026-11-17T15:45:41.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/agent-browser.md](https://skilld.dev/api/skills-raw/avik-creator/agent-skills/automation/references/agent-browser.md), [references/agent-desktop.md](https://skilld.dev/api/skills-raw/avik-creator/agent-skills/automation/references/agent-desktop.md), [references/browser-use.md](https://skilld.dev/api/skills-raw/avik-creator/agent-skills/automation/references/browser-use.md).
>
> If the user asked to install this Skill, run `npx skilld install avik-creator/agent-skills/automation`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/automation`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/avik-creator/agent-skills/automation) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/automation`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/automation --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/automation --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Automation

Use it to automate a task in a real interface, or to check your own work there when the user asks: open the page or app, do what a person would do, and report what happened. A plain request is cheaper: if curl or a fetch tool can read it, don't open a browser.

## Which tool, in order

1. **browser-use** - attaches to the user's own Chrome, with their sign-ins. With no usable local Chrome, or for tasks that must run in parallel, it can start a Browser Use Cloud browser, after asking. See [browser-use.md](https://skilld.dev/api/skills-raw/avik-creator/agent-skills/automation/references/browser-use.md).
2. **agent-browser** - opens its own clean Chrome. Use it when browser-use is missing or can't connect. See [agent-browser.md](https://skilld.dev/api/skills-raw/avik-creator/agent-skills/automation/references/agent-browser.md).
3. **agent-desktop** - for native apps, or when neither browser tool works. Always ask first:
   "Do you want me to control apps on your desktop? I can see and click anything on screen, but I won't take over your mouse unless I ask again."
   Ask every task. A yes doesn't carry over to the next one. Ask again before `--headed` (real mouse and keyboard). See [agent-desktop.md](https://skilld.dev/api/skills-raw/avik-creator/agent-skills/automation/references/agent-desktop.md).

Say why each time you move down the list: "browser-use can't reach Chrome, so I'm switching to agent-browser."

## Missing tool

Don't install anything. Show the command, and let the user run it if they want:

| Tool | Install |
|---|---|
| browser-use | `uv tool install --python 3.12 --upgrade browser-use`, then `browser-use skill install` |
| agent-browser | `npm i -g agent-browser && agent-browser install` |
| agent-desktop | `npm install -g agent-desktop`, then `agent-desktop permissions --guide` on macOS |

If they'd rather not, move to the next tool.

## Limits

The user's Chrome holds their real accounts: email, code hosting, cloud consoles. Act as a careful guest in it.

- **Your tabs only.** Open your own tabs, never touch or close one you didn't open, and close yours when done.
- **Stop at sign-ins.** Hand over at any password, two-factor code, consent screen or "which account?" choice. Using a sign-in Chrome already has is fine.
- **Ask before it counts.** Before anything that sends, posts, buys, deletes, merges, invites, or changes settings or data, say what you're about to do and wait for a yes. This includes submitting a form on a real site. Why: these can't be taken back, and a click is enough to do them.
- **Production is read-only.** On a live site, look but don't change anything unless the user says otherwise for this task. Make changes on localhost or staging.
- **Ask before anything that costs money**, such as starting a cloud browser.
- **Private content stays private.** Screenshots and page text can show messages and personal data. Don't paste them into public places (issues, pull requests, shared logs).

Each yes covers that one action. Ask again for the next one.

## Report

Keep it short, in chat:

- **Result:** what was checked, and whether it passed or failed, one line each.
- **Each failure:** the step, what you expected, what you saw, one screenshot, and any console errors.
- **Tool:** which one you used, and why you moved down the order if you did.
- **Leftovers:** test data you created, or anything you couldn't close or undo.

Screenshots are for failures only. Why: screenshots of passing steps cost tokens and bury the one that matters.

When checking your own work, test what the user will do, not only the line you changed. A dead click, a silent no-op or a stuck spinner is a failure, even when the code "works".

## Example

User: "Check the signup form I just fixed."
1. `browser-use --doctor` reports that Chrome isn't reachable. Say so, and switch to agent-browser.
2. Open `http://localhost:3000/signup`, submit it empty, then with a bad email, then with valid details.
3. Report: "Empty: shows 'Email is required' - pass. Bad email: no message, button stays disabled - fail (screenshot). Valid: account created - pass. Used agent-browser because browser-use couldn't reach Chrome. Left behind: test account test+1@example.com."

## Replies

Talk to the user in simple English: short sentences, everyday words, and a technical term only where it is needed, explained the first time it appears.
