Back to skill
Skillv1.0.0
ClawScan security
Asset Management · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignMar 9, 2026, 2:56 PM
- Verdict
- benign
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill's code, instructions, and data flows match its stated purpose (local portfolio management with optional Cloudflare KV sync); no evidence of hidden exfiltration or unrelated privileges, but pay attention to cloud sync configuration and a few minor inconsistencies.
- Guidance
- This skill appears coherent: it stores portfolio data locally and optionally syncs to a Cloudflare Worker you deploy. Before installing: 1) If you enable cloud sync, only point the skill at a worker URL you control and choose a strong token — data in ~/.openclaw/data/cryptofolio.json will be uploaded to that endpoint. 2) Do not deploy or use someone else's worker URL/token (that would let a third party receive your data). 3) The repo contains a worker template with a placeholder token; be sure to replace it when deploying. 4) The local web server logs and serves the same JSON file on localhost (no auth) — avoid starting it on shared machines. 5) If you want extra assurance, review the scripts (they're readable JS) and consider running them in an isolated environment. If you want me to, I can point out exact lines where the cloud URL/token are read and where data is POSTed/persisted.
Review Dimensions
- Purpose & Capability
- okName/description (crypto asset manager with export and optional cloud sync) align with the included CLI, local storage, web UI, and Cloudflare Worker backend. The files implement the stated features (local JSON storage, CLI commands, local web server, and worker for KV sync).
- Instruction Scope
- noteSKILL.md limits runtime actions to running the provided Node scripts, starting a local server, and configuring a user-provided Cloudflare Worker. The scripts read/write ~/.openclaw/data/cryptofolio.json and a config file and will upload/download that data from the configured cloud endpoint — this is expected for sync functionality but means sensitive portfolio data will be sent to any URL/token you configure.
- Install Mechanism
- okNo automated install or remote downloads are present in the skill package. It is instruction-only for runtime and includes local JS files; nothing in the repo installs external code during skill activation.
- Credentials
- noteRegistry metadata shows no required env vars, but the CLI supports CRYPTOFOLIO_API_URL and CRYPTOFOLIO_TOKEN (and SKILL.md/setup uses a URL+token). This is reasonable for optional cloud sync, but the metadata omission is an inconsistency to be aware of. If you set those env vars they control where your data is sent.
- Persistence & Privilege
- okalways is false and the skill does not request elevated or persistent platform privileges. It stores data under ~/.openclaw/data and does not modify other skills or global agent configuration. The local web server exposes data on localhost without authentication (expected for a local UI).