OpenCog
ReviewAudited by ClawScan on May 18, 2026.
Overview
The skill appears purpose-built for prediction-market trading, but it controls a wallet and has transaction-limit, key-storage, and provenance issues that should be reviewed before using any real funds.
Use this only with a throwaway wallet at first, prefer Sepolia/testnet, verify the exact repository and code before installing, lock down ~/.openclaw/.env permissions, and require explicit human confirmation of the final network, contract address, market, shares, and true spend/receive limits before any trade.
Findings (4)
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.
A confirmed trade could spend slightly more or receive slightly less than the parameter the user thought was the hard limit, especially if the user pasted a quote-provided slippage value.
The file describes --max as the maximum spend, but the script increases that value by the default slippage before signing the buy transaction. The sell script uses the analogous pattern for --min, which can accept less than the supplied minimum.
// --max is the maximum USDC to spend ... const maxRaw = toRaw((parseFloat(a.max) * (1 + slippage / 100)).toFixed(dec), dec);
Treat --max and --min as sensitive hard limits; patch the scripts so those values are not adjusted again, or use explicit slippage handling and confirm the final raw transaction bounds before trading.
If local file permissions are too broad, another local user or process could read the wallet key and use it to move funds or trade from that wallet.
A generated wallet private key is written persistently to ~/.openclaw/.env in plaintext, and the shown code does not set chmod 600 or another restrictive file mode.
_mkdirSync(_envDir, { recursive: true }); _appendFileSync(_envFile, `\nPRIVATE_KEY=${pk}\n`);Use only a throwaway wallet, immediately restrict ~/.openclaw/.env permissions to 600, and do not store a high-value mainnet key in this skill.
A user relying on registry metadata may not realize before installation that the skill manages a wallet key capable of signing transactions.
The registry metadata under-declares the credential and local state that SKILL.md and package.json describe: PRIVATE_KEY and ~/.openclaw/.env.
Required env vars: none ... Primary credential: none ... Required config paths: none
Update registry metadata/capability declarations so PRIVATE_KEY, ~/.openclaw/.env, network access, and transaction-signing behavior are visible before installation.
A user following the README could install code from a different source than the reviewed homepage, which is risky for software that handles wallet keys and trades.
The declared homepage in metadata/SKILL.md is https://github.com/openclaw/precog-skill, but the README install command points to a different repository.
git clone https://github.com/0xAstraea/opencog-basic precog
Verify the exact repository and commit being installed, and align the README, homepage, source metadata, and reviewed package before using the skill.