Skillv2.0.0

ClawScan security

DeFi Position Tracker · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignMar 19, 2026, 1:19 PM

Verdict: Benign
Confidence: high
Model: gpt-5-mini
Summary: The skill's instructions and requirements are coherent with a DeFi position-tracking tool; it is an instruction-only skill that expects use of public DeFi APIs and local calculation code, with no unexpected installs or system-level privileges requested.
Guidance: This skill is internally consistent for DeFi tracking, but review these practical points before installing: - The SKILL.md uses many third-party APIs that require API keys — the skill doesn't declare required env vars, so you should provide keys via the platform's secure secrets (read-only keys preferred). Do not paste private wallet seed phrases or private keys into the skill or chat. - The skill calls external services (DeBank, Zapper, The Graph, Alchemy/Infura, Helius/Birdeye, Revert, etc.). If privacy of wallet holdings matters, consider the privacy policy and data retention of those services before querying them with your addresses. - The provided Python snippet appears truncated/has a small variable typo and simplifies some AMM math; validate formulas and prefer official SDKs (Uniswap v3 SDK or protocol APIs) for concentrated-liquidity calculations. - Because this is instruction-only, nothing is written to disk by the skill itself — but code snippets shown might be executed by an agent or by you locally. Inspect and test locally in a safe environment before running on production data. - If you plan to hand data to another skill (crypto-tax-agent), verify that downstream skill’s behavior and permissions so you understand where your portfolio data will flow.

Review Dimensions

Purpose & Capability: okThe name/description match the runtime instructions: APIs, curl examples, and Python snippets are all aligned with pulling DeFi positions, computing impermanent loss, and preparing data for tax/treasury workflows. The listed protocols and chains are consistent with the data sources cited (DeBank, Zapper, The Graph, Alchemy, etc.).
Instruction Scope: noteSKILL.md restricts itself to fetching on-chain/third-party API data and local calculations. It uses wallet addresses and API keys in examples but does not instruct the agent to read unrelated system files or secret key material. One minor issue: the Python sample is truncated/has a variable typo (token0_price_u) and some comments acknowledging use of external SDKs — this appears to be a documentation/code quality issue, not malicious scope expansion.
Install Mechanism: okNo install spec and no code files — instruction-only. That minimizes disk/write risk. The metadata lists optional binaries (cast, python3, node) which are reasonable for the described tasks and marked optional.
Credentials: noteThe skill demonstrates use of multiple third-party APIs that require keys (DeBank Pro, Zapper, Alchemy/Infura, Helius/Birdeye, etc.), but the registry metadata declares no required env vars or primary credential. This is likely a documentation omission: the examples expect API keys (shown as YOUR_DEBANK_API_KEY, YOUR_ZAPPER_KEY) but the skill does not itself request or store any secrets. Users should supply read-only API keys via the platform's secure secret mechanism rather than pasting private keys into prompts.
Persistence & Privilege: okThe skill is not marked always:true and does not request to modify other skills or system-level settings. It can be invoked autonomously (platform default), which is normal for skills; there is no elevated persistence requested.