flipkart seller dashboard
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill is mostly coherent for a seller dashboard, but it asks for marketplace account access and includes recurring monitoring plus account-changing commands that need careful review.
Install only if you are comfortable granting seller API access and enabling recurring marketplace monitoring. Before use, require confirmations for price and order changes, restrict API credentials to the minimum needed scopes, verify WhatsApp recipients, and ensure scheduled jobs and stored memory can be reviewed and disabled.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A mistaken or misinterpreted command could change marketplace prices or cancel customer orders, directly affecting revenue and operations.
The skill can perform high-impact seller-account mutations. Order cancellation has a stated confirmation prompt, but price changes are presented as a direct command without visible confirmation, limits, or review safeguards.
"update price [SKU] to ₹[AMOUNT]" — Change listing price via API ... "cancel order [ORDER_ID]" — Cancel an order (with confirmation prompt)
Require explicit confirmation for every write action, add price-change thresholds, show before/after values, keep an audit log, and make order cancellation and price updates opt-in only.
The agent may be able to read seller orders, listings, returns, inventory, and other business data, and may act through the seller API where permitted.
The skill needs real marketplace credentials to access seller account data, and optionally Amazon SP-API credentials. This is purpose-aligned, but it grants sensitive account authority.
Auth: OAuth2 — use `FLIPKART_APP_ID` and `FLIPKART_APP_SECRET` to get access token ... If env `AMAZON_SP_API_REFRESH_TOKEN` is set, also connect to Amazon Selling Partner API
Use least-privileged API applications, avoid sharing broad production credentials, rotate/revoke tokens when no longer needed, and verify which Amazon/Flipkart scopes are granted.
If scheduled, the skill may keep accessing seller data and sending messages until the schedule or memory state is disabled.
The skill describes recurring scheduled behavior. It is disclosed and aligned with the dashboard purpose, but it can continue polling accounts and sending alerts after setup.
Daily Morning Report (8:00 AM IST via cron) ... Check Buy Box status on key listings every 2 hours ... Follow up daily until stock is replenished
Make schedules explicit and user-approved, provide a simple pause/disable path, and document where scheduled state is stored.
Stored competitor, stock, and pricing data could affect future recommendations or alerts if it is outdated or incorrect.
The skill stores operational seller information in persistent memory for later comparisons and reminders. This is purpose-aligned, but memory can become stale or influence later decisions.
Store a competitor tracking list in memory: `TRACK_PRICE|{YOUR_LISTING_ID}|{COMPETITOR_FLIPKART_URL}|{LAST_KNOWN_PRICE}` ... Store in memory: `RESTOCK_ALERT|{SKU}|{STOCK_LEVEL}|{DATE}`Review and clear stored memory periodically, avoid storing secrets, and confirm important actions against live marketplace data before changing prices or inventory-related settings.
Order counts, revenue, return details, and inventory alerts could be sent to the wrong chat or exposed through a third-party messaging channel if configured incorrectly.
The skill intends to send business metrics to WhatsApp. That is disclosed and purpose-aligned, but the artifact does not define recipient binding, WhatsApp credentials, or delivery safeguards.
sends WhatsApp morning summaries ... Format for WhatsApp: ... Orders: 18 (₹42,500 GMV) ... New returns: 2 ... Inventory Alerts
Confirm the WhatsApp recipient before enabling delivery, avoid including unnecessary sensitive details, and require approval before sending reports outside the local agent environment.