Add onboarding verification skill

[zachlloyd]

Description

Adds .agents/skills/onboarding-verification-skill, a local skill for orchestrating Linux stable Warp first-time onboarding verification in cloud agents.

The skill launches two parallel computer-use cloud agents:

• logged-out flow: installs stable Warp and verifies the account-free terminal-only onboarding path
• logged-in flow: installs stable Warp, authenticates with ONBOARDING_AGENT_FTUE_REFRESH_TOKEN, verifies authenticated onboarding, runs a terminal command, then opens the avatar/settings path and captures a screenshot showing the logged-in account email

It also documents safe secret handling for authenticated testing, including normalizing a raw refresh token or desktop redirect URL without printing token contents.

https://www.loom.com/share/2660d3b09f7d45429fb5aa8568d97c08
https://www.loom.com/share/b182f96638f74d5ebc9206e7e508f7d1

Linked Issue

• The linked issue is labeled ready-to-spec or ready-to-implement.
• Where appropriate, screenshots or a short video of the implementation are included below (especially for user-visible or UI changes).

Testing

• Validated SKILL.md frontmatter and required content with a Python check.

• Ran the updated skill with two parallel cloud agents using stable Linux Warp.

• Logged-out run succeeded: reached a usable terminal and ran echo warp-onboarding-logged-out-ready.

• Logged-in run succeeded: authenticated via the managed secret, reached a usable terminal, ran echo warp-onboarding-logged-in-ready, and captured the avatar/settings email screenshot.

• Logged-in artifacts:

  • Manifest artifact: 019e3796-3a9c-7846-9bbd-c637ed0b572a
  • Archive artifact: 019e3796-7966-746b-b453-93bd4976c806

• I have manually tested my changes locally with ./script/run

Screenshots / Videos

The logged-in run captured screenshots through onboarding and the post-login settings email step. The sanitized archive artifact is 019e3796-7966-746b-b453-93bd4976c806.

Agent Mode

• Warp Agent Mode - This PR was created via Warp's AI Agent Mode

CHANGELOG-NONE

Co-Authored-By: Oz oz-agent@warp.dev

[oz-for-oss]

@zachlloyd

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

Overview

This PR adds a new local skill for orchestrating logged-out and logged-in Linux Warp onboarding verification through cloud agents.

Concerns

• The authenticated redirect URL construction should require URL-encoding of secret-derived query values before they are embedded in warp://auth/desktop_redirect.
• The authenticated flow should not allow routing the secret-bearing redirect URL through a desktop URI handler in a way that places the token in process arguments or shell history.

Security

• The current URI-handler guidance can cause the refresh token to appear in process listings or shell history if the child agent uses a command such as xdg-open <warp-url>.

Verdict

Found: 0 critical, 2 important, 0 suggestions

Request changes

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

⚠️ [IMPORTANT] [SECURITY] Require URL-encoding for both the normalized refresh token and current state before building this query string; otherwise reserved characters can corrupt the redirect URL or be interpreted as extra parameters.

[oz-for-oss]

⚠️ [IMPORTANT] [SECURITY] Routing the full warp:// URL through a desktop URI handler can leak the refresh token if implemented with command-line arguments; restrict this to paste/clipboard or another mechanism that never puts the URL in shell history or process lists.

[zachlloyd]

Updated .agents/skills/onboarding-verification-skill/SKILL.md to address the auth-token handling review feedback:

• Require URL-encoding the normalized refresh token and current-run state separately before constructing the warp://auth/desktop_redirect URL.
• Treat token-bearing redirect URLs as secret material even after URL-encoding.
• Restrict the authenticated flow to Warp's pasted auth redirect/token input, and explicitly forbid routing the URL through desktop URI handlers, browser address bars, shell commands, process arguments, logs, artifacts, or reports.
• Clarify that the managed secret should authenticate as a dedicated non-employee, non-warp.dev FTUE test user.

No token value is included in the repo or PR comment.

[captainsafia]

Seems good overall! Left a note around cueing the agent to use the "Paste Auth Token" flow for login to avoid it having to parse the redirect URI itself.