Current skills

Email · available

Email gives a test a fresh, reachable inbox. It can support registration, account activation, email OTPs, magic-link sign-in, welcome messages, notifications, and password-reset journeys when the necessary account setup is available.

The inbox belongs to the test’s journey. This is not access to your personal or company mailbox, and it does not automatically provide an existing account in the application being tested.

Create a disposable inbox

Create a fresh email identity that the browser can enter into a registration or other email-based flow.

Wait for a matching email

Wait for a new message, optionally matching a sender or subject. Waiting is bounded; a missing or delayed message can prevent completion.

List and read messages

Inspect recent messages and sanitized message content, including sender, subject, body text, links, and attachment presence. Attachment presence is not the same as validating attachment contents.

Read an email OTP

Extract a one-time code from the selected email so a later browser step can enter it. If no usable code is found, the action cannot complete as planned.

Open a verification link

Open an HTTP or HTTPS verification or magic-login link from the selected message. The application’s resulting state still needs to be checked.

Example: verifying a new account

1. 01

   Prepare the inbox

   The skill creates a new email address for this test.

2. 02

   Submit the signup form

   Browser actions enter that address and the other required test data, then submit the form.

3. 03

   Receive the message

   Email waits for the relevant verification message and reads the selected result.

4. 04

   Continue in the browser

   The test enters the extracted code or opens the verification link, then checks the observed application response.

When Email is not needed

Checking that an email field is required, rejects malformed input, has a clear label, or displays an error can be done in the browser. Existing-user password login and duplicate-account validation do not inherently require a new inbox either.

What the current catalog does not provide

Social or enterprise identities

Email does not supply a Google, Microsoft, Apple, or enterprise SSO identity. A real SSO test needs the appropriate authorized identity and setup.

SMS, payment, or CAPTCHA services

The current enabled catalog does not include skills for receiving SMS, verifying payment settlement, or solving CAPTCHAs. Browser controls for these flows do not establish those external capabilities.

Guaranteed delivery or acceptance

An application may reject disposable addresses; delivery may be delayed; a code may expire; a message may not contain a usable link. Skill availability does not guarantee journey completion.

What you see in skill evidence

Skill details identify the skill, the action taken, and its displayed outputs. The skill output view hides private fields and masks designated sensitive values, such as OTPs. A displayed verification destination omits its query details.

These display rules are not a promise that every screenshot or recording is free of sensitive content. Use test data and review the full report before sharing it.