---
name: verify_auth_state_before_reporting_blocked
title: "Verify auth state before reporting blocked"
description: "Verify the live sign-in state of a service in the browser and the saved credential store before reporting it as login gated, expired or not connected, and run single-prompt discipline at verification gates."
version: 1.0.0
author: Script Master Labs LLC
license: MIT
source: https://scriptmasterlabs.com/hive402-skills/verify_auth_state_before_reporting_blocked/SKILL.md
registry: HIVE402 Skills (https://scriptmasterlabs.com/hive402-skills)
---

# Verify auth state before reporting blocked

## Probe the live session first

- Navigate to the actual service or dashboard in the live browser before reporting a service as login gated, signed out or session expired.

- Treat a search result, a text fetch or a missing credential as no evidence about session state. A signed in browser session can be alive while no password is stored anywhere.

- Report blocked only after the live navigation itself lands on a sign in page, an expired session notice or an access denial you can name.

## Check every auth source

- Check the saved credential store for the service before asking the user to sign in or paste a credential.

- Check for a browser session that the user established in an earlier sitting, including one created with a one time code sent to their email. That kind of session lives in browser cookies and has no password to look up.

- Name which source you checked and what it showed, so a missing password is never reported as a missing account or a dead session.

## Run one prompt at a time at verification gates

- Send exactly one verification prompt, read its number or code to the user, and wait for the user to confirm they are ready before any retry.

- Warn the user before resending that a resend kills the previous prompt and its number. Stacked prompts leave the user choosing between dead numbers.

- Stop after a failed or stacked attempt, have the user clear the old notifications, then start one clean attempt and stay with it to the end.

## Report what the probe proved

- State the destination the probe reached, such as a dashboard with its account name, and separate that from anything still unverified.

- When the session has genuinely expired, give the single reauth step the user alone can do, such as taking over the browser to request a fresh code, and keep doing every other part of the task yourself.

- Never carry a blocked report from an earlier attempt into a new report without a fresh probe in that attempt.

## Alternatives for better results

- Ask the user for a screenshot of the exact error when a sign in sheet or prompt fails, and read that error before prescribing a fix, because the failing layer is often the credential store or the prompt flow rather than the target service.

- Record a proven session route in memory once it works, naming where the session lives and how to reauth, so the next worker probes it instead of relearning it.


---

## From Script Master Labs

This skill is listed in [HIVE402 Skills](https://scriptmasterlabs.com/hive402-skills) —
every skill there passed a verification gate before listing: parsed, safety-scanned,
provenance recorded, self-contained. Skills, probed before listed.

Script Master Labs also runs [HIVE402](https://hive402.scriptmasterlabs.com), the
payability-probed catalog of 132 paid agent APIs, [OMNIGATE](https://scriptmasterlabs.com/omnigate-facilitator),
the x402 gateway those payments settle through, and the free
[x402 Starter Kit](https://scriptmasterlabs.com/x402-kit).