noon-shared

Noon — Shared (login, navigation, common patterns)

This skill covers what every noon Seller Center task needs: authentication, the page-structure URL map, My Catalog read access, and shared UI patterns (modals, button clicks). Operation-specific skills (noon-listing, noon-fbn, noon-exports, noon-ads) load this first.

1. Login — Auto-fetch OTP When Email Is Bound

Noon uses email OTP only (no password). Before doing ANYTHING, decide how the OTP will be retrieved — do NOT bother the user if an email MCP integration can do it for you.

Decision flow (follow in order, do NOT skip steps)

1. Open the login page and look at the email it's about to send OTP to:

   browser-use open "https://login.noon.partners/en/"
   sleep 3 && browser-use state      # find the email on the "We've sent..."
                                     # screen OR the prefilled channelIdentifier
   

   Ziniao often auto-fills or remembers a session. The page shows Log in with OTP sent to <email>.

2. Check whether the task prompt includes a "## Email System" section (the runner injects it when the store has connected email accounts). Compare the bound emails to the Noon login email shown on screen:

   • Match → fetch the OTP yourself via email MCP (Case A).
   • No email system section, OR emails do not match → ask the user (Case B). Never guess — mismatched emails mean a different inbox.

Case A — Auto-fetch OTP via email MCP (preferred)

This works when the bound email address equals the Noon login email. One round trip, no user prompt:

# 1. Trigger immediate IMAP poll (don't wait 5 min for auto-sync):
vibe_seller_sync_email_now(account_email='<bound-email>')

# 2. Get the per-account DB path:
vibe_seller_email_info(store_id='<store-id>')
# Returns: { accounts: [{ email, db_path, ... }] }

Then read the latest Noon OTP email. The body is HTML — the 6-digit code sits on its own line inside a styled <div>. Extract it with a regex on body_html (not body_text, which has escaped markup):