Jupiter Prediction Market

This skill largely implements a Jupiter Prediction Market client, but there are a few things to check before using it: - API key handling: The code expects a JUPITER_API_KEY environment variable or saves the key to config/api-key.json in the current working directory. The registry metadata does not declare this; assume the skill will read and may write an API key file. If you install it, avoid putting long-lived/privileged keys there — use a restricted/ephemeral key if possible. - Persistence: ApiKeyManager.setApiKey() writes config/api-key.json. That will persist secrets on disk under the agent's working directory. If you run this in a shared environment, consider running in an isolated sandbox or container and delete the file after use. - Missing/inconsistent files: src/market_manager.js requires '../api_client' and '../utils' paths that aren't present in the repo and contains mixed-language comments. This indicates the package may be incomplete or poorly packaged; test the scripts in a safe environment before relying on them. - Wallet signing: SKILL.md says transactions require user Solana wallet signatures, but the code does not implement signing flows. Do NOT provide private keys to this package. Confirm how on-chain actions are authorized (external wallet, hardware wallet, or separate signing process) before attempting to create/cancel trades or claim payouts. - Run in sandbox and review code: Because this skill can perform network requests and persist an API key, review the code yourself or run it in an isolated environment. Prefer ephemeral API keys, least-privilege credentials, and monitor network activity. If you don’t trust the author or need autonomous trading, consider a security review or use a vetted client instead.