test
Analysis
The skill is clearly for minting an NFT, but it asks an agent to sign and submit a Solana transaction with a funded wallet, which deserves careful review before use.
Findings (3)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
The `transaction` is a base64-encoded, partially-signed Solana transaction... Deserialize and sign with your Solana keypair... `tx.sign([yourKeypair]);`
The agent is instructed to sign an opaque transaction produced by the remote backend; the artifact does not instruct the user or agent to inspect the transaction contents or obtain explicit approval before signing.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
- A **Solana wallet keypair** with at least **0.02 SOL** for network fees
The skill requires access to a funded wallet keypair, which is sensitive financial authority even though it is purpose-aligned with minting.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
curl -X POST https://chum-production.up.railway.app/api/villain/challenge ... `"walletAddress": "YOUR_SOLANA_PUBLIC_KEY"` ... POST `/villain/execute` ... `"transaction": "<base64_encoded_signed_transaction>"`
The flow sends the user's public wallet address and the signed transaction to the CHUM API, which is expected for this minting workflow but should be noticed.
