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

sales-manager

Skill21 starsChanged 50 days agoNo licenceView on GitHub

The conductor of the Zynkr sales family — it decides which sales skill a given input needs, chains them when a job takes more than one, and reads the CRM across deals to say which ones need attention now. It owns the deal lifecycle; the five skills under it each own one step. Three modes: ROUTE (one input → the right child skill), SEQUENCE (a job that needs two or more, e.g. triage a whole event survey with sales-client-sourcing then run sales-outbound on each Hot Lead row), and REVIEW (deal-level pipeline sweep — what is stalled, what has no next step, whose follow-up task is overdue, whose draft is still unsent). It may write to the CRM, but never silently: every change is proposed as one batch and applied only on a single confirmation. Trigger on /sales-manager or when Peter says "什麼 deal 該追", "業務進度盤點", "pipeline review", "這週業務要做什麼", "幫我看一下 CRM 有什麼卡住", "handle this lead" without naming a skill, or hands over sales input and wants the whole job done rather than one step of it. Distinct from zynkr-gm (the company-level GM brief across every LOB — this one is the sales pipeline only, and never writes a weekly narrative), consult-status-report and consult-governance (the consulting portfolio), and zynkr-skills (which routes the whole skill ecosystem, not within sales).

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 7 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    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.