Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
CoinAPI OpenAPI Skill
v1.0.0Operate CoinAPI market data reads through UXC with a curated OpenAPI schema, API-key auth, and read-first guardrails.
⭐ 0· 140·1 current·1 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 name, description, OpenAPI schema, and runtime instructions all consistently describe a read-only CoinAPI market-data skill using UXC and an OpenAPI schema. That purpose matches the included files (schema, usage patterns, guardrails). However, the skill's manifest metadata declares no primary credential or required env vars while the SKILL.md explicitly requires a CoinAPI API key (COINAPI_KEY) and UXC auth binding; this discrepancy is unexpected and should be justified.
Instruction Scope
SKILL.md stays within the stated read-only scope: it documents only GET operations, instructs use of uxc and a linked CLI, and contains guardrails about read-only behavior and narrow queries. It does not ask the agent to read unrelated local files or exfiltrate data. The only scope creep is the implicit assumption that the runtime environment will provide UXC and the COINAPI_KEY secret (neither declared in the registry metadata).
Install Mechanism
This is instruction-only (no install spec), which is lower risk. Included script scripts/validate.sh performs local checks and requires jq and rg (ripgrep) — these are development/validation dependencies but were not declared in the manifest's required binaries. The script does not download or execute remote code and appears to only validate file presence and schema shape.
Credentials
SKILL.md requires a CoinAPI API key bound to rest.coinapi.io and instructs using the COINAPI_KEY secret env var, but the skill metadata lists no required env vars and no primary credential. That mismatch is the main proportionality concern: the skill needs a sensitive secret to function but does not declare it. Additionally, the validate script expects jq and rg but these binaries are not declared either. Requiring a single CoinAPI API key for read-only market data is proportionate — but it should be declared in the manifest and the consumer should know exactly where/how to supply it.
Persistence & Privilege
The skill does not request always:true and does not modify other skills. There is no install spec that writes persistent binaries, and SKILL.md only instructs creating a uxc CLI link (uxc link) which is scoped to uxc tooling. Autonomous invocation is allowed (default) but that is normal; it is not combined with other high-risk privileges.
What to consider before installing
This skill appears to be a coherent, read-only CoinAPI integration, but there are two gaps you should resolve before installing or using it: (1) SKILL.md requires a CoinAPI API key (COINAPI_KEY) and UXC to be installed, but the registry metadata does not declare that secret or those binaries — confirm how and where you'll supply the COINAPI_KEY (use a least-privileged/read-only key) and ensure uxc is installed from a trusted source; (2) the included validation script requires jq and ripgrep (rg) which are not declared — these are only for local validation but be aware if you run the script. Also verify the curated OpenAPI schema URL (raw.githubusercontent.com/holon-run/...) is from a source you trust. If the publisher cannot explain why the manifest omits the COINAPI_KEY requirement, treat the omission as a red flag and avoid providing secrets until clarified.Like a lobster shell, security has layers — review code before you run it.
latestvk97d5wcnqjywsfrte6mw9q0js9832xbn
License
MIT-0
Free to use, modify, and redistribute. No attribution required.