Back to skill
Skillv1.0.0
ClawScan security
Kuvera Portfolio & Market Data · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignMar 1, 2026, 5:27 PM
- Verdict
- benign
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill's code, instructions, and requirements are coherent with a read-only Kuvera CLI: it only needs a kuvera-cli binary, performs GET requests to api.kuvera.in, and stores a login token in the user's home directory.
- Guidance
- This skill appears to be what it claims: a read-only Kuvera CLI. Before installing, consider: 1) Login requires you to pass your Kuvera email/password to the CLI — avoid putting credentials in shell history (use an interactive prompt or a secure mechanism) because commands like kuvera-cli login <email> <password> may be recorded. 2) The CLI stores a JWT/token at ~/.openclaw/credentials/kuvera/token.json — ensure that file is protected by filesystem permissions and that your machine is trusted. 3) The code enforces a whitelist allowing only GET requests plus the authenticate POST; you may review kuvera-cli.js yourself to confirm no unexpected endpoints are present before running. 4) Because there's no automatic installer, ensure the kuvera-cli binary you place on PATH is the expected script (trust its source). If you need stronger guarantees, test the CLI in an isolated environment or inspect the token file handling and network endpoints further.
Review Dimensions
- Purpose & Capability
- okName/description ask for market & portfolio queries. The skill requires the kuvera-cli binary and the included kuvera-cli.js implements those read-only queries against api.kuvera.in — the requested pieces align with the stated purpose.
- Instruction Scope
- noteSKILL.md instructs the agent to run kuvera-cli commands (market, gold, usd, categories, fund, user, portfolio, transactions, sips). Login requires kuvera-cli login <email> <password>. The runtime instructions and CLI code stick to read-only GET endpoints, but note that login transmits user credentials to Kuvera and the CLI stores a token file (~/.openclaw/credentials/kuvera/token.json) — a normal side-effect but material for user privacy and shell-history consideration.
- Install Mechanism
- okNo automated install script or remote downloads. The README instructs copying the skill folder into the local OpenClaw skills directory. That is low risk compared to remote installers; installing the kuvera-cli binary is required but not automated by the skill.
- Credentials
- okThe skill requests no environment variables or unrelated credentials. It uses process.env.HOME to determine the user's home for token storage — appropriate and proportionate for storing a user auth token.
- Persistence & Privilege
- okalways is false and the skill does not request system-wide privileges. It writes its own token to ~/.openclaw/credentials/kuvera/token.json (expected). It does not modify other skills or global agent settings.