Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
icosmos
v0.0.1Shopify 店铺运营/诊断技能：从 Supabase 拉取店铺域名与 token，做装修/产品/结账/指标异常检测，并支持发布引流博文（唯一写操作）。
⭐ 0· 138·0 current·0 all-time
by王新勇(Tacey Wong)@taceywong
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The description says it pulls shop domains and tokens from Supabase and runs Shopify diagnostics (mostly read-only, with an optional blog publish). That purpose would legitimately require access to Supabase and Shopify credentials. However, the registry metadata declares no required env vars, no primary credential, and no required binaries — a mismatch with the SKILL.md which references ICOSMOS_USER_EMAIL / ICOSMOS_USER_PASSWORD, SHOPIFY_API_VERSION, and an on-disk 'icosmos-shopify' CLI. The lack of declared Supabase access parameters (URL, key) is also inconsistent with claimed behavior.
Instruction Scope
SKILL.md instructs the agent to run a local CLI (./icosmos-shopify) and to 'sync stores & tokens to local cache' using ICOSMOS_USER_EMAIL and ICOSMOS_USER_PASSWORD. It references reading Shopify data, suppressing sensitive fields, and a write action (blog publish) gated by --confirm. The instructions reference accessing and caching sensitive tokens and require env vars not declared elsewhere. There are no instructions about where Supabase credentials come from, how cached tokens are stored/encrypted, or what exact network endpoints are used — leaving wide discretion and potential for secret exposure.
Install Mechanism
There is no install spec and no code files in the package, yet the runtime instructions require a local binary named icosmos-shopify to exist in the current directory. That is incoherent: either the binary must be provided by the publisher (but it's not included) or the instructions assume an out-of-band install step (not documented). Lack of a documented, trusted install source for executable code is a notable risk.
Credentials
The SKILL.md requires ICOSMOS_USER_EMAIL and ICOSMOS_USER_PASSWORD to be saved as system environment variables and references Shopify tokens and Supabase-hosted tokens. The published metadata lists no required env vars or primary credentials. Requesting persistent system env storage of credentials and syncing tokens into a local cache is a high-impact capability and should be explicitly declared and justified. There is no mention of Supabase URL/service key or least-privilege Shopify token scopes.
Persistence & Privilege
The skill will persistively sync Shopify tokens into a local cache per the instructions and asks users to save credentials to system env. While always:false and normal autonomous-invocation defaults are set, the combination of undisclosed persistence of tokens and undisclosed binary source increases risk. There is no documentation of where the cache resides, its permissions, or encryption, nor any provenance for the executable that will perform those writes.
What to consider before installing
Do not install or run this skill until the publisher answers basic provenance and security questions. Specifically ask: (1) Where does the icosmos-shopify binary come from? Provide a verified download or source repo and an install spec. (2) How does setup authenticate to Supabase — what URL and service key are required, and why are those not declared? (3) Exactly which environment variables (names and purposes) are required and why must ICOSMOS_USER_EMAIL / ICOSMOS_USER_PASSWORD be stored as system env vars? (4) Where and how are synced Shopify tokens cached on disk? Are they encrypted and access-controlled? (5) What Shopify token scopes are required and can least-privilege tokens be used? Until you get clear answers and a verifiable install/source (or can run the binary in a safe, isolated environment and inspect it), treat this skill as untrusted. If you must test it, run it in an isolated VM or container, avoid placing long-lived secrets in global env vars, and prefer short-lived or scoped credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk97c017ng6mqdwpb9fhdm8rw4h833te4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.