ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

RiskState — Risk Governor for Crypto Trading Agents

v1.2.2

Deterministic risk governance API for autonomous crypto trading agents. Returns position limits, allowed actions, and policy constraints from 30+ real-time s...

⭐ 0· 85·0 current·0 all-time
byLikido@likidodefi
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
ℹ
Purpose & Capability
The skill's name, README, docs, and SKILL.md consistently describe a risk-governor API for crypto trading agents — requiring a single API key and returning permissioning data. That capability legitimately needs an API endpoint and key. However, the registry metadata at the top lists "Required env vars: none" while the SKILL.md explicitly declares env: RISKSTATE_API_KEY and shows authentication via a Bearer token. This metadata mismatch is an incoherence (likely a packaging/metadata error) and should be corrected/confirmed.
✓
Instruction Scope
The runtime instructions are narrow and consistent with the stated purpose: POST JSON to https://riskstate.netlify.app/v1/risk-state with Authorization: Bearer $RISKSTATE_API_KEY. Optional wallet parameter is relevant to DeFi monitoring. The SKILL.md does not instruct the agent to read unrelated files, other credentials, or system secrets.
✓
Install Mechanism
This is an instruction-only skill (no install spec, no code files to execute). That is lower risk because nothing is written or executed locally by the skill itself.
ℹ
Credentials
The service needs one credential (an API key) which is proportionate to its function. The concern is the registry metadata failing to list this required env var — users or the platform could miss prompting for the key or mis-handle permission scopes. Also note the docs reference an owner/admin key and external `rs_live_` keys; users should ensure they only supply external keys with limited scope.
✓
Persistence & Privilege
The skill does not request always:true and has no install-time persistence steps. It does not ask to modify other skills or system-wide settings in the provided materials.
What to consider before installing
What to check before installing or enabling this skill: - Verify the API host and ownership: SKILL.md points at https://riskstate.netlify.app for the API while the homepage is https://riskstate.ai. Confirm that riskstate.netlify.app is an intentional API host for RiskState (e.g., check the official website, GitHub repo, and maintainers) before sending an API key. - Provide a limited-scope key: use an "external"/read-only key (rs_live_ type) if possible, and avoid giving any owner/admin keys to the skill. Do not hardcode keys into source; use environment variables as recommended. - Correct the metadata gap: the registry metadata claims no required env vars, but SKILL.md requires RISKSTATE_API_KEY. Ask the publisher or registry to update the metadata so the platform can surface the prompt for the API key and label required permissions correctly. - Test with minimal data and monitoring: try one-off calls and verify network traffic (outbound destination, IPs, TLS certificate) and response shape before enabling the skill for autonomous use. Monitor API usage and rotate keys if anything looks unexpected. - Treat wallet parameter as sensitive: only supply wallet addresses when you intend on DeFi monitoring; the wallet parameter is relevant but it can expose on-chain linkage for that key. If the publisher provides a clarified package (metadata listing RISKSTATE_API_KEY) and an expected API host matching their official domain or a documented, trusted endpoint (and you can confirm the GitHub/org), this would reduce the concern. Conversely, unexpected hosts or requests for broader credentials would increase risk.

Like a lobster shell, security has layers — review code before you run it.

agent-skillsvk973hn7y6svez55b5dh22makvd83k0hzagentsvk973hn7y6svez55b5dh22makvd83k0hzaivk973hn7y6svez55b5dh22makvd83k0hzai-agentsvk973hn7y6svez55b5dh22makvd83k0hzai-tradingvk973hn7y6svez55b5dh22makvd83k0hzbitcoinvk973hn7y6svez55b5dh22makvd83k0hzbtcvk972arvfzw0hzgg6e4seyxy1r983dp22cryptovk973hn7y6svez55b5dh22makvd83k0hzdecentralized-financevk973hn7y6svez55b5dh22makvd83k0hzdefivk973hn7y6svez55b5dh22makvd83k0hzdefi-risk-managementvk973hn7y6svez55b5dh22makvd83k0hzethvk972arvfzw0hzgg6e4seyxy1r983dp22ethereumvk973hn7y6svez55b5dh22makvd83k0hzgovernancevk972arvfzw0hzgg6e4seyxy1r983dp22latestvk977zcvdp5z11qgqnhzkn7gv7h83k7nspolicyvk972arvfzw0hzgg6e4seyxy1r983dp22policy-enginevk973hn7y6svez55b5dh22makvd83k0hzposition-sizingvk972arvfzw0hzgg6e4seyxy1r983dp22riskvk972arvfzw0hzgg6e4seyxy1r983dp22risk-governancevk973hn7y6svez55b5dh22makvd83k0hzskills-shvk973hn7y6svez55b5dh22makvd83k0hztradingvk973hn7y6svez55b5dh22makvd83k0hztrading-botvk973hn7y6svez55b5dh22makvd83k0hz

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments