Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Cross-Asset Intelligence
v1.0.2Cross-asset financial analysis API combining crypto and traditional markets. BTC vs S&P500/NASDAQ/Nikkei225/DAX correlation, cross-market risk score (0-100),...
⭐ 0· 77·0 current·0 all-time
bySuga@sugacrypto
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill claims to provide paid cross-asset analysis via an x402 micropayment API. Requesting a wallet private key to sign micropayments is technically coherent with that purpose, but the registry metadata lists no required env vars or primary credential while SKILL.md explicitly instructs storing WALLET_SIGNING_KEY — an inconsistency in declared vs. actual requirements.
Instruction Scope
The runtime instructions tell the agent to automatically pay per request using a wallet private key and to make HTTP GET calls to an external endpoint (https://x402.bankr.bot/...). That grants the skill the ability to trigger external network calls that will consume funds whenever invoked. The SKILL.md does not provide controls or limits the agent should apply (e.g., spend caps, explicit user confirmation per payment), increasing the risk of unintended charges.
Install Mechanism
This is an instruction-only skill with no install spec and no code files; nothing is written to disk and no packages are pulled in by an installer, which minimizes supply-chain risk.
Credentials
SKILL.md requires a single highly sensitive secret (WALLET_SIGNING_KEY, a 32-byte private key). That is proportionate to an API design that signs on-chain micropayments, but the manifest did not declare this credential (primaryEnv is absent). Storing a raw private key in an env var is risky; if the agent or any component makes requests autonomously, that key could be used to drain funds. The skill's guidance to use a dedicated limited-funds wallet is appropriate but optional and unenforced.
Persistence & Privilege
The skill is not 'always' included, but model invocation is allowed (platform default). Combined with an agent-held wallet key and automatic per-request payments, autonomous invocation increases blast radius: the agent could make repeated paid requests without explicit user confirmation. The skill does not instruct explicit spend limits, user prompts, or rate-limiting.
What to consider before installing
Before installing: (1) Confirm the registry metadata is corrected to declare WALLET_SIGNING_KEY (ask the author why it was omitted). (2) Do NOT supply your main wallet private key — create a dedicated wallet with a small capped balance for this skill. (3) Prefer signing flows that use an external signer or constrained approvals rather than plaintext private keys in env vars; avoid storing keys in unencrypted .env files. (4) Ask the author how payments are signed, whether the service can request/execute payments without explicit user confirmation, and whether there are spend caps or per-call confirmation options. (5) If you cannot verify the endpoint operator (x402.bankr.bot) and audit the payment flow, avoid giving the agent any private key or running this skill autonomously.Like a lobster shell, security has layers — review code before you run it.
latestvk978bzcf3qcbs58qcjyp6gmw5x84ezgg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.