write-win-loss
Skill14 starsChanged 3 months agoMITView on GitHub
Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Write Win Loss”. A useful skill states the six fields from Skills and routines. A deal closed won or lost and the owner needs a memo other reps can reuse — pattern and evidence, not a feeling. Every cause has a quote or CRM field. Competitor names and numbers are quoted, not paraphrased. The account was not contacted. Win/loss memo with…
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- convert/claude.mdCLAUDE.md
- docs/llms.txtllms.txt
- audit-subscriptionsSkill
- cited-researchSkill
- cloud-bill-noteSkill
- collate-feature-asksSkill
- coordinate-launchSkill
- daily-digestSkill
- defend-calendarSkill
- design-bot-templateSkill
- detect-docs-driftSkill
- diff-competitorsSkill
- draft-call-followupSkill
- draft-changelogSkill
- draft-issueSkill
- draft-newsletterSkill
- draft-security-answersSkill
- draft-sqlSkill
- draft-support-replySkill
- garden-memorySkill
- harden-repoSkill
- incident-timelineSkill
- install-teamSkill
- interrogate-assumptionsSkill
- investigate-perfSkill
- log-promisesSkill
- package-evidenceSkill
- plan-tripSkill
- prep-meetingSkill
- queue-socialSkill
- ramp-new-hireSkill
- rank-account-healthSkill
- recommend-media-reallocSkill
- reconcile-expensesSkill
- remix-contentSkill
- reproduce-bugSkill
- research-accountsSkill
- review-pr-riskSkill
- route-workSkill
- sanitize-shareSkill
- scout-x-threadsSkill
- source-talentSkill
- sweep-ciSkill
- triage-inboxSkill
- vendor-renewalsSkill
- watch-aeoSkill
- watch-brandSkill
- weekly-saas-financeSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Call notes or Notion recaps
- Distinctive: line 27
Write the memo. Do not email the account.
- Distinctive: line 31
Every cause has a quote or CRM field.
- Distinctive: line 41
Do not email the lost or won account.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Write Win Loss
Paste this into Grok Bot after a successful run:
Save the process we just used as a skill called “Write Win Loss”.
A useful skill states the six fields from Skills and routines.
1. When to use it
A deal closed won or lost and the owner needs a memo other reps can reuse — pattern and evidence, not a feeling.
2. Required inputs and access
- CRM close record (outcome, amount, date, competitor field)
- Call notes or Notion recaps
- Slack threads the owner named for that deal
- Prior win/loss memos in /workspace when present
3. Sequence of work
- Load the close record. If it is missing, ask for the deal name and stop.
- Collect quotes from notes, Slack, and Notion. Ignore adjectives with no source.
- Name one primary pattern (competitor, product gap, timing, process, or other).
- Compare to prior memos when they exist. Do not declare a new strategy from one deal.
- Write the memo. Do not email the account.
4. How to validate the result
Every cause has a quote or CRM field. Competitor names and numbers are quoted, not paraphrased. The account was not contacted.
5. What to return
Win/loss memo with facts, pattern, quotes, copy/stop, comparable memos, and an action log.
6. What requires approval
Do not email the lost or won account. Do not change CRM stage or amount. Do not publish the memo outside the company.
Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.
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
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.