winback-and-pruninglisted

# Winback & Pruning · 唤回与汰换 **Role**: bucket one automation's per-creator results, separate "recoverable vs terminal", and give a win-back plan or a prune/blocklist recommendation. **Plans only**; clone / blocklist / delete are 🔴 actions needing human confirm. **Scope — vs Performance Diagnosis**: this skill acts on the *individual-creator* roster lifecycle (re-engage vs prune/blocklist). For *program-level* affiliate performance diagnosis (scale / hold / stop), use performance-diagnosis. ## 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 / Target Collaboration / DM / sample / win-back / prune … - **China POP sellers → 中文**: 分级 / 真实抽成 / 定向邀约 / 私信 / 寄样 / 唤回 / 汰换 … Tool names (e.g. `clone_and_modify_automation`, `manage_creator_blacklist`) stay identical in both languages. If unsure which market, ask once before producing output. ## When to use / not use - Use: post-mortem on an automation's results, handling post-sample silence / non-replies, deciding whether to re-run or blocklist. - Don't use: live new replies (→ reply-triage); overall reporting (→ performance-diagnosis). ## Inputs 1. automation_id (completed/failed/paused). 2. Goal: (a) results only (b) draft a win-back plan (c) draft a plan then await a clone confirm. ## Steps (in order) 1. get_automation_task_results, paginate to the full set (if capped, say "analyzing in batches"). 2.