Messari

Crypto market intelligence powered by Messari's REST API. Provides real-time access to Messari AI (chat completions over 30TB+ crypto data), Signal (sentiment, mindshare, trending narratives), Metrics (prices, volumes, fundamentals for 34,000+ assets across 210+ exchanges), News, Research, Stablecoins, Exchanges, Networks, Protocols, Token Unlocks, Fundraising, Intel, Topics, and X-Users data. Use when the user asks about crypto markets, token analysis, sentiment, protocol metrics, asset research, trending narratives, stablecoin flows, token unlock schedules, fundraising rounds, governance events, or any blockchain/crypto data question. Requires a Messari API key and Messari AI credits.

Before installing: - Confirm provenance: the skill's source/homepage is missing; prefer skills published by a known owner or linked to an official Messari listing. - Verify how your Messari API key will be supplied and stored by the platform (the SKILL.md requires MESSARI_API_KEY, but the registry metadata doesn't list it). Ensure the platform injects the key only into requests to api.messari.io and does not expose it elsewhere. - Understand cost: Messari AI completions require paid AI credits — confirm who bears the cost when the skill uses AI endpoints. - If you proceed, provide only the Messari API key (no other unrelated secrets), monitor the skill's network usage, and revoke the key if you see unexpected behavior. If you need higher assurance, request the publisher to correct the registry metadata to explicitly list MESSARI_API_KEY (and any other required vars) and provide an official homepage or owner verification.

Type: OpenClaw Skill Name: messari-crypto Version: 1.0.0 The skill bundle is designed to integrate with the Messari REST API for crypto market intelligence. All files, including the `SKILL.md` instructions for the AI agent and the `references/api_services.md` documentation, are clearly aligned with this stated purpose. The `SKILL.md` correctly declares the `MESSARI_API_KEY` as a required environment variable and provides benign `curl` examples demonstrating API usage. There is no evidence of prompt injection attempts, data exfiltration to unauthorized endpoints, malicious execution, persistence mechanisms, or obfuscation.