Skillv1.0.0

ClawScan security

flipkart seller dashboard · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousFeb 27, 2026, 7:25 PM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill's Flipkart integration aligns with its description, but several operational pieces are missing or inconsistent (WhatsApp delivery and optional Amazon support lack required credentials/config), so the package is incomplete and potentially misleading.
Guidance: This skill generally looks like what it claims for Flipkart, but it's incomplete and therefore risky to install as-is. Before installing ask the developer to: (1) declare and document the WhatsApp/message-provider credentials (e.g., Twilio/WhatsApp Business API keys) and how messages are sent; (2) declare all Amazon SP-API credentials required (LWA client id/secret, refresh token, role ARN etc.) if Amazon integration is offered; (3) explain how cron scheduling and persistent storage (tracked competitor list, restock alerts, token cache) are implemented by the host or skill (so data isn't lost or unintentionally exposed); (4) provide details on what exact Flipkart API scopes the FLIPKART_APP_ID/SECRET require and recommend least-privilege credentials. If the developer cannot provide those details, treat the skill as unfinished and avoid granting any production credentials or enabling autonomous invocation that would allow it to send messages or change prices.

Review Dimensions

Purpose & Capability: noteThe declared purpose (Flipkart seller dashboard) matches the required Flipkart credentials (FLIPKART_APP_ID, FLIPKART_APP_SECRET). However, the README promises WhatsApp delivery and an optional Amazon India extension — those capabilities would legitimately require additional credentials and setup that are not declared.
Instruction Scope: concernSKILL.md instructs the agent to send daily WhatsApp summaries, run cron-style daily/bi-hourly checks, and optionally connect to Amazon SP-API. The instructions reference env AMAZON_SP_API_REFRESH_TOKEN (for Amazon) and external message delivery to WhatsApp, but provide no details on which WhatsApp API/provider to use or what credentials are required. It also assumes persistent 'memory' for tracked items but offers no persistence mechanism or guidance for storing tokens, which is scope creep and operationally incomplete.
Install Mechanism: okInstruction-only skill with no install spec or code files; this is low-risk from an install perspective because nothing is written to disk. However, the lack of code means runtime behavior is entirely driven by the SKILL.md, so missing operational details matter more.
Credentials: concernOnly FLIPKART_APP_ID and FLIPKART_APP_SECRET are declared — appropriate for the Flipkart API. But SKILL.md references AMAZON_SP_API_REFRESH_TOKEN (not declared) and requires sending WhatsApp messages (no WhatsApp/Twilio/Meta credentials declared). Either the skill is incomplete or it expects platform-level integrations that are not stated; both are concerning because external message-sending needs explicit credentials and user consent.
Persistence & Privilege: noteThe skill does not request permanent 'always' presence and does not modify other skills. It expects to keep tracking data 'in memory' and to run scheduled jobs (cron). Because it's instruction-only, it's unclear how scheduled invocation or persistent state is provided by the host; autonomous invocation (allowed by default) combined with outbound messaging capability could increase blast radius if credentials are misconfigured, but there's no explicit privileged flag set.