Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
中文简介正在准备中。当前显示原文说明。
Draft a clear, kind rejection email from an approved human decision without inventing feedback or sending it.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Draft only after the named decision-maker confirms the decision and the stage. Harper does not decide who is rejected.
Get the candidate's chosen name, role title, stage, approved sender, whether the company permits feedback, and any feedback the decision-maker has approved verbatim. Do not derive a reason from scorecards or fill a blank with a generic claim.
Lead with the decision in the first two sentences. Thank the candidate for the specific time or work they gave. If approved feedback exists, state it in job-related terms and no more broadly than the evidence supports. Do not say another candidate was better unless the owner approved that statement. Do not promise future contact.
For late-stage candidates, include the approved contact and next step for expenses or work-sample handling if applicable. Keep the subject plain.
Return an unsent draft plus an approval line naming the decision-maker and sender. Never send it. Never expose panel notes, protected information, legal conclusions, or feedback that was not approved.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
中文简介正在准备中。当前显示原文说明。
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
中文简介正在准备中。当前显示原文说明。
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
中文简介正在准备中。当前显示原文说明。
Write ad variants that each test one idea, within platform limits and supported claims.
中文简介正在准备中。当前显示原文说明。
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
中文简介正在准备中。当前显示原文说明。
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
中文简介正在准备中。当前显示原文说明。