UI Automation

Use when a task needs a rendered interface observed, a browser driven, or a desktop application operated — post-deploy UI acceptance, checking whether a page renders as expected, driving software with no usable CLI, or capturing visual evidence — and should be executed by the external Codex agent rather than in this session. Not for writing automation code such as test suites or Playwright specs. Covers dispatching through `codex exec`, the artifact contract, and evidence recovery.

24 stars 5 forksProductivity & Notes Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add ckanner/agent-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add ckanner/agent-skills --skill ui-automation
Manual install
git clone --depth 1 https://github.com/ckanner/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/ui-automation ~/.claude/skills/ui-automation

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# UI Automation (delegated to Codex)

## Overview

Dispatch a self-contained task to the external Codex agent when the work requires eyes on
a screen or hands on a GUI: browser automation, Chrome inspection, desktop application
operation, or visual verification. Codex supplies its own model plus its own browser-use
and computer-use plugins. This session supplies the task, the contract, and the review.

**The return channel is text only.** Screenshots, recordings, and produced files never
travel back through it — they must land on disk. The artifact contract below is what makes
them retrievable.

## When to Use This Skill

- Verifying a deployed or released UI against expected behaviour
- Checking whether a page renders correctly, or inspecting it via browser devtools
- Driving an application that has no usable CLI (a GUI tool, an editor, a 3D package)
- Any task whose success is established by *looking at something* rather than by reading output
- Any task where the artifact produced (render, export, recording) is the deliverable

Do **not** use this skill when the task is fully expressible as shell commands and file
reads in this workspace — do that work directly.

Do **not** use this skill to *write* automation code (test suites, Playwright or Cypress
specs, scraping scripts). That is an ordinary coding task. This skill is for dispatching
interface work to an external agent, not for producing automation source.

## Workflow

### Step 1 — Scope the run
Read the full skill on GitHub

Details

Skill name
ui-automation
Path
ui-automation/SKILL.md
License
Apache-2.0
Repo updated
3 October 2026

FAQ

What does the UI Automation skill do?

Use when a task needs a rendered interface observed, a browser driven, or a desktop application operated — post-deploy UI acceptance, checking whether a page renders as expected, driving software with no usable CLI, or capturing visual evidence — and should be executed by the external Codex agent rather than in this session. Not for writing automation code such as test suites or Playwright specs. Covers dispatching through `codex exec`, the artifact contract, and evidence recovery.

How do I install the UI Automation skill?

Claude Code plugin: /plugin marketplace add ckanner/agent-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is UI Automation popular?

It lives in ckanner/agent-skills, which has 24 GitHub stars and 5 forks, and is included in 1 curated skill list.

Related skills

Jta

24

ckanner/agent-skills

Translate JSON i18n files to multiple languages with AI-powered quality optimization. Use when user mentions translating JSON, i18n files, internationalization, locale files, or needs to convert language files to other languages.

Writing & ContentIn 1 list

Prompt Optimizer

24

ckanner/agent-skills

This skill should be used when users request help optimizing, improving, or refining their prompts or instructions for AI models. Use this skill when users provide vague, unclear, or poorly structured prompts and need assistance transforming them into clear, effective, and well-structured instructions that AI models can better understand and execute. This skill applies comprehensive prompt engineering best practices to enhance prompt quality, clarity, and effectiveness.

AI, LLMs & AgentsIn 1 list

Client Email Coach

48

harvard-lil/lawskills-hub

Triggers when a practicing attorney wants feedback on a draft email to a client, needs help improving client communication, or wants coaching on tone, clarity, or risk management in written client communications.

Productivity & Notes

Inkbox Slack Responder

44

inkbox-ai/hermes-agent-plugin

Use when responding to an Inkbox Slack source or using enabled Slack tools.

Productivity & Notes10

Ijfw Auto Memorize

43

FerroxLabs/wayland-core

Session-end auto-extraction of lessons, errors, fixes, and user feedback into structured memory. Fires at session end. Requires consent on first run.

Productivity & Notes17

Inkbox Notes Memory

44

inkbox-ai/hermes-agent-plugin

Use when the user asks to save, remember, list, retrieve, update, or delete notes in Inkbox. Hermes does not expose Inkbox note tools; explain the limitation or use host memory only if available outside this plugin.

Productivity & Notes10

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.