gui-onboarding-verification-skill

Orchestrates parallel cloud agents to screenshot and verify Warp's Linux first-time onboarding flows.

64.7k|5.5k|Updated Jul 8, 2021
One-click install
npx skills add https://github.com/warpdotdev/warp --skill gui-onboarding-verification-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gui-onboarding-verification-skill
Source: https://github.com/warpdotdev/warp/tree/main/.agents/skills/gui-onboarding-verification-skill
Command: npx skills add https://github.com/warpdotdev/warp --skill gui-onboarding-verification-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually verifying Warp's first-time install and onboarding experience across logged-out and logged-in paths on Linux is slow and easy to miss visual defects or alternate branches. This Skill automates that verification by launching parallel Oz cloud agents with computer use to walk through onboarding, capture screenshots, and report UI quality issues.

Core Features & Use Cases

  • Parallel baseline exploration: Launches two cloud agents simultaneously, one covering the login-free flow and one covering the authenticated flow using the managed ONBOARDING_AGENT_FTUE_REFRESH_TOKEN secret.
  • Branch coverage fan-out: Baseline explorers propose distinct onboarding branches, and the parent orchestrator deduplicates and launches up to four targeted follow-up agents for high-value alternate paths.
  • Structured screenshot evidence: Every step is captured with sequential screenshots, a manifest, and issue-focused captures for misalignment, truncation, broken loading states, or auth failures.
  • Use Case: Before a Warp release, ask the agent to verify the Linux onboarding experience; it installs the latest stable package, walks both auth states, screenshots every screen, and returns a consolidated report of visual defects and unexplored branches.

Quick Start

Ask the agent to test and screenshot the Warp first-time install and onboarding experience on Linux in both logged-out and logged-in states.

Frequently Asked Questions about gui-onboarding-verification-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test Warp's first-time onboarding flow on Linux?

Ask the agent to verify the Warp onboarding experience; it launches two parallel Oz cloud agents with computer use that install the latest stable Linux package, walk through logged-out and logged-in onboarding, and screenshot every step until a usable terminal session.

How does the logged-in onboarding flow authenticate?

The logged-in child uses the managed secret ONBOARDING_AGENT_FTUE_REFRESH_TOKEN, normalizes it into a current-run redirect URL, and submits it through Warp's Paste Auth Token UI. The token is never printed, logged, or included in artifacts.

Does this skill work for the Warp TUI front-end?

No, it applies only to Warp's GUI desktop front-end built on the WarpUI pixel framework. For the headless TUI front-end, use the tui-ui-guidelines, tui-testing, and tui-verify-change skills instead.

What Linux distributions and packages are supported?

The skill maps official stable Warp downloads by distro and CPU architecture: deb and rpm packages for amd64 and arm64, pacman for Arch, with AppImage as a fallback when native packages cannot be installed.

What happens if the auth token is missing or invalid?

The authenticated child treats a missing, expired, or rejected ONBOARDING_AGENT_FTUE_REFRESH_TOKEN as a blocker, captures a screenshot of the failing screen, and reports the non-sensitive error without exposing any token contents.

How many follow-up agents does the verification launch?

By default at most four follow-up agents are launched, and only for concrete branch points observed by the baseline explorers. If no meaningful branches are found, coverage stops after the baseline pass and that is reported.