Btc Contract Scanner

<think> The userasks: "Translate the following skill description into concise Chinese. Return JSON only like {"description_zh":"..."}. Description: BTC合约自适应扫描。5策略集成(EMA/MACD/RSI/布林/放量)，双方向评分， walkforward自优化。Serenity逆向价值风格。VPN环境下OKX API就绪。" So we need to output JSON with key "description_zh" and the translation into Chinese. But thedescription is already in Chinese. Actually the user says translate into concise Chinese. The description is already Chinese, but the translation would be the same orrefined? They may want a concise Chinese translation. Possibly they want the English description? Wait they wrote: "Translate thefollowing skill description into concise Chinese." So the description is originally Chinese, but they might want to refine it. The input is in Chinese already. But perhaps they want to translate into Chinese as an output, which is already Chinese. Possibly they want a concise version. The description:"BTC合约自适应扫描。5策略集成(EMA/MACD/RSI/布林/放量)，双方向评分， walkforward自优化。Serenity逆向价值风格。VPN环境下OKX API就绪。" We can condense: "BTC合约自适应扫描，集成5策略（EMA/MACD/RSI/布林/放量），双方向评分，walkforward自优化，采用Serenity逆向价值风格，VPN环境下OKX API已就绪。" That is concise. The JSONmust be like {"description_zh":"..."}. So produce that. Ensure only JSON, no extra text. Use proper JSON formatting, no trailing commas. Also ensure correct encoding of Chinese characters. We'll output thedescription_zh with the concise Chinese. Thus final answer: {"description_zh":"BTC合约自适应扫描，集成5策略（EMA/MACD/RSI/布林/放量），双方向评分，walkforward自优化，采用Serenity逆向价值风格，VPN环境下OKX API已就绪。"} </think> {"description_zh":"BTC合约自适应扫描，集成5策略（EMA/MACD/RSI/布林/放量），双方向评分，walkforward自优化，采用Serenity逆向价值风格，VPN环境下OKX API已就绪。"}