Stove Taker Api

使用 Stove Protocol 的 Taker API 进行锁单、成交、撤单响应以及成交记录与订单查询，基于 API Key 认证访问。

This skill implements CLI calls to the Stove Taker API and will send whatever API Key you provide to the configured base_url (default https://proto.stove.finance). Before installing or using it: 1) Verify whether the actual Stove API requires an API Secret and HMAC signature — the included docs say a Secret/signature is required but the script does not implement signing; if the API does require signing, this tool may not work and you should not supply a secret to an untrusted skill. 2) Treat the API Key as sensitive: provide it only via the skill's secret config (do not paste into chat) and consider using a scoped key for testing. 3) Prefer using the test environment (use_test_env or --env test) when trying the skill. 4) If you rely on this in production, review the Python script source locally to ensure it meets your security and signing requirements or extend it to implement the documented HMAC signing flow. 5) The metadata omission (registry showing no required creds) is a red flag: confirm with the provider/maintainer why the documentation and runtime arguments differ before trusting this skill with real credentials.

Type: OpenClaw Skill Name: stove-taker-api Version: 0.1.0 The skill bundle provides a standard interface for interacting with the Stove Protocol Taker API. The core logic in `scripts/taker_api.py` uses the Python standard library to wrap HTTP requests for order management tasks like locking, filling, and querying orders. While there is a discrepancy between the script's simple API key header implementation and the HMAC signature requirements described in `references/API Authorization.md`, this appears to be a functional oversight or an environmental difference rather than a malicious indicator. The bundle lacks any signs of data exfiltration, unauthorized command execution, or prompt injection attempts.