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

sales-research

Skill21 starsChanged 51 days agoNo licenceView on GitHub

Runs AI background research on a company (and optionally a contact) in the Zynkr CRM and writes a concise, sales-context zh-TW brief back onto that record as a CRM note (備註) via `mcp__zynkr__create_note`. The research runs on the Claude Code side — WebSearch/WebFetch plus the Taiwan government registry APIs keyed off the 統一編號 — and only the write-back touches the platform, so it spends NO workspace AI quota. The platform's own "AI 背景研究" button and its MCP twin `mcp__zynkr__research_company` do the same job but bill the workspace AI budget; prefer this skill unless Peter asks for that one by name. Trigger EAGERLY whenever Peter says "trigger company research", "research this company", "研究這間公司", "查一下這間公司背景", "幫我查一下[公司名]", "look into [company]", "跑一下背景研究", or asks to research/enrich/look up a company or contact that is or is about to be in the Zynkr CRM — even if he only names the company and doesn't spell out "research." Also fire immediately after a company/contact gets created in this conversation if he asks for research on it in the same breath (e.g. "create a company for X, also trigger company research"). Do NOT fire automatically after every company/contact creation on your own initiative — only when asked, in this call or the next.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. About 0 are common, 12 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    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 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.