Skills nansen-general-search
๐Ÿ“ฆ

nansen-general-search

Content revision r1 Safe โš™๏ธ External commands๐Ÿ”‘ Env variables

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.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "nansen-general-search" from https://skillstore.io/skills/internet-court-nansen-general-search.md and its manifest at https://skillstore.io/api/skills/internet-court-nansen-general-search/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "nansen-general-search". Find token matches for jupiter.

Expected outcome:

Jupiter token candidates are listed with matching names, symbols, chains, and contract addresses. Ambiguous matches are grouped for follow-up verification.

Using "nansen-general-search". Search for Vitalik as an entity.

Expected outcome:

A short entity list is returned with names and available labels. Results are limited to the requested count.

Using "nansen-general-search". Find bonk on Solana and show only key fields.

Expected outcome:

Solana results are filtered to likely Bonk matches. Each result includes the requested identifying fields when Nansen provides them.

Security Audit

Safe
v2 โ€ข 7/21/2026 Open versioned report

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.

1
Files scanned
35
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: claude View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/internet-court-nansen-general-search/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/internet-court-nansen-general-search/security.svg)](https://skillstore.io/skills/internet-court-nansen-general-search?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/internet-court-nansen-general-search?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/internet-court-nansen-general-search/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/internet-court-nansen-general-search.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

internet-court. (2026). nansen-general-search security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/internet-court-nansen-general-search/audits/2

BibTeX citation

@techreport{internet-court-internet-court-nansen-general-search-2026, author = {internet-court}, title = {nansen-general-search security audit report (audit version 2)}, institution = {Skillstore}, year = {2026}, number = {2}, url = {https://skillstore.io/skills/internet-court-nansen-general-search/audits/2}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "nansen-general-search security audit report (audit version 2)" version: "unspecified" type: report authors: - name: "internet-court" date-released: "2026-07-21" url: "https://skillstore.io/skills/internet-court-nansen-general-search/audits/2" identifiers: - type: other value: "skillstore:internet-court-nansen-general-search:audit:2" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
85
Content
65
Community
83
Spec Compliance

What You Can Build

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.

Try These Prompts

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.

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.

Avoid

  • 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.

Frequently Asked Questions

What does this skill search?
It searches Nansen for token names and entity names, then returns matching records from the CLI.
Can it search by wallet or contract address?
No. The source instructions state that address lookup should use profiler labels instead.
Does it require a Nansen account?
Yes. It requires the nansen CLI and a valid NANSEN_API_KEY with suitable access.
Can I limit the number of results?
Yes. The skill supports a result limit, with the CLI maximum noted as 50.
Can it filter results by chain?
Yes. Token searches can be filtered by chain when the CLI supports that filter.
Is it compatible with Claude, Codex, and Claude Code?
Yes. The report lists support for Claude, Codex, and Claude Code.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

3f6e026a3363e0954ede7bef0cfe88d4475de137

Maintenance freshness

7/21/2026

Usage

1 downloads ยท 0 views

File structure

๐Ÿ“„ SKILL.md

More from internet-court

View all
View all