Horizon SDK
Analysis
This appears to be a real prediction-market trading skill, but it can place and cancel orders using an API key and delegates core trading behavior to an external SDK, so it needs careful review before installation.
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
price = _safe_float(args[3], "price") size = _safe_float(args[4], "size") _print(tools.submit_order(market_id, side, price, size, market_side))
The wrapper passes agent/user-supplied price and size directly into the SDK order-submission call, and the provided artifacts do not show a confirmation gate, maximum size, or price/position limit before submitting trades.
[0] uv | formula: horizon-sdk
The skill installs an external SDK by package name, and the provided wrapper imports that package for the core trading operations. For a financial trading skill, an unpinned external dependency and unknown source increase the importance of verifying package provenance.
Start a live data feed: start-feed <name> <feed_type> [config_json]
The skill documents starting live data feeds, which is consistent with trading and market analytics, but users should recognize that this may create ongoing background activity in the Horizon environment.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
requires:
env:
- HORIZON_API_KEY
primaryEnv: HORIZON_API_KEYThe skill explicitly requires a Horizon API key, which is expected for this integration but is sensitive because the same skill also exposes account and order-management operations.
