Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Trading Decision Pro
v1.0.1AI-powered trading decision assistant by Automaton. Market sentiment analysis, risk assessment, real-time trade recommendations.
⭐ 0· 84·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 README/SKILL.md repeatedly describes multi-source sentiment aggregation (social, news, on‑chain, Fear & Greed, Telegram, etc.) and documents an apiKey option as required. Registry metadata lists no required env vars or primary credential. The included code simulates data (Math.random) rather than implementing network fetches. That combination (big external-data claims + no declared credentials + simulated local behavior) is inconsistent: either the skill should declare and document the data providers and required keys, or the published description is overstating capabilities.
Instruction Scope
SKILL.md shows runtime guidance that expects an apiKey and refers to installing via clawhub and contacting the author for paid services via private messaging (WeChat/Telegram). The provided index.js implements functions locally (simulated sentiment/indicators) and does not contain network calls in the visible portion; SKILL.md implies external endpoints and paid 'advanced signals' which are not implemented. The SKILL.md also instructs use of an apiKey but the registry declares none — the runtime instructions therefore may be misleading or incomplete.
Install Mechanism
No install spec is present and package.json has no dependencies, so nothing is automatically downloaded from arbitrary URLs. The skill appears to be shipped as source files in the bundle. This is lower risk than a skill that downloads/extracts remote archives, but the lack of an install spec while SKILL.md shows clawhub/npm install instructions is a documentation inconsistency to be aware of.
Credentials
The code reads an API key from options.apiKey or process.env.TRADING_DECISION_API_KEY, and SKILL.md documents an apiKey parameter; yet the registry metadata shows zero required environment variables and no primary credential. That mismatch is abnormal: a trading data integrator normally needs credentials (exchange/data provider API keys). The skill asking for private contact/payment channels for 'pro' features also increases the need to verify where credentials or payments are being sent. Require/env declarations should match actual runtime needs.
Persistence & Privilege
The skill does not request 'always: true' and does not declare any system-level config or privilege. There is no indication it modifies other skills or system settings. Autonomous invocation is allowed (default) but not combined here with other high-risk flags.
What to consider before installing
Key concerns to consider before installing or using this skill:
- Metadata mismatch: SKILL.md and README say an apiKey is required for data sources, but the registry shows no required env vars. Confirm with the author which API keys and providers are actually needed and why they were omitted from the registry manifest.
- Overstated capabilities: The code mostly simulates sentiment and indicators (randomized values) instead of fetching real social/news/on‑chain data. If you expect real‑time multi‑source signals, ask where those integrations live and whether they'd require additional credentials or network access.
- Credentials and privacy: Do not supply real API keys, exchange/private keys, or account credentials to an unverified author. If the skill later requests keys or asks you to contact a private channel for paid features, verify the payment flow and data handling policy before sending sensitive info.
- Out‑of‑band payments/contact: The skill encourages contacting via WeChat/Telegram and paid tiers. That is a common fraud vector — prefer payment via verified platform channels and avoid sharing credentials over private messaging.
- Code quality issues: The shipped index.js appears truncated/buggy in places (e.g., truncated variable name, inconsistent authorship in package.json vs meta). These suggest the package may be incomplete or unmaintained. Run the included test suite in a sandbox before trusting outputs.
- What to ask the maintainer / next steps: Request a clear list of required environment variables and external endpoints, a full untruncated index.js, and proof of data-source integrations. Run the package in an isolated environment, inspect network activity during use, and only supply API keys after you confirm the endpoints and that the maintainer is trustworthy.
Overall: the package is not obviously malicious, but the inconsistencies, overclaims, and code issues make it unsafe to treat as production‑ready without additional verification.index.js:18
Environment variable access combined with network send.
Patterns worth reviewing
These patterns may indicate risky behavior. Check the VirusTotal and OpenClaw results above for context-aware analysis before installing.Like a lobster shell, security has layers — review code before you run it.
latestvk977x46642a1d32nmhq707vk8583gh71
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🧠 Clawdis