Nansen Wallet Profiler
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may run Nansen wallet queries and consume API quota while performing analysis.
The skill permits the agent to run Nansen CLI commands. This is central to the wallet-profiler purpose, but users should notice that the agent can invoke those API-backed commands when the skill is used.
allowed-tools: Bash(nansen:*)
Use the skill for specific wallet-analysis tasks and confirm large batch, trace, or export requests before running them.
Large trace or batch requests could consume Nansen credits or hit API limits.
The artifact explicitly documents that tracing can fan out into many API calls. This is disclosed and purpose-aligned, but it can affect cost or rate limits.
`trace` makes many API calls — use `--width` conservatively.
Keep `--depth`, `--width`, and batch wallet lists small unless you intentionally want a broader analysis.
The skill can use the configured Nansen API key to query Nansen services and consume the associated account’s quota.
The skill requires a Nansen API key. This is expected for accessing Nansen data, but it delegates use of the user’s Nansen account credentials to the CLI.
requires:
env:
- NANSEN_API_KEYUse an API key intended for this purpose, rotate it if no longer needed, and monitor Nansen API usage.
Installing the skill also installs and trusts the external `nansen-cli` package.
The skill depends on installing an external Node package to supply its CLI. This is normal for this integration, but the provided artifacts do not include package source or a lockfile.
node | package: nansen-cli | creates binaries: nansen
Install from a trusted registry/source and review the package provenance if your environment has strict supply-chain requirements.