New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cloud UI Change Verification

by warpdotdev in warpdotdev/warp

Verifies a Warp client change by pushing it to a branch and spawning a cloud agent with computer use that follows the test-warp-ui skill, only when you ask for it.

AGPL-3.0Auto-check passedTesting & QA

Install Cloud UI Change Verification

skills CLI
$ npx skills add warpdotdev/warp --skill verify-ui-change-in-cloud -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install warpdotdev/warp verify-ui-change-in-cloud --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/channel-gated-skills/dogfood/verify-ui-change-in-cloud .claude/skills/verify-ui-change-in-cloud && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
verify-ui-change-in-cloud
GitHub stars
65k
Token cost
~1.2k tokens
SKILL.md length
555 words
Files
1
Skills in repo
46
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Verifies a Warp client change by pushing it to a branch and spawning a cloud agent with computer use that follows the test-warp-ui skill, only when you ask for it.

  • Works in 5 steps: Push Your Changes → Detect the Repository → Spawn the Cloud Agent → …
  • Having a cloud agent visually verify a Warp UI change after you push a branch
  • Calls git and cargo
  • Verifying startup, config or migration behavior changes in the running client

What it does

This is an opt-in workflow meant for local, non-sandboxed environments. After a user-facing change the agent may briefly offer it, but launches only after an explicit request or a yes, and it covers anything that changes what the user sees or experiences, such as startup behavior, config handling or migration flows, not just visual tweaks. The changes must first be pushed to a branch, since the cloud agent clones the repo into a fresh environment.

The agent checks the git remote to confirm the repo is the Warp one and stops with a warning otherwise. It then calls run_agents with a one-entry batch: a short summary, a base prompt that tells the cloud agent to read and follow the test-warp-ui skill, the Warp dev environment ID, computer use enabled, and a display name like verify-ui-change. The prompt should name the element or flow to test, any mocking or pre-seeded filesystem and app state, and the observations to report back.

When your agent uses it

  • Having a cloud agent visually verify a Warp UI change after you push a branch
  • Verifying startup, config or migration behavior changes in the running client
  • Delegating computer-use testing to a remote environment

Example prompts

  • “I pushed the branch with the new tab bar, so verify it in the cloud with computer use.”
  • “Yes, run the cloud verification you offered for the settings change.”
  • “Spawn a cloud agent to check that the migration flow shows the right dialog on first launch.”

Requirements

  • The run_agents tool with a remote Warp dev environment
  • Changes pushed to a branch
  • The bundled test-warp-ui skill

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Push Your Changes
  2. Detect the Repository
  3. Spawn the Cloud Agent
  4. Write an Effective Prompt
  5. Surface the Cloud Agent Link

What it can do on your machine

Read from SKILL.md and the folder at commit f571865. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cloud UI Change Verification loads about 1.2k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 555 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from warpdotdev/warp at commit f571865, republished under its AGPL-3.0 licence (© warpdotdev). 555 words, ~1,162 tokens.

Download SKILL.mdSave it as .claude/skills/verify-ui-change-in-cloud/SKILL.md (or your agent's skills folder).
name
verify-ui-change-in-cloud
description
Verifies user-facing Warp client changes by spawning a cloud agent with computer use to test Warp. Use only when the user explicitly requested computer-use verification or accepted an offer to run it, and ONLY in non-sandboxed environments and local environments. Triggers a cloud agent that runs the test-warp-ui skill.
user-invocable
true

Verify UI Change in Cloud

Use this workflow to verify a user-facing client change by spawning a cloud agent with computer use capabilities. Do not invoke it automatically after every UI change: launch only when the user explicitly requested computer-use verification or accepted an offer to run it. After completing a user-facing change, you may briefly offer this verification; do not launch until the user says yes. This applies to any change that affects what the user sees or experiences in the running app — not just visual/UI changes, but also startup behavior, config handling, migration flows, and other client-side logic.

Workflow

1. Push Your Changes

The cloud agent runs in a fresh environment that clones the repo. Your changes must be pushed to a branch so the cloud agent can access them.

2. Detect the Repository

Before spawning the cloud agent, detect which repository you are running in. Check the Git remote URL to determine the repo:

bash
git remote get-url origin

Verify the remote URL contains warpdotdev/warp. If it does not, warn the user that this skill only supports the warp repository and stop.

The environment ID for the warp Dev Environment is SVhg783GBFQHk1OfdPfFU9.

3. Spawn the Cloud Agent

Use the run_agents tool to spawn a remote cloud agent. A single-child batch (one entry in agent_run_configs) is valid.

  • summary: a brief declarative explanation, e.g. "Spawning a cloud agent with computer use to verify the UI change."
  • base_prompt: include an instruction to read and follow the test-warp-ui skill, followed by the verification task (see the next section)
  • remote.environment_id: SVhg783GBFQHk1OfdPfFU9
  • remote.computer_use_enabled: true
  • agent_run_configs: a single entry with name set to a short display name such as "verify-ui-change". The per-agent prompt can be empty since base_prompt covers the task.

The test-warp-ui skill is bundled, so the cloud agent has it automatically. Tell the agent to invoke it by name in the base_prompt (e.g. "Read and follow the test-warp-ui skill.").

Show full SKILL.md (243 more words)Show less
4. Write an Effective Prompt

The prompt should tell the cloud agent:

  • Which element, flow, or behavior to test
  • What hardcoding or mocking is needed (see below and the test-warp-ui skill for details on sandbox constraints)
  • What filesystem or app state to pre-seed before launching (e.g., creating directories, writing config files)
  • What specific observations to report back

Example prompts:

I changed the settings dialog header to use a larger font and blue color.
Hardcode the settings dialog to open on launch, then describe the header text,
font size relative to other text, and color.
I added a migration that symlinks config from ~/.warp into ~/.warp-preview on first launch.
The migration is gated on Channel::Preview. Before building, hardcode the migration to run
regardless of channel by removing the channel check. Also create a fake ~/.warp directory
with test files. After launching Warp, verify the symlinks were created in ~/.warp-preview.
Hardcoding to reach the code path under test

The cloud agent builds Warp with cargo run, which may not match the exact runtime conditions of your change (e.g., different channel, missing feature flags, absent preconditions). When this happens, instruct the cloud agent to temporarily hardcode the code so the build exercises the path you need to test. Common examples:

  • Gated code paths: If the change is behind a channel check, feature flag, or experiment, tell the agent to remove or bypass the gate before building.
  • Pre-existing state: If the change depends on filesystem state that wouldn't exist in a clean environment (e.g., a config directory from a prior install), tell the agent to create it before launching.
  • Startup behavior: If the change affects something that only happens on first launch or migration, make sure the agent sets up the preconditions that trigger it.

Be explicit in the prompt about what to hardcode and why — the cloud agent won't infer this on its own.

No extra surfacing step is needed — the Warp client displays the cloud agent run automatically.

© warpdotdev, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in resources/channel-gated-skills/dogfood/verify-ui-change-in-cloud of warpdotdev/warp.

Open the folder on GitHubat commit f571865

Compare with similar skills

Cloud UI Change Verification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cloud UI Change Verification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cloud UI Change Verification this skillwarpdotdev/warp65k—~1.2kAutomated safety check: PassAGPL-3.0
Evidence-Driven Testingmichaelshimeles/skills1.3k1 repos~3.9kAutomated safety check: PassNone
Parallels macOS VM Labsteipete/agent-scripts7.3k—~1.8kAutomated safety check: PassMIT
Electron App Screenshotkeybase/client9.3k—~476Automated safety check: PassBSD-3-Clause
Stevemikker/steve170—~421Automated safety check: PassNone
Diff-Driven Smoke TestsSkyvern-AI/skyvern23k—~5.2kAutomated safety check: PassAGPL-3.0

Similar skills

  • Evidence-Driven Testing

    michaelshimeles/skills

    Records an annotated screen recording of the agent testing an app hands-on, then posts the video and a results summary to the PR and tracker issue.

    1.3k GitHub starsUsed in 1 repo~3.9k tokens
    Testing & QAAuto-check passed

  • Parallels macOS VM Lab

    steipete/agent-scripts

    Uses a clean Parallels macOS VM to test GUI automation, TCC permission prompts and screenshot tools like Peekaboo, verifying results from outside the guest.

    7.3k GitHub stars~1.8k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Electron App Screenshot

    keybase/client

    Takes a screenshot of a running Electron desktop app through playwright-cli over remote debugging, shrinks it and shows it so you can check the UI visually.

    9.3k GitHub stars~476 tokensUpdated today
    Testing & QAAuto-check passed

  • Steve

    mikker/steve

    Use the steve CLI to automate macOS apps via Accessibility APIs.

    170 GitHub stars~421 tokensUpdated 6 mo ago
    Testing & QAAuto-check passed

  • Diff-Driven Smoke Tests

    Skyvern-AI/skyvern

    Reads your git diff, writes a handful of happy-path browser smoke tests, runs them with Skyvern or Chrome DevTools MCP and posts screenshot evidence to the PR.

    23k GitHub stars~5.2k tokensUpdated today
    Testing & QAAuto-check passed

  • Diff-Driven QA

    Skyvern-AI/skyvern

    Reads your git diff, decides whether the change needs browser QA, API checks or repo tests, runs that validation and reports pass or fail with evidence.

    23k GitHub stars~4.7k tokensUpdated today
    Testing & QAAuto-check: warnings

More from warpdotdev/warp

All 46 skills in this repo

  • Figma Design System Builder

    warpdotdev/warp

    Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Auto-check passed

  • Figma use_figma Plugin API Rules

    warpdotdev/warp

    Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Auto-check passed

  • Warp Factory Files

    warpdotdev/warp

    Authors and edits file-based Warp software factory definitions rooted at factory.yaml, covering agents, automations, scorers and webhooks, and validates them before a pull request.

    65k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Figma Design to Code

    warpdotdev/warp

    Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.

    65k GitHub starsUsed in 4 repos~2.9k tokens
    Auto-check passed

  • Warp GUI to Agent CLI Migration

    warpdotdev/warp

    Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.

    65k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed

  • Figma Design System Rules Generator

    warpdotdev/warp

    Creates project-specific design system rules from your codebase so coding agents implement Figma designs with your components, naming and tokens.

    65k GitHub starsUsed in 3 repos~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about Cloud UI Change Verification

What does Cloud UI Change Verification do?

Verifies a Warp client change by pushing it to a branch and spawning a cloud agent with computer use that follows the test-warp-ui skill, only when you ask for it. This is an opt-in workflow meant for local, non-sandboxed environments. After a user-facing change the agent may briefly offer it, but launches only after an explicit request or a yes, and it covers anything that changes what the user sees or experiences, such as startup behavior, config handling or migration flows, not just visual tweaks.

When should I use Cloud UI Change Verification?

Cloud UI Change Verification fits situations like: having a cloud agent visually verify a Warp UI change after you push a branch; verifying startup, config or migration behavior changes in the running client; delegating computer-use testing to a remote environment.

How do I install Cloud UI Change Verification in Claude Code?

Run `npx skills add warpdotdev/warp --skill verify-ui-change-in-cloud -a claude-code`. Or copy the skill folder (resources/channel-gated-skills/dogfood/verify-ui-change-in-cloud in warpdotdev/warp) into .claude/skills/verify-ui-change-in-cloud in your project. Claude Code loads it when a task matches its description.

How do I install Cloud UI Change Verification in Codex?

Run `npx skills add warpdotdev/warp --skill verify-ui-change-in-cloud -a codex`. Or copy the skill folder (resources/channel-gated-skills/dogfood/verify-ui-change-in-cloud in warpdotdev/warp) into .agents/skills/verify-ui-change-in-cloud in your project. Codex loads it when a task matches its description.

Can I use Cloud UI Change Verification in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add warpdotdev/warp --skill verify-ui-change-in-cloud -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-ui-change-in-cloud, .gemini/skills/verify-ui-change-in-cloud, .github/skills/verify-ui-change-in-cloud and .opencode/skills/verify-ui-change-in-cloud in your project.

What does Cloud UI Change Verification need to run?

Going by SKILL.md and its folder, Cloud UI Change Verification needs the command-line tools its instructions call (git and cargo). Our summary lists: The run_agents tool with a remote Warp dev environment; Changes pushed to a branch; The bundled test-warp-ui skill.

Does Cloud UI Change Verification access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Cloud UI Change Verification safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cloud UI Change Verification use?

Cloud UI Change Verification is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cloud UI Change Verification use?

About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cloud UI Change Verification?

Skills that share tags, products or a category with Cloud UI Change Verification: Evidence-Driven Testing (michaelshimeles/skills, 1.3k stars), Parallels macOS VM Lab (steipete/agent-scripts, 7.3k stars), Electron App Screenshot (keybase/client, 9.3k stars) and Steve (mikker/steve, 170 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cloud UI Change Verification?

warpdotdev (a GitHub organization) maintains it in warpdotdev/warp, which has 65,380 GitHub stars. The repository holds 46 skills in this directory. The repository was last updated on October 7, 2026.

Source: warpdotdev/warp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.