Committee Prediction Market Skills

• Risk level: Low Risk
• Analyzed: Mar 7, 2026, 2:53 AM
• Findings: 0
• Version: 0.1.0

Overview

The skill's instructions and requirements are coherent with a committee-based prediction-market integration on BSC; it is instruction-only, asks for no extra credentials, and contains no obvious unrelated or disproportionate demands.

This instruction-only skill appears coherent for interacting with the specified BSC contracts, but take these precautions before using it: - Verify the on-chain addresses and constants in the SKILL.md (factory and token addresses) independently (e.g., block explorer) before sending transactions. - The skill assumes you provide an RPC endpoint and an account able to sign transactions; it does not request keys itself. Never hand your private keys to an agent or skill; instead, use a secure wallet or transaction-signing flow that you control. - Test flows on a testnet or fork first; on mainnet transactions are irreversible and can move funds. - Be cautious when approving tokens — avoid unlimited allowances unless you understand the implications. - Note the minor mismatch: the doc expects upper-layer config/env vars but lists none as required. Make sure your workflow supplies the needed addresses, RPC, and signer explicitly rather than relying on implicit environment access. If you want higher assurance, request the author to declare the expected environment variables (RPC URL, contract addresses, signer identifier) in the skill metadata and to document any exact JSON-RPC calls the agent will make.