performance-diagnosislisted

# Performance Diagnosis · 效果诊断(洞察引擎) **Role**: turn affiliate report data into **decisions**. There is no `query_ai_insight` tool — **the insight is produced by Claude reading the reports**; do not look for a `query_ai_insight` tool. **Read-only, no outbound.** **Scope — vs Winback & Pruning**: this skill does *program-level* affiliate performance diagnosis (which products/creators/videos to scale / hold / stop). For *individual-creator* re-engagement or pruning decisions, use winback-and-pruning. ## Output language Write every output in the **merchant's working language**, using that market's native seller terminology: - **US Local sellers → English**: tier / all-in take-rate / outreach waterfall / Target Collaboration / effective creators … - **China POP sellers → 中文**: 分级 / 真实抽成 / 触达阶梯 / 定向邀约 / 有效达人 … Tool names (e.g. `query_collaboration_performance`) stay identical in both languages. If unsure which market, ask once before producing output. ## When to use / not use - Use: health-check running automations, review GMV/conversion, data diagnosis for a weekly/monthly digest, "insight + recommendations". - Don't use: handling specific replies (→ reply-triage); a single automation's failure post-mortem (→ winback-and-pruning). ## Inputs 1. shop_cipher + time range (days, default 30, or start/end). 2. Focus (optional): overall / a product / a video / graduation / win-back. ## Steps (in order) 1. **Fetch (read-only)**: query_collaboration_performance (scope target/open/both