Silke Manifold
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill appears to match its Manifold Markets purpose, but it can use your API key to directly change bets and positions, including sell-all actions, without enforced confirmation.
Use this only if you intentionally want your agent to access and trade on your Manifold account. Keep the API key private, test read-only commands first, use dry-run for bets, and require a clear manual confirmation before any bet, sell, or cancel action.
Findings (2)
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.
If an agent misunderstands a request or acts too freely, it could liquidate a Manifold position or otherwise change your account state.
The documented default sell command is an account-mutating action and is presented as selling all shares; unlike the bet section's dry-run guidance, the artifacts do not specify a confirmation or dry-run safeguard for this path.
# Sell all shares in a market
python3 {baseDir}/scripts/manifold.py sell <contract-id>Require explicit user confirmation before any bet, sell, or cancel command, and consider adding enforced dry-run or confirmation checks plus amount/share limits in the script.
Any agent process that can invoke the skill with this environment variable can access account data and perform permitted Manifold API actions.
The skill requires a Manifold API key as its primary credential. This is expected for the stated purpose, but it gives the skill authority to access and modify the user's Manifold account through the API.
"requires": { "bins": ["python3"], "env": ["MANIFOLD_API_KEY"] },
"primaryEnv": "MANIFOLD_API_KEY"Use a revocable Manifold API key, keep it out of shared environments, and remove or rotate it if you no longer trust the skill.