⚠
Purpose & Capability
Name/description match the code and SKILL.md: wallet creation, balance lookups via Helius/DAS, sends, and Jupiter swaps are implemented. However the registry metadata declared no required credentials or config, while the code and SKILL.md require a heliusApiKey stored in ~/.config/solana-skill/config.json and will error if it's missing. That mismatch (declaring no required credential while the skill will not function without an API key file) is an incoherence users should know about.
⚠
Instruction Scope
SKILL.md and code stay within the stated domain (Solana + Helius + Jupiter) and do not read arbitrary system files. However: (1) the wallet module derives an encryption password from process.env.USER and process.env.HOME (getDefaultPassword), which implicitly uses environment data not declared in the metadata and results in predictable/weak encryption; (2) references include webhook creation with arbitrary webhookURL (the code exposes a path to register webhooks that can post to any endpoint) — that enables sending on-chain events to external endpoints if the user configures it; and (3) some reference endpoints list non-HTTPS regional Helius sender URLs (http), which is an operational/security note. The instructions are otherwise explicit rather than vague, but the agent/code will create persistent config and wallet files and rely on a non-secret machine-derived password unless the user changes behavior.
✓
Install Mechanism
There is no install spec (instruction-only at registry level) and all code is present in the bundle. No external arbitrary download or archive extraction occurs during install. package.json lists reasonable dependencies (@solana/web3.js, helius-sdk, etc.). Risk is limited to running the included scripts (npx tsx) — evaluate those scripts before running.
⚠
Credentials
The skill does not declare required environment variables or a primary credential in the registry, but it requires a Helius API key stored in a config file (~/.config/solana-skill/config.json). The code also implicitly uses process.env.USER and process.env.HOME to derive a default wallet password (not documented as a required secret), which is disproportionate: deriving encryption secrets from predictable environment values is weak and surprising. Other than that, the skill does not request unrelated cloud credentials. The discrepancy between declared requirements and actual file/env access is the main proportionality issue.
ℹ
Persistence & Privilege
The skill creates and reads persistent files under ~/.config/solana-skill (config.json, wallets/, logs). That is expected for a wallet manager, but it's a significant persistent presence on disk and stores encrypted private keys. always:false (normal) and the skill does not modify other skills or global agent settings. Users should be aware these files are long-lived and control their filesystem permissions and backups.