Back to skill
Skillv0.5.2
ClawScan security
Openclaw · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignMar 12, 2026, 12:52 AM
- Verdict
- benign
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill's declared purpose (a Skytale trust/MLS integration) aligns with its requirements and instructions — it asks for a single Skytale API key and Python, and its runtime steps center on installing and using the Skytale Python SDK and MCP integration.
- Guidance
- This skill appears to do what it says: provide an MLS-based trust layer via the Skytale Python SDK. Before installing, confirm you trust the skytale.sh service and the skytale-sdk package on PyPI (verify package name, maintainer, and release history). Treat SKYTALE_API_KEY as highly sensitive: give it least privilege, store it securely, and rotate/revoke it if you suspect misuse. Review the skytale-sdk code (or your security team's vetting) if your environment requires stricter supply-chain assurance, and avoid placing API keys in shared config files (examples/openclaw-config.json includes keys in env blocks — do not commit real keys to source control).
Review Dimensions
- Purpose & Capability
- okName/description (Skytale/MLS trust layer) match the requested items: python as runtime and a SKYTALE_API_KEY. Examples and SKILL.md show using skytale-sdk, MCP server integration, identity, encrypted channels, audit logs and federation, which are all consistent with the stated purpose.
- Instruction Scope
- noteSKILL.md limits runtime actions to installing/using the skytale-sdk, configuring an MCP entry, and calling SDK/MCP functions to create/join channels, send/receive messages, manage keys, and record encrypted audit logs. It does require the agent to hold and use the SKYTALE_API_KEY (sensitive) and the examples add SKYTALE_IDENTITY in env; users should understand the skill enables networked operations to Skytale servers and will transmit user-supplied messages and state to that service.
- Install Mechanism
- okNo packaged install spec in the registry; the skill is instruction-first and includes a setup.sh that invokes pip to install skytale-sdk[mcp]. Using pip for a named SDK is typical; this is a moderate-risk operation (third-party package install) but consistent with the skill's needs. No downloads from arbitrary URLs or obfuscated installers are present.
- Credentials
- noteThe skill requests a single primary credential (SKYTALE_API_KEY), and examples also reference SKYTALE_IDENTITY for MCP runtime. The number of env vars is proportional to the integration, but the SKYTALE_API_KEY is powerful — it grants access to the Skytale API and should be treated as a sensitive secret with least-privilege and rotation policies.
- Persistence & Privilege
- okThe skill is not always-enabled (always: false), is user-invocable, and does not request system-wide configuration changes. Its setup script installs a Python package but does not modify other skills or agent-wide configs beyond instructions to add an MCP server entry. No excessive persistence or privilege escalation is requested.