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

Warp UI Testing with Computer Use

by warpdotdev in warpdotdev/warp

Guides visual testing of Warp UI changes by launching the app with an API key and driving it through the computer use tool, with optional mocked state.

AGPL-3.0Auto-check passedTesting & QA

Install Warp UI Testing with Computer Use

skills CLI
$ npx skills add warpdotdev/warp --skill test-warp-ui -a claude-code

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

GitHub CLI
$ gh skill install warpdotdev/warp test-warp-ui --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/test-warp-ui .claude/skills/test-warp-ui && 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
test-warp-ui
GitHub stars
65k
Used in
1 other repo
Token cost
~1k tokens
SKILL.md length
533 words
Files
1
Skills in repo
46
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Guides visual testing of Warp UI changes by launching the app with an API key and driving it through the computer use tool, with optional mocked state.

  • Works in 3 steps: Hardcode or Mock Data (When Needed) → Invoke Computer Use → Verify Results
  • Checking visually that a Warp UI change looks and behaves as intended
  • SKILL.md covers Running Warp, Testing Workflow and Tips
  • Calls cargo; needs STAGING_USER_WARP_API_KEY and WARP_API_KEY

What it does

Used only when computer-use testing has been requested and the computer_use tool is available. The agent launches Warp from the repository root with cargo run --bin warp, which builds the internal dogfood channel, the only channel that honors the --api-key flag for the GUI app. A key already in WARP_API_KEY is picked up automatically, while one in STAGING_USER_WARP_API_KEY has to be passed explicitly.

Before testing, the launch is checked: Warp should open straight to the terminal rather than the sign-in screen, and the build output must not say the key was provided but ignored, which signals the wrong binary was launched. The testing workflow then suggests hardcoding or mocking data when a UI state is hard to reach, such as conditional UI, unreleased feature flags or error states, while keeping such changes minimal, before invoking computer use. First builds can take several minutes.

When your agent uses it

  • Checking visually that a Warp UI change looks and behaves as intended
  • Launching an authenticated dogfood Warp build for testing
  • Reaching a hard-to-trigger UI state by mocking data or enabling a flag

Example prompts

  • “Test the new settings page in Warp with computer use and report what you see.”
  • “Launch Warp with my staging API key and confirm it opens authenticated.”
  • “Mock an error response so we can check how the failure banner looks in the running app.”

Requirements

  • The computer_use tool
  • Rust and cargo to build Warp
  • A Warp API key in WARP_API_KEY or STAGING_USER_WARP_API_KEY

Workflow steps

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

  1. Hardcode or Mock Data (When Needed)
  2. Invoke Computer Use
  3. Verify Results

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:

    • cargo

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

  • Network

    No URLs in SKILL.md.

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • STAGING_USER_WARP_API_KEY
    • WARP_API_KEY

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

Context cost

Warp UI Testing with Computer Use loads about 1k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 533 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~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 warpdotdev/warp at commit f571865, republished under its AGPL-3.0 licence (© warpdotdev). 533 words, ~1,012 tokens.

Download SKILL.mdSave it as .claude/skills/test-warp-ui/SKILL.md (or your agent's skills folder).
name
test-warp-ui
description
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computer_use tool is available to the agent. Covers launching Warp and verifying UI behavior.
user-invocable
false

Computer Use for Warp UI Testing

Use the computer_use tool to visually test that Warp looks and behaves as intended after UI changes, when computer-use testing was requested.

Running Warp

Launch Warp from the repository root. The exact command depends on which environment variable holds the API key:

  • If WARP_API_KEY is already set, omit the flag entirely — the --api-key flag is bound to WARP_API_KEY, so Warp reads it automatically:

    bash
    cargo run --bin warp

  • If the key is in STAGING_USER_WARP_API_KEY instead, pass it explicitly via the flag:

    bash
    cargo run --bin warp -- --api-key $STAGING_USER_WARP_API_KEY

Always pass --bin warp explicitly. That target builds the internal (dogfood) channel, which is the only channel that honors --api-key for the GUI app. A plain cargo run builds the OSS channel, which ignores the key and falls back to interactive onboarding.

Authenticating this way starts the app directly without interactive login prompts.

Initial builds may take several minutes; subsequent incremental builds are faster.

Verify the launch is authenticated

After launching, confirm both of the following before testing:

  • Warp is authenticated — it opens straight to the terminal, NOT the logged-out onboarding/sign-in screen.
  • The cargo run stderr/terminal output does not contain the substring provided but IGNORED.

If that warning appears (or the app is logged out), the wrong binary/channel was launched — stop and relaunch with cargo run --bin warp.

Testing Workflow

1. Hardcode or Mock Data (When Needed)

If you just need to verify that a specific UI looks correct, it can be useful to hardcode or mock data so the UI state is immediately reachable without navigating a full flow. This is optional — skip this step when testing end-to-end flows that should work naturally.

Examples of when to hardcode:

  • Conditional UI: The feature only appears under certain conditions (e.g., a specific setting, a non-empty data set, an active subscription) — hardcode the condition so the UI always appears.
  • Feature flags: The feature is behind a flag that isn't enabled yet — enable it directly.
  • Error states: You want to test error handling UI — hardcode error responses or failure conditions.

Keep mocked changes minimal and focused — only change what's necessary to reach the UI state under test.

Show full SKILL.md (187 more words)Show less
2. Invoke Computer Use

Call the computer_use tool with a task description that includes:

  • The command to build and launch Warp from the repo root: cargo run --bin warp when WARP_API_KEY is set in the environment, or cargo run --bin warp -- --api-key $STAGING_USER_WARP_API_KEY when the key is in STAGING_USER_WARP_API_KEY instead
  • Step-by-step instructions for navigating to the UI being tested
  • Specific observations to report: describe exactly what elements, text, colors, layout, or states the tool should observe and describe back
  • Do not include expected values in the task — the tool should report what it sees, not judge correctness
3. Verify Results

Compare the observations returned by computer_use against your expectations. If the UI doesn't match, investigate and adjust the code or mocks accordingly.

Tips

  • Be specific in task descriptions: Instead of "check if the dialog looks right," say "open Settings, click the General tab, and describe the text and layout of the first section."
  • Test one thing at a time: Focused tests are easier to debug when observations don't match expectations.
  • Build before invoking: Always confirm the build succeeds before calling computer_use. The tool cannot fix build errors.

© 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/test-warp-ui of warpdotdev/warp.

Open the folder on GitHubat commit f571865

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in warpdotdev/warp, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Warp UI Testing with Computer Use 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.

Warp UI Testing with Computer Use compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Warp UI Testing with Computer Use this skillwarpdotdev/warp65k1 repos~1kAutomated 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
Codex Coding Pluginstyler-ai/ProjectAtlas438—~1.8kAutomated safety check: PassMIT

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

  • Codex Coding Plugin

    styler-ai/ProjectAtlas

    Build, review, or fix ProjectAtlas plugin/runtime installer integration for Codex, Claude Code, and OpenCode, especially version convergence, stale ProjectAtlas cache repair, MCP config generation…

    438 GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed

  • Run Shunt

    pleaseai/shunt

    Build, launch, and drive shunt — the Claude Code LLM gateway (a Rust/axum Anthropic-Messages proxy).

    251 GitHub stars~2.6k tokensUpdated today
    Testing & QAAuto-check passed

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 Warp UI Testing with Computer Use

What does Warp UI Testing with Computer Use do?

Guides visual testing of Warp UI changes by launching the app with an API key and driving it through the computer use tool, with optional mocked state. Used only when computer-use testing has been requested and the computer_use tool is available. The agent launches Warp from the repository root with cargo run --bin warp, which builds the internal dogfood channel, the only channel that honors the --api-key flag for the GUI app.

When should I use Warp UI Testing with Computer Use?

Warp UI Testing with Computer Use fits situations like: checking visually that a Warp UI change looks and behaves as intended; launching an authenticated dogfood Warp build for testing; reaching a hard-to-trigger UI state by mocking data or enabling a flag.

How do I install Warp UI Testing with Computer Use in Claude Code?

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

How do I install Warp UI Testing with Computer Use in Codex?

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

Can I use Warp UI Testing with Computer Use 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 test-warp-ui -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-warp-ui, .gemini/skills/test-warp-ui, .github/skills/test-warp-ui and .opencode/skills/test-warp-ui in your project.

What does Warp UI Testing with Computer Use need to run?

Going by SKILL.md and its folder, Warp UI Testing with Computer Use needs the command-line tools its instructions call (cargo) and credentials named STAGING_USER_WARP_API_KEY and WARP_API_KEY. Our summary lists: The computer_use tool; Rust and cargo to build Warp; A Warp API key in WARP_API_KEY or STAGING_USER_WARP_API_KEY.

Does Warp UI Testing with Computer Use access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Warp UI Testing with Computer Use 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 Warp UI Testing with Computer Use use?

Warp UI Testing with Computer Use 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 Warp UI Testing with Computer Use use?

About 1k tokens (SKILL.md is roughly 4k 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 Warp UI Testing with Computer Use?

Skills that share tags, products or a category with Warp UI Testing with Computer Use: 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 Warp UI Testing with Computer Use?

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.