Follow up planner
面向外贸出口场景的 Hermes / Open claw Agent Skills 包,支持海外客户发现、批量名单处理、公司背调、客户评分、决策层线索、开发信、跟进计划和报价单导出。
npx -y skills add Xuxchloris/export_skills --skill follow-up-plannerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when a trade agent needs outreach follow-up timing, next-touch planning, reminder schedules, buyer reply follow-up, quotation follow-up, sample follow-up, or prospect status updates
SKILL.md
2.3 KB, as published. Nobody here has run it
Follow-Up Planner
Overview
Create a practical follow-up schedule from prospect priority and reply status. The core rule is to generate reviewable tasks, not automatic sends.
When to Use
Use this skill after an outreach draft, buyer reply classification, quotation draft, sample discussion, or meeting request when the user needs the next-touch plan.
Use reply-classification first when an inbound reply has not been classified.
Inputs
- Prospect priority from
prospect-scoring - Last contact date and channel
- Reply classification, if available
- Quotation, catalog, sample, or meeting status
- Tone rules from
TONE.yaml
Outputs
{
"prospect_status": "",
"last_contact_date": "",
"tasks": [
{
"due_date": "",
"task_type": "",
"reason": "",
"draft_requested": false,
"human_review_required": true
}
],
"pause_reason": "",
"review_notes": []
}
Procedure
- Read the prospect priority, last contact date, and latest reply classification.
- Pause planning when the prospect status does not call for another touch.
- For an unanswered A or B prospect, suggest a light sequence such as D+3, D+7, and D+14 from the first outreach date.
- For a quotation, catalog, sample, or meeting discussion, plan the next touch from the latest buyer-facing action.
- Keep each task specific: due date, task type, reason, and whether an email draft is needed.
- Send email draft requests to
email-crafting. - Keep every task as a human-reviewed reminder.
Verification
- Due dates are derived from the latest relevant contact.
- Task reasons match prospect status and buyer signals.
- Paused prospects receive no new follow-up task.
- The plan does not send messages automatically.
- Every generated task requires human review.
Common Mistakes
| Mistake | Fix |
|---|---|
| Scheduling from an old contact date | Use the latest relevant action |
| Giving every prospect the same cadence | Consider priority and reply type |
| Creating vague reminders | Include due date, reason, and task type |
| Treating a task as an automatic send | Keep it as a human-reviewed reminder |