Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Full Potential Intelligence
v1.0.0Provides real-time AI frontier intelligence with scores, live feeds, labor displacement, investment insights, gap opportunities, and daily briefings.
⭐ 0· 45·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The stated purpose (real-time AI intelligence) could legitimately require contacting a remote service and providing feed data, but the SKILL.md relies on running 'npx mcp-remote' at runtime. The skill metadata declared no required binaries or credentials, yet the instructions effectively require the 'npx' binary and will obtain API keys via self-registration. That mismatch (runtime needs not declared) is an incoherence.
Instruction Scope
The instructions instruct the agent to execute an npm/X command that will fetch and run remote code and open an SSE connection to https://fullpotential.ai/mcp. They also expose write operations (register_agent, contribute_intelligence) that create API keys and accept user-contributed reports. This grants the remote service broad ways to interact with the agent and could result in transmitting user data or enabling remote control — scope exceeds the simple 'read a feed' model the description might imply.
Install Mechanism
There is no formal install spec, but the SKILL.md explicitly invokes 'npx -y mcp-remote ...', which means code will be downloaded and executed at runtime from npm (or whatever npx resolves to). That dynamic fetch/execute pattern is high-risk because the package provenance and contents are not declared, and the MCP endpoint is an unknown host.
Credentials
The registry metadata declares no required environment variables or primary credential, yet the skill's tools include 'register_agent' which 'get API key instantly'. The skill implicitly expects creation and use of credentials but doesn't declare how they will be stored/managed. That gap between declared secrets and the instructions that generate/use keys is a proportionality and transparency problem.
Persistence & Privilege
The skill does not request 'always: true' and has default autonomous invocation settings (normal), but the MCP connection model opens a persistent remote channel which could be used by the remote server to interact with the agent over time. Autonomous invocation combined with remote-executed code increases risk — not a direct metadata flag, but important to consider.
What to consider before installing
This skill will try to run 'npx mcp-remote' and open a live connection to https://fullpotential.ai/mcp and can issue/receive commands and issue API keys via self-registration. That means code will be downloaded and executed from the network and a remote server could influence the agent or receive data. Before installing: (1) verify the skill's source and maintainers (the registry shows 'unknown' and no homepage), (2) ask the author for the mcp-remote package name, its npm link, and a reproducible install method or source code, (3) ensure 'npx' is present or require the package be vendor-checked rather than fetched at runtime, (4) consider running the skill in a strictly sandboxed environment or rejecting it if you cannot verify the remote host and package, and (5) beware that contributing intelligence may send user content to the remote service and that the skill can create API keys that the agent will possess. Given those inconsistencies and the dynamic code execution, proceed only if you trust the publisher and can audit the remote package and server.Like a lobster shell, security has layers — review code before you run it.
latestvk977mc18jztf5e3973ck20h94183pw62
License
MIT-0
Free to use, modify, and redistribute. No attribution required.