noon-shared

Automate Noon Seller Center authentication, navigation, and shared UI interactions.

40|8|Updated May 14, 2026
One-click install
npx skills add https://github.com/zpoint/vibe-seller --skill noon-shared
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: noon-shared
Source: https://github.com/zpoint/vibe-seller/tree/main/app/skills_v2/noon-shared
Command: npx skills add https://github.com/zpoint/vibe-seller --skill noon-shared

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-border sellers using the Noon e-commerce platform often have to repeatedly implement the same foundational Seller Center operations like login, navigation, and handling common UI elements for every individual automation task, leading to redundant work and inconsistent behavior across different Noon-related workflows.

Core Features & Use Cases

  • Unified Noon Authentication: Handles OTP retrieval via bound email integration or user prompt, plus automatic project ID discovery from post-login URLs, eliminating repeated login setup for every Noon task.
  • Pre-built Page Navigation Map: Provides direct, reliable URLs for all core Noon Seller Center pages including catalog management, FBN inventory, sales reports, and ad manager, skipping slow and error-prone manual sidebar navigation.
  • Reusable UI Interaction Patterns: Covers common modals, off-screen button clicks, and cross-origin iframe interactions that appear across all Noon seller workflows, ensuring consistent and reliable browser automation behavior. Use case: A seller managing multiple Noon stores for different regional markets can use this shared skill as a base for all Noon-specific tasks, avoiding duplicate work for login and navigation every time they run a listing update, inventory check, or ad tuning task.

Quick Start

Use the noon-shared skill to log in to your Noon Seller Center account, retrieve your store's project ID, and navigate directly to the My Catalog page to view all your active product listings.

Frequently Asked Questions about noon-shared

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

FAQPage Schema
How do I automate Noon Seller Center login with OTP retrieval for browser automation?

Noon Seller Center login automation handles OTP retrieval via bound email integration or user prompts, plus automatic project ID discovery from post-login URLs. This eliminates repeated manual authentication setup for every individual Noon task.

What is the best way to navigate directly to Noon Seller Center pages without manual sidebar clicks?

Direct URL navigation maps for Noon Seller Center provide reliable links to catalog management, FBN inventory, sales reports, and ad manager pages. This skips slow manual sidebar navigation and reduces error-prone clicks during browser automation.

How do I handle cross-origin iframes and off-screen buttons when automating Noon e-commerce tasks?

Reusable UI interaction patterns cover common modals, off-screen button clicks, and cross-origin iframe interactions across Noon seller workflows. These shared patterns ensure consistent browser automation behavior for all Noon tasks.

Can I use Noon Seller Center automation for cross-border selling across multiple regional stores?

Cross-border sellers managing multiple Noon stores for different regional markets can use this shared skill as a base. It avoids duplicate login and navigation work for listing updates, inventory checks, or ad tuning tasks.

Why does my Noon Seller Center automation fail when handling shared modals and button click patterns?

Inconsistent handling of shared modals and button click patterns causes failures across Noon seller workflows. Reusable UI interaction patterns provide reliable browser automation behavior to eliminate redundant implementation and fix these issues.

Do I need to set up email integration to automate OTP login for Noon Seller Center tasks?

OTP login for Noon Seller Center supports both bound email integration for automatic OTP retrieval and manual user prompts. Email integration enables fully automated authentication, while prompts work without email setup.