Monte Carlo Crypto Core

Monte Carlo Crypto Trading Core. Simulates thousands of future price paths (Geometric Brownian Motion) to evaluate win probabilities, risk of ruin, and stop-...

This skill appears to implement the Monte Carlo simulation it advertises, but treat the billing parts with caution before installing. Key points to consider: - Billing and charges: The skill uses an external billing API (https://skillpay.me). Every non-skipped run calls the billing endpoint and may require payment. Test using the --skip-billing flag or a sandbox account first. - Hardcoded credentials: scripts/billing.py contains a hardcoded API key and a default SKILL_ID ('paythefly'). If you fail to set the required environment variables, the skill will fall back to those values and route billing requests to that account. That may cause unexpected charges or route payments away from your intended destination. - Docs inconsistency: SKILL.md and README refer to SKILLPAY_API_KEY, but the code expects SKILL_BILLING_API_KEY. Confirm which environment variables the platform will actually provide and set them explicitly before use. - What to do before using: inspect/replace billing.py or remove the hardcoded defaults, verify SKILL_BILLING_API_KEY points to an account you control, and run an initial test with --skip-billing or a test user to confirm behavior. If you cannot verify the billing endpoint and the account it charges, do not supply real payment credentials. Confidence is medium because the issues look like sloppy engineering (inconsistent env var names, hardcoded fallback) rather than clear malice, but the hardcoded billing fallback is a real risk that should be resolved or verified prior to use.

Type: OpenClaw Skill Name: totoxu-montecarlo Version: 1.3.0 The skill provides a legitimate Monte Carlo simulation tool for crypto trading using Geometric Brownian Motion. It includes a billing integration with an external service (skillpay.me) to facilitate pay-per-use functionality, which is clearly documented in SKILL.md and README.md. The code in scripts/montecarlo.py and scripts/billing.py is transparent, lacks high-risk behaviors like shell execution or data exfiltration, and the hardcoded API key in the billing script appears to be a low-privilege fallback for the service's SDK.