New: 98,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

Verify UI Change In Cloud

by Heartcoolman in Heartcoolman/warp-cn

Invoke this automatically after completing any user-facing client change, ONLY in non-sandboxed environments and local environments.

AGPL-3.0Auto-check passedProductivity & Automation

Install Verify UI Change In Cloud

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

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

GitHub CLI
$ gh skill install Heartcoolman/warp-cn 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/Heartcoolman/warp-cn.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
120
Token cost
~1.1k tokens
SKILL.md length
514 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Invoke this automatically after completing any user-facing client change, ONLY in non-sandboxed environments and local environments.

  • Works in 5 steps: Push Your Changes → Detect the Repository → Spawn the Cloud Agent → …
  • A cloud agent that runs the test-warp-ui skill
  • Calls git and cargo
  • Tasks that involve Desktop control

What it does

Verify UI Change In Cloud is an agent skill from Heartcoolman/warp-cn. Invoke this automatically after completing any user-facing client change, ONLY in non-sandboxed environments and local environments. Verifies changes by spawning a cloud agent with computer use to test Warp. Triggers a cloud agent that runs the test-warp-ui skill.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Desktop control. The repository describes itself as: Warp 客户端中文本地化与自定义改造（fork from warpdotdev/warp）. The licence is AGPL-3.0.

When your agent uses it

  • A cloud agent that runs the test-warp-ui skill
  • Tasks that involve Desktop control

Example prompts

  • “/verify-ui-change-in-cloud”

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 6d5df21. 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

Verify UI Change In Cloud loads about 1.1k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 514 words of instructions outside code blocks.

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

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 Heartcoolman/warp-cn at commit 6d5df21, republished under its AGPL-3.0 licence (© Heartcoolman). 514 words, ~1,082 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
Invoke this automatically after completing any user-facing client change, ONLY in non-sandboxed environments and local environments. Verifies changes by spawning a cloud agent with computer use to test Warp. Triggers a cloud agent that runs the test-warp-ui skill.
user-invocable
true

Verify UI Change in Cloud

After making a user-facing client change, use this workflow to verify it by spawning a cloud agent with computer use capabilities. 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.").

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.
Show full SKILL.md (184 more words)Show less
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.

© Heartcoolman, 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 Heartcoolman/warp-cn.

Open the folder on GitHubat commit 6d5df21

Compare with similar skills

Verify UI Change In Cloud 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.

Verify UI Change In Cloud compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify UI Change In Cloud this skillHeartcoolman/warp-cn120—~1.1kAutomated safety check: PassAGPL-3.0
Vision SkillsAnionex/agent-vision-toolkit1.2k—~4kAutomated safety check: PassMIT
Mac Computer UseTo3akaRin/mac-computer-use1.1k—~495Automated safety check: PassMIT
Crabbox Appsopenclaw/openclaw392k—~1.5kAutomated safety check: PassMIT
Agent Managementautonomous-ai/Physical-AI-Operating-System407—~1.7kAutomated safety check: PassApache-2.0
Computer Usebam-bam-2/solo-skills3671 repos~915Automated safety check: PassMIT

Similar skills

  • Vision Skills

    Anionex/agent-vision-toolkit

    Local vision CLIs: glance (describe/ask/OCR an image), ground (locate a target, pixel box), detect (element inventory), trace (image to SVG geometry), crop (cut a pixel box to a file), and…

    1.2k GitHub stars~4k tokensUpdated 2 days ago
    Productivity & AutomationAuto-check passed

  • Mac Computer Use

    To3akaRin/mac-computer-use

    操作 macOS 桌面应用，探测窗口和自动化接口、截图、读取或修改辅助功能元素、执行鼠标键盘动作，以及通过 CDP 操作内嵌 Chromium 页面。适用于桌面应用自动化与界面验收；普通网页任务优先使用已有浏览器工具。

    1.1k GitHub stars~495 tokensUpdated 16 days ago
    Productivity & AutomationAuto-check passed

  • Crabbox Apps

    openclaw/openclaw

    A skill your agent uses when asked to open, run, test, or show an app in Crabbox, including native desktops, web previews, and computer use on a temporary machine.

    392k GitHub stars~1.5k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Agent Management

    autonomous-ai/Physical-AI-Operating-System

    Legacy Autonomous Buddy control for explicitly requested Buddy coding sessions.

    407 GitHub stars~1.7k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Computer Use

    bam-bam-2/solo-skills

    Use Orca's computer-use CLI to inspect and operate local desktop app windows through accessibility trees, screenshots, and safe UI actions.

    367 GitHub starsUsed in 1 repo~915 tokens
    Productivity & AutomationAuto-check passed

  • Cloud Computer Use

    davidondrej/cloudroom-core

    See and control desktop apps on this Cloud sandbox’s virtual Linux screen with cloudroom computer-use: launch GUI apps you build or install, read their UI, click, type, and take screenshots.

    282 GitHub stars~881 tokensUpdated yesterday
    Productivity & AutomationAuto-check: notes

Categories

Questions about Verify UI Change In Cloud

What does Verify UI Change In Cloud do?

Invoke this automatically after completing any user-facing client change, ONLY in non-sandboxed environments and local environments. Verify UI Change In Cloud is an agent skill from Heartcoolman/warp-cn. Invoke this automatically after completing any user-facing client change, ONLY in non-sandboxed environments and local environments.

When should I use Verify UI Change In Cloud?

Verify UI Change In Cloud fits situations like: A cloud agent that runs the test-warp-ui skill; tasks that involve Desktop control.

How do I install Verify UI Change In Cloud in Claude Code?

Run `npx skills add Heartcoolman/warp-cn --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 Heartcoolman/warp-cn) 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 Verify UI Change In Cloud in Codex?

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

Can I use Verify UI Change In Cloud 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 Heartcoolman/warp-cn --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 Verify UI Change In Cloud need to run?

Going by SKILL.md and its folder, Verify UI Change In Cloud needs the command-line tools its instructions call (git and cargo).

Does Verify UI Change In Cloud 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 Verify UI Change In Cloud 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 Verify UI Change In Cloud use?

Verify UI Change In Cloud 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 Verify UI Change In Cloud use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 Verify UI Change In Cloud?

Skills that share tags, products or a category with Verify UI Change In Cloud: Vision Skills (Anionex/agent-vision-toolkit, 1.2k stars), Mac Computer Use (To3akaRin/mac-computer-use, 1.1k stars), Crabbox Apps (openclaw/openclaw, 392k stars) and Agent Management (autonomous-ai/Physical-AI-Operating-System, 407 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify UI Change In Cloud?

Heartcoolman (a GitHub user) maintains it in Heartcoolman/warp-cn, which has 120 GitHub stars. The repository was last updated on October 5, 2026.

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