# Find Nansen Tokens and Entities

Blockchain researchers often need a token address or entity match from a plain name. This skill runs Nansen search commands and returns concise matches with useful fields.

## Install

```bash
npx skillstore add internet-court/nansen-general-search
```

## Metadata

- Status: approved
- Slug: internet-court-nansen-general-search
- Skillstore revision: r1
- Version status: missing
- Tree hash: d4d427452c7c13518e15dcebf59d019efb024e7b99cf2022bafe9b3d76f7b331
- Author: internet-court
- GitHub username: internet-court
- License: MIT
- Repository: https://github.com/internet-court/internet-court-skill/tree/main/vendored/nansen/nansen-general-search
- Ref: 3f6e026a3363e0954ede7bef0cfe88d4475de137
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, env\_access
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/internet-court-nansen-general-search
- Manifest: https://skillstore.pages.dev/api/skills/internet-court-nansen-general-search/manifest

## Capabilities

- Search Nansen for tokens by case-insensitive name text.
- Search Nansen for entities by name with a result limit.
- Filter token searches by blockchain using the chain option.
- Request selected result fields such as address, name, symbol, and chain.
- Explain when address lookup should use profiler labels instead of search.

## Use Cases

- Resolve Token Addresses: Find likely token matches by name before checking address, symbol, and chain details.
- Identify Known Entities: Search for entity names and review a small set of possible Nansen matches.
- Prepare Research Inputs: Collect normalized names, addresses, and chains for downstream wallet or token analysis.

## Prompt Templates

### Find a Token

```
Use Nansen search to find token matches for "jupiter". Show address, name, symbol, and chain when available.
```

### Search an Entity

```
Search Nansen for the entity name "Vitalik" and limit results to five. Summarize each likely match.
```

### Filter by Chain

```
Find token matches for "bonk" on Solana only. Return the most relevant fields and explain any ambiguity.
```

### Build a Research Shortlist

```
Search Nansen for these names: "jupiter", "bonk", and "aave". Separate token and entity results, include chains, and note unresolved names.
```

## Limitations

- Requires the nansen CLI and a valid NANSEN\_API\_KEY.
- Does not match directly by address.
- Depends on Nansen data availability and API permissions.
- Search results are limited by the CLI maximum result count.

## Best Practices

- Use the smallest result limit that answers the research question.
- Verify token addresses before using them in transactions or reports.
- Use a dedicated Nansen API key and rotate it when access changes.

## Anti Patterns

- Do not use this skill as proof that a token is safe or endorsed.
- Do not search by address; use the appropriate address lookup workflow.
- Do not expose API keys in prompts, logs, screenshots, or shared outputs.

## Security Audit

- Audited at: 2026-07-21T03:25:54.386\+00:00
- Summary: All eight static findings are false positives. The six 'external\_commands' hits are the static analyzer misclassifying Markdown code-fence markers and documentation table rows as Ruby/shell backtick execution; the two 'env\_access' hits are declarative references to the NANSEN\_API\_KEY environment variable name in the skill's metadata \(requires/primaryEnv\), not code that reads or exfiltrates the secret. The skill only documents invocations of a first-party 'nansen' CLI with hardcoded subcommands and no command-injection vector. No prompt injection, data exfiltration, or business-logic abuse was found.

## Stats

- Views: 0
- Downloads: 4
- Favorites: 1
- Popularity score: 0