菜单
Read the sales pipeline and find who has gone quiet — prospects contacted but not answered, past the follow-up window. Reads records before judging them; invents nothing. Use in the gone-cold and weekly review workflows.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/AutomatedMarketer/agent-team-template --skill review-pipeline命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Apply the week's learning to the team's written rules, raise everything that would rewire the team as a task card, and write the one-page tune-up report. Use as the closing step of the weekly tune-up.
Write the run-log entry that records what this run did. Use at the end of every agent run, scheduled or manual, before committing.
Turn the owner's reaction to a draft — shipped, edited, or binned — into a filed verdict and a written rule, so the same correction never has to be made twice. Use whenever the owner says what they did with a piece the team produced.
正在显示 SKILL.md
| name | review-pipeline |
| description | Read the sales pipeline and find who has gone quiet — prospects contacted but not answered, past the follow-up window. Reads records before judging them; invents nothing. Use in the gone-cold and weekly review workflows. |
The pipeline is agents/sales/output/pipeline.md unless a CRM is connected. Either way
the job is the same: who did we approach, who answered, and who has gone quiet.
Three rules, in force whether the pipeline is a markdown table or a connected CRM:
A prospect is cold when all three hold:
A prospect we said we would skip stays skipped. A prospect with a reply logged is warm, whatever the date says.
A list, coldest first — for each quiet prospect: name, what we last sent and when, the
follow-up note from their research file (agents/sales/output/<date>-<prospect>.md)
when one exists, and anything in the row that suggests why they went quiet.
Also note pipeline health in two lines: how many rows total, how many active, how many cold. The weekly review reads this step's output too, so write it to be read twice.
If the pipeline is empty or has no cold rows, say so in one line. An empty chase list is a fine result; a padded one costs the owner real relationships.