Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
polymarket-predictradar-whale-alert-skills
v1.0.0Polymarket Whale Alert — real-time large order monitoring. Queries the past 24 hours of smart money (HUMAN/MM/SIGNAL) large orders. Trigger words: whale, wha...
⭐ 0· 28·0 current·0 all-time
byYeri@cnica
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The SKILL.md describes exactly the expected functionality (query past-24h large trades, filter by smart-money labels, enrich with market metadata). The required actions (SQL queries, classification lookup, URL construction) are coherent with the stated purpose.
Instruction Scope
Instructions are prescriptive and scoped to fetching trade rows, filtering by smart-money profiles, and producing structured output. They explicitly instruct running SQL via the MCP client and using the smart-money and gamma clients. This is within scope, but the skill instructs the agent to run direct SQL queries against internal analytics tables and to display full wallet addresses — acceptable for this task but sensitive and worthy of review.
Install Mechanism
There is no install spec and no code files (instruction-only), so nothing is written to disk by the skill itself. This is lower risk, but the skill expects shared modules to be available at ../../polymarket-data-layer — a runtime dependency that's not declared in the registry metadata.
Credentials
The skill declares no required environment variables or credentials, yet it relies on a shared 'polymarket-data-layer' that the SKILL.md says performs an MCP session handshake. Where credentials/session tokens come from is not specified. That hidden dependency (implicit credentials or access baked into the shared modules) is a proportionally large privilege for a seemingly public registry entry and should be clarified before use.
Persistence & Privilege
The skill is not marked always:true and does not request persistent presence or changes to other skills. It does not attempt to modify system or skill configs in the provided instructions.
What to consider before installing
This skill itself is instruction-only and appears to do what its name says, but it depends on organization-internal modules (../../polymarket-data-layer) and an MCP session handshake that are not declared in the registry metadata. Before installing or enabling it: 1) Confirm the skill's source and that the referenced polymarket-data-layer library exists and is trusted. 2) Ask the publisher where MCP credentials/session tokens are stored and whether the shared client has network access to internal databases. 3) Verify the MCP client's code (mcp-client.js and smartmoney/gamma wrappers) to ensure it does not exfiltrate data and uses least-privilege credentials. 4) Run the skill in a restricted/dev environment first to observe behavior and outputs (it will execute SQL queries via the shared client). 5) If you do not operate inside the organization that hosts those shared modules, expect the skill to fail or to rely on hidden credentials — avoid running it with elevated access. If the publisher cannot explain the implicit credentials or provide source code for the shared data-layer wrappers, treat the skill as untrusted.Like a lobster shell, security has layers — review code before you run it.
latestvk976apy7c2dkktnmzxateaz1d1842ga1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.