agentleFS
peter-tu-zynkrpeter-tu-zynkr/zynkr-skill-builder/skills/2-sales-consultant/sales-follow-up/SKILL.md

sales-follow-up

Skill21 starsChanged 51 days agoNo licenceView on GitHub

Turn a finished sales DEMO / discovery call into a converting follow-up — the post-meeting counterpart to sales-outbound. Give it the demo transcript (a Fireflies meeting, a Google Doc URL, or pasted notes) and it does two things in one pass: (1) drafts a pre-sales follow-up reply as a threaded Gmail DRAFT in Peter's inbox (never sends), in the prospect's language and Peter's voice — opening by mirroring the exact pain points they raised, mapping each to the matching Zynkr CRM capability (zynkr.ai/crm), and moving them toward adopting the solution, with a "sales kit attached manually" line; (2) syncs the EXISTING CRM deal — finds the deal / contact / company, logs the demo as a note activity, refreshes the deal summary, nudges the stage if warranted, closes the now-stale scheduling task, and creates the agreed follow-up task. Trigger on /sales-follow-up or when Peter hands over a demo / meeting transcript after a call and says "draft a follow-up", "draft the pre-sales follow-up", "follow up on this demo", "寫跟進信", "擬一封 demo 後的跟進信", "幫這場 demo 寫追蹤信並更新 CRM", "log the demo and draft the follow-up", or otherwise wants the post-demo email plus the deal updated. Distinct from sales-outbound (a PRE-meeting DM → new lead + first reply) and consult-project-specialist (documents a meeting into a NEW project + Drive folder): this one takes ONE completed demo transcript on an EXISTING deal and produces a conversion follow-up draft + a light deal update — no new lead, no Drive folder, no meeting-to-project.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.