SushiSwap API

REST API for optimized token swapping (including executable transaction generation), swap quoting, and pricing using the SushiSwap Aggregator. Use this skill when the user wants to: - Get a swap quote between two tokens on 40+ evm networks - Generate executable swap transaction data - Fetch token prices for a specific network or token - Retrieve token metadata - Discover supported AMM liquidity sources - Integrate SushiSwap swapping or pricing logic via HTTP/REST (and not the SushiSwap Javascript API)

This skill appears to be a documentation-driven wrapper around SushiSwap's HTTP API and does not request credentials or install code. Before installing: (1) Verify the API base URL (https://api.sushi.com) and that the OpenAPI file matches the official SushiSwap API from a trusted source; (2) Decide how you will supply the mandatory 'referrer' value (the skill forbids auto-generating it) — treat it as an integrator identifier and do not embed secrets; (3) Review the openapi.yaml for any unexpected endpoints or encoded/obfuscated blocks (the scanner flagged a base64 pattern); (4) Be aware that fee and feeReceiver parameters can redirect fees — only use trusted feeReceiver addresses and understand business implications; (5) Do not provide private keys or wallet secrets to the skill — the API returns transaction calldata but the skill does not and should not sign or submit transactions on your behalf without explicit, secure handling. If you need higher assurance, ask the skill author for a source/homepage or a cryptographic provenance proof for the OpenAPI file.

Type: OpenClaw Skill Name: sushiswap-api Version: 0.1.0 The skill bundle provides a legitimate integration with the SushiSwap API for token swapping, pricing, and transaction generation. The `SKILL.md` and `references/OPENAPI.md` files contain clear instructions for the AI agent, emphasizing the use of a `referrer` parameter and explicitly forbidding the fabrication of transaction calldata or unauthorized modification of fee parameters. There is no evidence of prompt injection attempts, data exfiltration, malicious execution, persistence mechanisms, or obfuscation. The `openapi.yaml` defines standard API endpoints for DeFi interactions, including the generation of transaction data, which is expected for this type of service and is intended for user approval, not automatic execution by the agent.