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

sales-proposal-writer

Skill21 starsChanged 51 days agoNo licenceView on GitHub

Turn a qualified CRM deal plus whatever the client actually sent — a requirement sheet, discovery notes, a meeting transcript, a prior proposal — into a priced client proposal published as a 交付文件 at platform.zynkr.ai/d/<token>, and keep it alive through the revision rounds. It does four things in one pass: ranks the client's asks by an openly-stated criterion and presents them as 第一順位/額外項目 (never colour codes, never our internal IDs); splits them into a recurring lane and a one-off build lane; prices every line from the B2B pricing sheet anchored at NT$10,000/hr with the hours shown; and writes an honest-boundaries section saying what we will not do and why. On later rounds it reads the review comments on the document, applies them, resolves them, verifies the published body by checksum, and syncs the CRM note, the Gmail draft and the kickoff doc in the same pass. Trigger on /sales-proposal-writer or when Peter says "寫提案", "幫我做提案", "報價給這個客戶", "把需求整理成提案", "提案 v2", "draft the proposal", "quote this client", "update the proposal", or hands over a client's requirement list and wants a priced document out of it. Distinct from sales-follow-up (writes the post-demo EMAIL on an existing deal — this writes the PROPOSAL and hands the email to it), consult-solution-planning (an INTERNAL solution plan, unpriced) and consult-brd-writer (a requirements document, unpriced).

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 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.

  • 0

    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.