pd-follow-up
Skill0 starsChanged 30 days agoMITView on GitHub
Draft follow-up or nudge emails for Pipedrive deals using deal history and last notes; saves as Gmail or Outlook draft if connected, never sends. Use when the user asks to draft a follow-up, nudge, recap email or re-engage a quiet deal.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- pd-accessSkill
- pd-account-healthSkill
- pd-advisorSkill
- pd-askSkill
- pd-coreSkill
- pd-crm-architectSkill
- pd-data-hygieneSkill
- pd-icp-discoverySkill
- pd-industrySkill
- pd-lead-qualifierSkill
- pd-morning-briefSkill
- pd-pipeline-reviewSkill
- pd-playbook-minerSkill
- pd-premortemSkill
- pd-setupSkill
- pd-thread-mapSkill
- pd-win-backSkill
- pd-win-lossSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Follow pd-core rules (load pd-core if not loaded).
- Very specific: line 25
No invented facts, prices or promises.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
pd-follow-up
Follow pd-core rules (load pd-core if not loaded).
Requires: Pipedrive
Optional: Gmail or Outlook (save as draft)
Fallback: Pipedrive note [Claude] Draft email (after confirm) or chat
Steps
- Identify deal(s). Batch mode: "nudge my quiet deals" ->
getDeals owner_id=<me> status=open updated_until=<today - stale_days> limit=20(stale_daysfrom.pipedrive/config.json, default 14), then draft up to 10. - Per deal fetch:
getDeal,getNotes deal_id limit=5,getPersons deal_id(recipient email). No email on file: say so, draft anyway. - Pick the type: recap after call, nudge after silence, proposal follow-up, re-engage lost/cold, meeting request.
- Draft rules:
- 60-120 words, the user's language and tone (copy tone from earlier notes or emails if visible).
- One specific reference to the last conversation. One clear ask with a date or two time options.
- No invented facts, prices or promises. Missing info:
[placeholder]. - Subject line under 8 words.
- Save: Gmail/Outlook draft if live (to the person's email, nothing sent). Otherwise show in chat; offer to save as a Pipedrive note.
- Offer: create an activity "Follow up on email" due in 3 business days (safe-write).
Output
Deal 1042 Acme rollout -> ana@acme.com (Gmail draft saved)
Subject: Revised quote for the October rollout
<body>Batch: one line per draft plus where it was saved. Never send. Never ask the user for email passwords.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.