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

sales-outbound

Skill21 starsChanged 50 days agoNo licenceView on GitHub

Turn ONE person's interest signal into a tracked CRM lead AND a ready-to-send reply. The signal can be a copied DM / chat thread (Threads, IG, LINE, FB Messenger, WhatsApp, email), a single row from an event feedback or registration form, a website enquiry, or the text off a business card — anything where one named person showed interest and left an email address. Optionally hand it their profile link too. It does two things in one pass: (1) collects who they are — parsing the signal and enriching from any social/profile URL — and writes the client context into Zynkr CRM (find-or-create company + contact, a new deal, a verbatim source note, and a follow-up task for the next step); (2) drafts the outbound reply as a Gmail DRAFT in Peter's inbox (never sends), in the signal's language and Peter's voice, and — whenever the ask is a meeting — reads Peter's calendar FIRST and offers three real slots in 台北時間. Trigger on /sales-outbound or when Peter pastes a DM, a feedback-form row, or an enquiry and says "draft a reply", "draft an outbound mail", "回這個", "幫我擬回覆", "把這個 lead 建進 CRM 並擬信", "log this lead and draft the email", "turn this DM into a draft", "這個回饋幫我 建客戶並擬信", or otherwise hands over one person's interest signal and wants both the CRM record and the reply prepared. Distinct from sales-client-sourcing (BATCH-enriches a WHOLE survey Sheet into new columns — no CRM records, no email), consult-intake (a weekly BATCH sweep of inbound website consult EMAILS) and consult-project-specialist (documents ONE sales/consulting MEETING transcript into a project + Drive folder + deal): this one takes ONE person's signal and produces a lead record + a drafted reply, no Drive folder, no meeting parsing. Mode B — a five-touch outbound SEQUENCE for someone who has NEVER replied: trigger on "一週五封", "連續開發信", "跑一整套序列", "同一個人五次", "五封序列", or when Peter points at the 陌開名單 roster and wants a batch worked end to end. Mode B claims the lead in the roster, reads Peter's calendar for real slots, picks a role angle, writes all five emails, saves them as Gmail drafts, and logs the touch. See references/sequence-5touch.md.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    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 364,980 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.